Creating a DVM repository
Complete the following steps to create a DVM repository.
|
1. |
|
2. |
![[More]](/technical-documents/image/06c335e5-e428-4d93-ab36-dbbd04003f6e){kind=small}
(More), and then select The Repositories page appears.
On the Repositories page, the DVM Repositories pane appears.
|
3. |
|
5. |
Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary 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 Common Internet File System (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. |
|
Enter the location for storing the protected data. For example, type X:\Repository\Data. | |
|
Enter the location for storing the protected metadata. For example, type X:\Repository\Metadata. |
|
◦ |
Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table. |
|
8. |
In the Storage Configuration area, click More Details and enter the details for the storage location as described in the following table. |
| |||||||||
|
Set the value to one of the following:
If set to Off, Rapid Recovery controls the caching. If set to Sync, Windows controls the caching as well as the synchronous input/output. | |||||||||
|
Specify the number of bytes you want each sector to include. The default value is 512. | |||||||||
|
Specify the average number of bytes per record. The default value is 8192. |
|
9. |
|
10. |
|
11. |
When all of the storage locations you want to create for the repository at this time have been defined, in the Add New Repository dialog box, click Create. |
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
|
1. |
|
2. |
The Repositories page appears.
The DVM Repositories pane appears.
|
3. |
In the repositories summary table, from the row representing the DVM repository for which you want to add a storage location, click Settings and select Add Storage Location. |
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. |
|
Enter the location for storing the protected data. For example, type X:\Repository\Data. | |
|
Enter the location for storing the protected metadata. For example, type X:\Repository\Metadata. |
|
◦ |
Or, select Add file on CIFS share to specify a network share location and then enter the information as described in the following table. |
|
5. |
In the Storage Configuration pane, click More Details and enter the details for the storage location as described in the following table. |
| |||||||||
|
Set the value to one of the following:
If set to Off, Rapid Recovery controls the caching. If set to Sync, Windows controls the caching as well as the synchronous input/output. | |||||||||
|
Specify the number of bytes you want each sector to include. The default value is 512. | |||||||||
|
Specify the average number of bytes per record. The default value is 8192. |
|
6. |
Optionally, if you want to perform the repository optimization job for the selected repository, select Run Repository Optimization Job for [Repository name]. |
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.
For more information about the repository optimization job, see About the Repository Optimization Job.
|
7. |
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 to 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 this 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).
|
NOTE: In AppAssure Core versions, this job was called Integrity Check job. In Rapid Recovery Core this job is named Check Repository Job. |
For instructions on how to perform this check, see the procedure Performing an integrity check on a legacy DVM repository.
You do not need to run this job:
|
• |
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.
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 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. |
Performing an integrity check on a legacy DVM repository
An integrity check is available only for legacy AppAssure DVM repositories that may still be in use after an upgrade to Rapid Recovery. The purpose of this procedure is to check the integrity of an entire DVM repository. This is recommended for replicated target cores when upgrading from AppAssure 5.3.x to release 5.4. During the execution of the integrity check, which can be lengthy, no other actions can be performed in the repository.
|
1. |
|
2. |
The Repositories page appears.
The DVM Repositories pane appears.
|
3. |
![[Actions]](/technical-documents/image/1a257d2f-d6b2-4239-8e8a-90d287c80797){kind=small}
and from the drop-down menu, and then click A confirmation message appears.
|
4. |
![[Events]](/technical-documents/image/bf7f8973-8c1c-4ed0-a7c8-87f5f4de00c5){kind=small}
(Events). |
6. |
![[Job Details]](/technical-documents/image/ef6d9536-5e80-4708-b037-6af769299e75){kind=small}