What are three true statements about an integrity check in vCenter Data Recovery?

What are three true statements about an integrity check in vCenter Data Recovery? (Choose three.)

A.
The operation reclaims space on the deduplication store.

B.
The operation can be executed outside of the maintenance window.

C.
The operation ensures that the deduplication store is synchronized with the catalog.

D.
The operation can be resumed from a previous incomplete integrity check.

E.
The operation can be incremental.

3 Comments on “What are three true statements about an integrity check in vCenter Data Recovery?

  1. Ajay says:

    B is not correct, Integrity check operation can not be executed outside maintenance window. A is the correct choice as it reclaims space on deduplication store.

    So correct answer is A, D and E

    1. Jon says:

      http://pubs.vmware.com/vsphere-50/topic/com.vmware.datarecovery.admin.doc_20/GUID-FC3ABCAE-7517-4B46-AD0B-F7464FBB2C00.html

      “In addition, the integrity check can be started manually. When the integrity check is started manually, it always performs full integrity check of the entire destination, and does not use the maintenance window.”

      The article also goes on to show that D and E are correct answer and A is incorrect because reclamation of space is up to the so aptly named “reclaim” job.

  2. vcp510 says:

    There are several processes that the deduplication store completes including integrity check, recatalog, and reclaim.
    Integrity check

    This operation is performed to verify and maintain data integrity on the deduplication store. Integrity checks are completed on some or all of the deduplication store under different conditions. Data Recovery is designed to complete an incremental or full integrity checks during the maintenance window. Incremental integrity checks verify the integrity of restore points that have been added to the deduplication store since the most recent full or incremental integrity check. Data Recovery is also designed to perform an integrity check of all restore points once a week.

    The destination maintenance window should be used to avoid the case where integrity checks may consume computing resources or otherwise interfere with any backup operations in process. As a result, the destination maintenance window and backup window should be defined such that they do not overlap. The destination maintenance is stopped if it does not complete within the defined window. Even if the maintenance is stopped, the destination is not locked out from other operations such as backup and restore. The next time destination maintenance window opens, the operation continues where it was left off. For more information on configuring the maintenance window, see Establish a Maintenance Schedule.

    In addition, the integrity check can be started manually. When the integrity check is started manually, it always performs full integrity check of the entire destination, and does not use the maintenance window. Normally, the backup and restore operations are allowed from the deduplication store while the integrity check is in progress. If a restore point is manually marked for delete, backups are not allowed during integrity check but restore operations are allowed. If damaged restore points are found in the deduplication store during integrity check, a manual integrity check must be run after marking the damaged restore points for delete. During this manually run integrity check, backups and restores are not allowed.

    Data Recovery stores information about the progress of an integrity check. As a result, if the backup appliance stops integrity check, the process can be restarted from where the check was stopped, thereby ensuring that work completed on an integrity check is not lost. The backup appliance stops integrity checks when the maintenance window passes. Tracking progress helps ensure integrity checks eventually complete. Integrity checks that are manually stopped by user intervention do not save progress information, so after such a stop, the integrity check begins again from the start.
    Recatalog

    This operation is performed to ensure that the catalog of restore points is synchronized with the contents of the deduplication store. This operation runs automatically when there is an inconsistency detected between the catalog and the deduplication store. While the recatalog operation is in progress, no other operation is allowed on the deduplication store.
    Reclaim

    This operation is performed to reclaim space on the deduplication store. This can be a result of the Data Recovery appliance enforcing the retention policy and deleting expired restore points. This operation runs automatically on a daily basis according to the maintenance window. While the reclaim operation is in progress, backups to the deduplication store are not allowed, but restore operations from the deduplication store are allowed.

    The reclaim operation starts or is deferred based on the same logic used for determining whether or not to complete an integrity check. Reclaim operations are generally run once every 24 hours when no backup windows are active.

    During the reclaim operation, Data Recovery applies the retention policy for each source virtual machine in a backup job for the corresponding destination. If one virtual machine is included in multiple backup jobs with different retention policies, Data Recovery combines the retention policy, keeping sufficient backups to meet the criteria of all backup jobs. If a source virtual machine was defined in a backup job at some point, but the virtual machine is deleted or is no longer defined in a backup job, none of the restore points of that virtual machine are removed.

    The retention policy keeps backups that are some combination of being weekly, monthly, quarterly, or yearly. Those periods are defined as follows:


Leave a Reply

Your email address will not be published. Required fields are marked *