Chat now with support
Tchattez avec un ingénieur du support

Rapid Recovery 6.3 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Credentials Vault Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore BMR Windows and Linux Understanding boot CD creation for Windows machines Managing a Linux boot image Performing a bare metal restore using the Restore Machine Wizard Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts Core Console references REST APIs Glossary

Performing an integrity check on a legacy DVM repository

An integrity check is available for DVM repositories. The purpose of this procedure is to check the integrity of an entire DVM repository. During the execution of the integrity check, which can be lengthy, no other actions can be performed in the repository.

If you have multiple DVM repositories for a target Core, perform this process once for each repository.

NOTE:If you have another DVM repository on the target Core for which the Checking Repository job has already been completed, or if you create a new additional repository for this target Core, you can perform operations in that secondary repository while the Checking Repository job is running on the DVM repository you specified.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [More] 
    (More), and then select Repositories.

    The Repositories page displays.

  3. In the DVM Repositories summary table, from the row representing the DVM repository that you want to check, click [Actions] 
    (More options) and from the drop-down menu, select Check Repository.

    A confirmation message appears.

    Caution:Before you confirm that you want to perform the job, you should carefully consider the duration of time required. 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.

  4. From the Check Repository dialog box, to perform the integrity check, click Yes.

    The dialog box closes. Any jobs that were queued or that are in progress are canceled, and the integrity check job begins.

  5. To monitor the progress of the Integrity Check job for a repository, including a determination of whether additional steps are required after the check, from the icon bar, click [Events] 
    (Events).
  6. From the Tasks page, click [Job Details] 
    Job Details for the job to view more information about the job status.
    • If you see an error in any child tasks for this job, note the error and provide the information to a Quest technical support representative.
    • If the Integrity Check job completes all child tasks successfully, you can then establish a custom retention policy for this repository.

About DVM repository optimization

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 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 DVM repository, see Optimizing a DVM repository.

You can interrupt the Optimize Repository job for a limited time if required. For more information, see Interrupting or resuming DVM repository optimization.

Optimizing a DVM repository

You must have a DVM repostiory in your Core to perform this procedure.

You can perform offline deduplication of data saved to an existing DVM 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 DVM deduplication cache.

Complete the steps in this procedure to optimize a DVM repository.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [More] 
    (More), and then select Repositories.

    The Repositories page appears.

  3. In the DVM Repositories pane, from the row representing the repository you want to optimize, click [More] 
    (More options) and then select Optimize.

    A warning prompt appears asking you to confirm the optimization.

  4. 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 DVM repository optimization.

Interrupting or resuming DVM repository optimization

This task requires a DVM repository to exist in your Core, with a running repository optimization job.

When you initiate the Optimize Repository Job, the selected DVM repository is deduplicated. This deduplication optimization is a processor-intensive job intended to save space in the repository. For more information, see About DVM 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.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [More] 
    (More), and then select [More] 
    Repositories.

    The Repositories page appears.

  3. If you want to interrupt an optimization job, do the following:
    1. In the repositories summary table, from the row representing the appropriate repository, click [More options] 
      (More options) and then select Interrupt Optimization Job.

      A warning prompt appears asking you to confirm the interruption.

    2. To confirm the interruption, click Yes.
  4. If you want to resume an interrupted optimization job, do the following:
    1. In the repositories summary table, from the row representing the appropriate repository, click [More options] 
      (More options) and then select Optimize.

      A warning prompt appears asking you to confirm the optimization.

    2. 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.

Documents connexes