
DL4300 Appliance
About the Repository Optimization Job
97
NOTE:
This job checks the integrity of all of the contents within a repository. For information about the
Integrity Check
job, which you can use to ensure that a repository is mountable and usable, see
Parent topic
Checking a repository
Rapid Recovery lets you perform a diagnostic check of a DVM repository volume when errors occur. Core errors
could be the result of it being improperly shut down, a hardware failure, or other environmental, lower IP stack
factors that can be exposed in Rapid Recovery functionality.
NOTE:
This procedure should only be performed for diagnostic purposes. For example, run this check in
the event of hardware failure, improper shutdown of the Core, or failure when importing a repository.
1. Navigate to the Rapid Recovery Core Console.
2.
On the icon bar, click (More), and then select Repositories.
The Repositories page appears.
The DVM Repositories pane appears.
3. To check a DVM repository, in the DVM Repositories pane, in any row of the summary table representing a
DVM repository, click
and then select Check.
The Check Repository dialog box appears.
4. In the Check Repository dialog box, confirm that you understand that all active tasks associated with this
repository will be canceled and that you want to proceed.
Active jobs are canceled and the Check Repository Job starts.
5. Optionally, can you track the status of the job by clicking the Running tasks drop-down menu in the button
bar, and selecting the Maintaining repository job.
Parent topic
About the Repository Optimization Job
When using a DVM repository, the data you capture in each snapshot is deduplicated. This deduplication occurs
incrementally, as snapshots are saved to the 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 DVM 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 DVM 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
.
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