DL4300 Appliance
About checking the integrity of DVM repositories
96
Text Box
Description
Average Bytes per Record
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].
Dell 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 the Repository Optimization Job
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.
Parent topic
About checking the integrity of DVM repositories
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.
NOTE:
The Cores must share the same three digits for the release number (for example, both start with
6.0.1.xxxx, or 5.4.3.xxxx). The build number (represented by xxxx) can be different only if the target Core is
newer.
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
.
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 Dell Support, so you can
schedule time to work with a Support representative to perform additional procedures to identify and remediate
data inconsistencies.
CAUTION:
Running this job is expected to take an extended period of time. The amount of time differs
based on the amount and type of data in your repository, and on the underlying storage system. While the
job is running, no other transactions can be performed in that repository, including transfers (snapshot and
base image backups, and replication), nightly jobs, and so on.
You can perform other operations in other repositories while this job is running.
