Users Guide
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 windows 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, Dell
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 on page 66.
For information on performing this job, see Running the Check Repository Job on a DVM repository on page 70.
1.
In the Rapid Recovery Core Console, pause protection for the protected machine or machines whose recovery points you
want to migrate. For more information, see Pausing and resuming protection on page 130.
2. Cancel all current operations for the protected machine or machines whose 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 on page
82.
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 on page 231.
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 on page 60.
● 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:
a. On the Core Console, click the protected machine in the navigation tree.
b. On the Summary page of the protected machine, click Settings.
c. On the Settings page, in the General pane, click the Repository drop-down list, and then select in the name of the
repository you created in Step 4.
232
Recovering data