Converse agora com nosso suporte
Chat com o suporte

Rapid Recovery 6.7 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings 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 Snapshots and recovery points Managing privacy Encryption Authentication Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore Differences in bare metal restore for Windows and Linux machines 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

Forcing a snapshot

Forcing a snapshot lets you force a data transfer for the current protected machine. When you force a snapshot, the transfer starts immediately or is added to the queue if other jobs are running.

You can choose from two types of snapshots.

If you select an incremental snapshot and there is no previous recovery point, a base image is captured. Forcing a snapshot does not change the timing for any schedules snapshots.

  • A base image is a snapshot of all data on the selected volumes of the machine.
  • An incremental snapshot captures all data that has been changed since the last snapshot.
  1. In the Rapid Recovery Core Console, navigate to the machine or cluster with the recovery point for which you want to force a snapshot.
  2. On the Summary page, in the Summary pane, click Force Snapshot.

    The Force Snapshot dialog appears.

  3. In the Force Snapshot dialog box, in the check box, click one or more volumes or protection groups.
  4. Click Force Snapshot or Force Base Image, respectively.
  5. If you selected a base image, click to confirm that you want to take a base image.

    A base image could take a substantial amount of time, based on the amount of data in the volumes you want to back up.

    The snapshot you selected is queued and begins as soon as other jobs have completed.

Removing recovery points

You can easily remove recovery points for a particular machine from the repository. When you delete recovery points in Rapid Recovery, you can specify one of the following options.

  • Delete All Recovery Points. Removes all recovery points for the selected protected machine from the Repository.
  • Delete a Range of Recovery Points. Removes all recovery points in a specified range before the current, up to and including the base image, which is all data on the machine as well as all recovery points after the current until the next base image.

NOTE: You cannot recover the recovery points you have deleted. If you need the data stored in the recovery points, considering archiving the data first.

  1. In the Rapid Recovery Core Console, under the Protected Machines menu, click the name or IP address of the machine for which you want to view and remove recovery points.
    The Summary view for the selected protected machine appears.
  2. Next to the machine name or IP address, click the Recovery Points menu.
    The Recovery Points page for the selected machine appears.
  3. Scroll down to the Recovery Points pane.
    Options appear under the pane title, including Refresh, Delete Range, and Delete All.
  4. To delete all currently stored recovery points, under the Recovery Points pane title, click Delete All, and in the confirmation dialog box, click to confirm deletion.
  5. To delete a set of recovery points in a specific data range, do the following:
    1. Under the Recovery Points pane title, click Delete Range.
      The Delete Recovery Points Within Range dialog box appears.
    2. In the Delete Recovery Points Within Range dialog box, in the From field, select the date and time from which you want to start deleting recovery points.
    3. In the To field, select the date and time defining the last recovery point you want to delete.
    4. Click Delete.
    5. In the confirmation dialog box, click to confirm deletion.

Deleting an orphaned recovery point chain

An orphaned recovery point is an incremental snapshot that is not associated with a base image. Subsequent snapshots continue to build onto this recovery point; however, without the base image, the resulting recovery points are incomplete and are unlikely to contain the data necessary to complete a recovery. These recovery points are considered to be part of the orphaned recovery point chain. If this situation occurs, the best solution is to delete the chain and create a new base image.

For more information about forcing a base image, see Forcing a snapshot.

  1. In the Rapid Recovery Core Console, navigate to the protected machine for which you want to delete the orphaned recovery point chain.
  2. From the menu at the top of the page, click Recovery Points.
  3. In the Recovery Points pane, expand the orphaned recovery point.

    This recovery point is labeled in the Type column as “Incremental, Orphaned.”

  4. Next to Actions, click Delete.

    The Delete Recovery Points window appears.

  5. In the Delete Recovery Points window, click Yes.

    Caution: Deleting this recovery point deletes the entire chain of recovery points, including any incremental recovery points that occur before or after it, until the next base image. This operation cannot be undone.

    The orphaned recovery point chain is deleted.

Migrating recovery points manually to a different repository

If you want to remove the recovery points of a protected machine from a repository without deleting them, you can migrate them to a different repository manually by using this procedure. This process involves archiving recovery points from the source repository, and then importing the archive into the target repository.

For example, you can perform this procedure if your existing repository is full, or if your needs change and you want to protect a machine using a different Core and repository.

Caution: If your repository was upgraded previously from AppAssure 5.3 or 5.4 and used replication, Quest recommends performing the Check Repository Job on each repository in that target Core before migration. Performing this job will preclude copying any data irregularities to the new destination repository. The Check Repository Job is only available in the UI if it is applicable to your Core, and could take a substantial amount of time to run.

  1. In the Rapid Recovery Core Console, pause protection for any protected machines that have recovery points you want to migrate. For more information, see Pausing and resuming protection.
  2. Cancel all current operations for any protected machines that have recovery points you want to migrate, or wait for them all to complete.
  3. Archive the recovery points for the machine or machines you paused. For more information, see Creating an archive.
  4. After archiving and verifying the archive, remove the existing recovery points for the protected machine you want to migrate. For more information, see Removing recovery points.

    NOTE: Without removing existing recovery points, you cannot change repositories for a protected machine.

  5. Create a new repository for the migrated recovery points, or ensure a new destination repository exists. For more information, see Creating a DVM repository.
    If you want to use an existing repository, continue to step 6.
  6. Change the repository for each machine that you paused by completing the following steps:
    1. On the Core Console, click the protected machine in the navigation tree.
    2. On the Summary page of the protected machine, click Settings.
    3. On the Settings page, in the General pane, click the Repository drop-down list, and then select the name of the repository you created in step 4.

      If you want to use an existing repository, select the name of an existing repository.

      NOTE: When migrating recovery points to an existing repository, ensure that the existing repository has enough free space to contain the migrated recovery points.

    4. Click [Save] to save the change to settings.
  7. Resume protection for the machine or machines that you paused. For more information, see Pausing and resuming protection.
  8. Take a new base image for each of the protected machines you moved. For more information, see Forcing a snapshot and use the Force Base Image option.
  9. Import the archived data for the machines you want to migrate. For more information, see Importing an archive.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação