This procedure assumes that your Core is already replicating to an Azure repository.
In the settings for an Azure repository, you can change such settings as number of concurrent operations, and enabling or disabling deduplication or compression.
Complete the following task to change the available settings for an Azure repository.
To change Azure repository settings
- From the Rapid Recovery Core Console, in the icon bar, click
![[More]](/pt-br/technical-documents/image/f406e47a-494d-43cd-b8a5-f1cda29ea056)
(More), and then select 
Repositories.
- On the Repositories page, from the row representing the repository you want to update, click
(More options) and then select Settings.
The Repository Settings dialog displays.
- On the Repository Settings dialog, you can change the settings described in the following table.
Table 13: DVM settings
| Maximum concurrent operations |
The number of jobs that the repository can perform at one time. The default is 64. |
| Description |
Can contain and display notes or a description that you want to associate with this repository. |
| Azure repository size |
The maximum amount of space you want to reserve for the Azure repository.
|
|
NOTE:Rapid Recovery uses only as much space in the repository as it needs for your replicated data. The size that you enter tells Rapid Recovery not to use more space than the specified amount. | |
| Deduplication cache size |
The maximum amount of space you want to reserve for the dedupe cache.
|
| Metadata cache size |
The maximum amount of space you want to reserve for the metadata cache.
|
| Enable deduplication |
When this option is selected, Rapid Recovery Core deduplicates data so that only unique blocks are saved to the repository.
This setting is enabled by default. Clear this option and save to disable deduplication. |
| Enable compression |
When this option is selected, Rapid Recovery Core compresses data to reduce space used.
This setting is enabled by default. Clear this option and save to disable compression. |
- Click Save.
The changes are applied to the repository.
When you protect a machine with Rapid Recovery, the data you capture in each snapshot is deduplicated and stored in a DVM repository and then optionally replicated to a DVM repository on another Core or to an Azure repository. This deduplication occurs incrementally, as snapshots are saved to the initial repository. One occurrence of each string of information is saved to the repository. When an information string is duplicated, a reference to the original string in the deduplication cache is used, saving storage space in the repository.
If the deduplication cache is filled, only snapshot data that is already referenced in the cache is deduplicated. As deduplication occurs, the cache continues to update with new unique values, overwriting the oldest values in the cache. This results in less than optimal deduplication.
For more information about deduplication, see Understanding deduplication cache and storage locations.
You can choose to increase your duplication cache before it is full, which ensures continued optimal deduplication of your data in that repository. For more information, see Configuring DVM deduplication cache settings.
You can also increase your deduplication cache after it is full. If you want to reclaim space in the repository after increasing your cache, you can optimize the repository. This action forces a comparison of the data in your snapshots to the information in the deduplication cache. If any repeated strings are found in the repository, that data is replaced with references to the data, which saves storage space in the repository. This is sometimes referred to as off-line deduplication, since this deduplication process occurs upon your request, instead of incrementally as snapshot data is transferred.
The optimization process is processor-intensive. The amount of time it takes to run this job depends on several factors. These factors include the size of your repository; the amount of data in your repository; available network bandwidth; and existing load on the input and output of your system. The more data in your repository, the longer this job runs.
The following actions are superseded or canceled when the Repository Optimization Job is occurring.
- Delete All Recovery Points Job
- Delete Recovery Points Chain Job
- Maintain Repository Job
- Delete Recovery Points Job Base
- Optimize Repository Job
For steps on optimizing an existing repository, see Optimizing a repository.
You can interrupt the Optimize Repository job for a limited time if required. For more information, see Interrupting or resuming repository optimization.
You can perform on-demand deduplication of data saved to an existing repository. This is accomplished by launching the Repository Optimization Job.
|
|
NOTE: Quest recommends performing the Optimize Repository job only after increasing your deduplication cache size. This action lets you reclaim repository space and more effectively use the deduplication cache. |
Complete the steps in this procedure to optimize a repository.
- Navigate to the Rapid Recovery Core Console.
- On the icon bar, click (More), and then select Repositories.
The Repositories page appears.
- From the row representing the repository you want to optimize, click
![[More]](/pt-br/technical-documents/image/dcd1bf77-dea4-4111-9aad-cda7af5b0e9a)
(More options) and then select Optimize.
A warning prompt appears asking you to confirm the optimization.
- To confirm the optimization, click Yes.
The optimization job takes precedence over most other jobs. If necessary, you can interrupt an optimization job in progress. For more information on interrupting or resuming this job, see Interrupting or resuming repository optimization.
When you initiate the Optimize Repository Job, the selected repository is deduplicated. This deduplication optimization is a processor-intensive job intended to save space in the repository. For more information, see About repository optimization.
Once this job has been initiated, you can interrupt the job using the following procedure. This pauses deduplication. If you have already interrupted a optimization, you can resume the process using this procedure.
Complete the steps in this procedure to interrupt or resume a repository optimization job.
- Navigate to the Rapid Recovery Core Console.
- On the icon bar, click (More), and then select Repositories.
The Repositories page appears.
- If you want to interrupt an optimization job, do the following:
- In the repositories summary table, from the row representing the appropriate repository, click (More options) and then select Interrupt Optimization Job.
A warning prompt appears asking you to confirm the interruption.
- To confirm the interruption, click Yes.
- If you want to resume an interrupted optimization job, do the following:
- In the repositories summary table, from the row representing the appropriate repository, click (More options) and then select Optimize.
A warning prompt appears asking you to confirm the optimization.
- In the dialog box, select the option Continue job from the interrupted point, and then click Yes.
The dialog box closes, and the repository optimization job resumes from the point where it was last interrupted.
