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.
The Force Snapshot dialog appears.
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.
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.
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 windows appears.
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.