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.
|
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. |
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.
This recovery point is labeled in the Type column as “Incremental, Orphaned.”
The Delete Recovery Points window appears.
|
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.
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. For information about this job, see About checking the integrity of DVM repositories. For information on performing this job, see Performing an integrity check on a DVM repository. |
|
NOTE: Without removing existing recovery points, you cannot change repositories for a protected machine. |
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. |
This section describes how to configure and manage the replication of protected data from a Rapid Recovery source Core to a Rapid Recovery target Core for disaster recovery.
Topics include:
Replication with Rapid Recovery
Recovery point chains and orphans
Determining your seeding needs and strategy
Performance considerations for replicated data transfer
Viewing incoming and outgoing replication
Replicating to a self-managed target Core
Replicating to a third-party target Core
Adding a machine to existing replication
Consuming the seed drive on a target Core
Removing outgoing replication from the source Core
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center