Chat now with support
Chat with Support

The Quest and One Identity Support Portals will be unavailable on Friday July 10, 2020 from 5:30 PM to 6:30 PM for website maintenance.

Rapid Recovery 6.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings
Core settings key functions Rapid Recovery Core settings Core-level tools
Repositories Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts The Local Mount Utility Core Console references REST APIs About us Glossary

Managing a DVM repository

Managing a DVM repository involves the following operations:

1.
Creating a DVM repository. Before creating a repository, consider the appropriate technology type.

For information about the different repository types, see Understanding repositories.

For information about creating a DVM repository, see Creating a DVM repository.

2.
Connecting to a repository. For more information about connecting to an existing repository currently managed by another Core, see Connecting to an existing repository.
3.
Adding a new storage location. For more information on adding a new storage location to a DVM repository, see Adding a storage location to an existing DVM repository.
4.
Checking a repository. For more information about checking a DVM repository, see Checking a repository.
5.
Modifying repository settings. For more information about viewing repository details or modifying settings for a repository, see Viewing or modifying repository details
6.
Performing DVM repository optimization. For more information about the repository optimization job, see About DVM repository optimization. For steps to optimize an existing DVM repository, see Optimizing a DVM repository.
7.
Deleting a repository. For more information about deleting a repository, see Deleting a repository.

For information on managing a tiering repository, see Managing a tiering repository.

Creating a DVM repository

This process describes how to create a repository on your Core using the Deduplication Volume Manager (DVM) repository technology.

If you want to create a tiering repository for secondary storage of recovery points originally saved in your DVM repository, see the topic Creating a tiering repository.

Complete the following steps to create a DVM repository.

1.
Navigate to the Rapid Recovery Core Console.

The Repositories page appears.

The Add New Repository dialog box displays.

Table 27. Add New Repository settings

Text Box

Description

Repository Name

Enter the display name of the repository.

By default, this text box consists of the word Repository and a number, which corresponds to the number of repositories for this Core. For example, if this is the first repository, the default name is Repository 1. Change the name as needed.

Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.

Concurrent Operations

Define the number of concurrent requests you want the repository to support. By default the value is 64.

Comments

Optionally, enter a descriptive note about this repository. You can enter up to 254 characters. For example, type DVM Repository 2.

5.
Click Add Storage Location to define the specific storage location or volume for this repository. Use a fast primary storage drive with sufficient storage space. The storage location for a DVM repository can either be local (on storage attached to the Core server), or on a Common Internet File System (CIFS) network-shared location You cannot specify both for a single storage location.
CAUTION: Define a dedicated folder within the root for the storage location for your repository. Do not specify the root location. For example, use E:\Repository\, not E:\. If the repository that you are creating in this step is later removed, all files at the storage location of your repository are deleted. If you define your storage location at the root, all other files in the volume (e.g., E:\) are deleted, which could result in catastrophic data loss.

The Add Storage Location dialog box appears.

6.
Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location.
7.
In the Storage Location area, specify how to add the file for the storage location. You can choose to add a locally attached storage volume (such as direct attached storage, a storage area network, or network attached storage). You could also specify a storage volume on a CIFS shared location.
Select Add file on local disk to specify a local machine, and then enter the information as described in the following table.

Table 28. Local disk settings

Text Box

Description

Data path

Enter the location for storing the protected data.

For example, type X:\Repository\Data.

When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

Metadata path

Enter the location for storing the protected metadata.

For example, type X:\Repository\Metadata.

When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table.

Table 29. CIFS share credentials

Text Box

Description

UNC path

Enter the path for the network share location.

If this location is at the root, define a dedicated folder name (for example, Repository).

The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

User name

Specify a user name for accessing the network share location.

Password

Specify a password for accessing the network share location.

8.
In the Storage Configuration area, click More Details and enter the details for the storage location as described in the following table.

Table 30. Storage configuration details

Text Box

Description

Size

Set the size or capacity for the storage location. The minimum size is 1 GB. The default is 250 GB. You can choose from the following:

If the storage location is a New Technology File System (NTFS) volume using Windows 8 or later, or Windows Server 2012 or later, the file size limit is 256 TB.

NOTE: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.

Write caching policy

The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations.

Set the value to one of the following:

If set to On, which is the default, Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.

If set to Off, Rapid Recovery controls the caching.

If set to Sync, Windows controls the caching as well as the synchronous input/output.

Bytes per sector

Specify the number of bytes you want each sector to include. The default value is 512.

Average bytes per record

Specify the average number of bytes per record. The default value is 8192.

9.
Click Save.
The Add Storage Location dialog box closes and your settings are saved. The Add New Repository dialog box shows your new storage location.
10.
Optionally, repeat Step 6 through Step 9 to add additional storage locations for the repository.

The Add New Repository dialog box closes, and your changes are applied. The Repositories page appears, showing your newly added repository in the DVM Repositories summary table.

Adding a storage location to an existing DVM repository

A DVM repository must exist in your repository to perform this procedure.

Adding a storage location to a DVM repository lets you define where you want the repository or volume to be stored.

Complete the steps in the following procedure to specify the storage location for the repository or volume.

1.
Navigate to the Rapid Recovery Core Console.

The Repositories page appears.

The DVM Repositories pane appears.

The Add Storage Location dialog box displays.

Select Add file on local disk to specify a local machine and then enter the information as described in the following table.

Table 31. Local disk settings

Text Box

Description

Data path

Enter the location for storing the protected data.

For example, type X:\Repository\Data.

The same limitations to the path apply; use only alphanumeric characters, hyphen, or period, with no spaces or special characters.

Metadata path

Enter the location for storing the protected metadata.

For example, type X:\Repository\Metadata.

When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

Or, select Add file on CIFS share to specify a network share location and then enter the information as described in the following table.

Table 32. CIFS share credentials

Text Box

Description

UNC Path

Enter the path for the network share location.

If this location is at the root, define a dedicated folder name (for example, Repository).

The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

User Name

Specify a user name for accessing the network share location.

Password

Specify a password for accessing the network share location.

5.
In the Storage Configuration pane, click More Details and enter the details for the storage location as described in the following table.

Table 33. Storage location details

Text Box

Description

Size

Set the size or capacity for the storage location. The default size is 250 GB. You can choose from the following:

If the storage location is an NTFS volume using Windows 8, 8.1 or Windows Server 2012, 2012 R2, or 2016, the file size limit is 256 TB.

NOTE: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.

Write Caching Policy

The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations.

Set the value to one of the following:

If set to On, which is the default, Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.

If set to Off, Rapid Recovery controls the caching.

If set to Sync, Windows controls the caching as well as the synchronous input/output.

Bytes per Sector

Specify the number of bytes you want each sector to include. The default value is 512.

Average Bytes per Record

Specify the average number of bytes per record. The default value is 8192.

Quest recommends performing the Repository Optimization Job when adding storage locations to an existing repository. This job optimizes the free space by applying deduplication to data stored in the repository.

Based on factors such as the size of your repository, amount of data in your repository, available network bandwidth, and existing load on the input and output of your system, performing a Repository Optimization Job could take a substantial amount of time and bandwidth in your environment.

For more information about the repository optimization job, see About DVM repository optimization.

7.
Click Save.

The dialog box closes and the storage location is saved. In the repositories summary table, the storage location you created is visible if you expand the repository details.

About checking the integrity of DVM repositories

In AppAssure release 5.3.6 and earlier releases, replication included the process of copying recovery points from the source Core to the target Core regularly. Rollup of aging recovery points occurred only at the source Core. Combined older recovery points were synchronized daily when running the nightly job.

Starting with AppAssure version 5.4.1 and in current releases of Rapid Recovery Core, users can set disparate retention policies between source and target Cores. For replication to work properly with different retention policies, the target Core must have the same software version (or newer) than the source Core.

Administrators can now configure rollup on a target Core at a different rate than on the source Core. Similarly, you can now define a custom retention policy for any replicated machine. For example, you can roll up recovery points in the target Core at a faster rate and with less granularity than on the source Core, saving space. Or you can roll up recovery points for any selected replicated machine at a slower rate in the target Core, maintaining more granularity, which may be useful for compliance purposes. For more information on using a retention policy that differs from the default in the Core, see Customizing retention policy settings for a protected machine.

Some customers experienced inconsistencies in recovery points that were replicated to a target Core prior to AppAssure release 5.3.6. To address this issue, AppAssure release 5.4.1 and later include a Core job to run on each DVM repository. Quest recommends performing the Integrity Check job a single time on each DVM repository on a replicated target Core if the repository was created prior to release 5.4.x (if it was created in release 5.3.x or earlier).

For instructions on how to perform this check, see the procedure Performing an integrity check on a DVM repository.

The Integrity Check job will not be available:

On a new DVM repository on a target Core created in AppAssure release 5.4.1 or later or created in Rapid Recovery.

If your Core has been upgraded at any point from AppAssure 5.3.x and you used replication, you must run this job before you can configure dissimilar retention policies between the source Core and a target Core, or configure a custom retention policy on a replicated machine.

You will not see or be able to run this job unless you have one or more eligible repositories (created prior to 5.4.x and not yet performed).

Running this job verifies the integrity of all data stored in the specified repository, ensuring you can recover data from each snapshot or base image. If the integrity check discovers any issue with data in your repository, the job ceases immediately. The event details for that job on the Core prompt you to contact Quest Data Protection Support, so you can schedule time to work with a Support representative to perform additional procedures to identify and remediate data inconsistencies.

You can perform other operations in other repositories while this job is running.

NOTE: This job checks the integrity of all of the contents within a repository. For information about the Checking repository job, which you can use to ensure that a repository is mountable and usable, see Checking a repository.
Related Documents