Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings Repositories Encryption keys Protecting machines
About protecting machines with Rapid Recovery Support for dynamic and basic volumes 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 Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Viewing the recovery progress Starting a restored target server Troubleshooting connections to the Universal Recovery Console Repairing boot problems Performing a file system check on the restored volume
Managing aging data Archiving Cloud storage accounts The Local Mount Utility The Central Management Console Core Console references Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Scripting REST APIs About us Glossary

Archive creation and storage options

You can create a one-time archive on demand at any time.

You can also define requirements for continual archive. This action creates an archive of recovery points for the machines you select, in the location you designate. Additional recovery points for those machines are then continually appended to the archive on a schedule you define (on a daily, weekly, or monthly basis).

When you create an archive, you specify where you want to save it. You can store an archive in a file system (locally or on a network), or in a storage account in the cloud.

* 
NOTE: Before archiving to a cloud account, you must first add the credentials to the storage account on your Rapid Recovery Core. For more information on defining a cloud account in the Core, see Adding a cloud account.
•
One-time archives are read-only. When creating a one-time archive, the destination location you specify must be empty.
•
When using scheduled archive, the Core appends additional recovery points to the existing archive.
•
If the storage medium you selected runs out of space, Rapid Recovery pauses the archive job, letting you specify another location. Your archive is then split into segments, which can reside in different locations, as space allows.
Adding a cloud account

Recovery point chain options for archives

Before creating your archive, you must decide on the proper approach for recovery point chains. Use the following information to determine which option you select in the Options page of the Archive Wizard.

•
Build complete recovery point chains, including referenced base images outside the date range. If you select the option to build complete recovery point chains, then you can perform the full range of restore actions for any recovery point in the archive. This range includes file-level restore, volume-level restore, and bare metal restore. When you select this option, full recovery point chains are saved with your archive. You can restore data even if the base image corresponding to the selected recovery point is earlier than the date range of your archive. However, the file size of this archive is larger, to ensure that you have access to data in the full recovery point chain.
•
Include only the recovery points in the date range. This saves space, but you are responsible for archiving any needed base images. If you include only the recovery points in the specified date range in your archive, the file size of the archive is smaller. For data in which the base image is included in the date range you specified, you have access to the full range of restore options. However, if you want to recover data captured in a base image from a date earlier than the date range you specified, you may be restricted to file-level recovery only. Data outside the range of the archive is orphaned.

For more information on recovery point chains, see the topic Recovery point chains and orphans.

Related concepts 
Recovery point chains and orphans
Related tasks 
Creating an archive
Editing a scheduled archive

Methods to access an archive

When you need to access the data in an archived recovery point, you have two options.

•
For archives created with Rapid Recovery version 6.0.1 and later, you can attach the archive. The attached archive is displayed in the left navigation menu of the Core Console. You can browse the recovery points in the archive, and take the same actions on that data as with any other recovery points currently in your repository, without importing that data into your repository.
•
You can import an archive, restoring those recovery points to your repository. You can then take the same actions on that data as with any other recovery points currently in your Core. Rapid Recovery is backward compatible, supporting import of archives from all AppAssure and Rapid Recovery versions.
* 
CAUTION: Since the Core recognizes the original dates of recovery points in an archive, recovery points imported from an archive may be rolled up or deleted during the next nightly job period, if their age exceeds the retention period. If you want to retain older recovery points, you can disable rollup or extend the retention period for the relevant protected machines.

When you need to access the data in an archived recovery point, you can attach (for Rapid Recovery 6.x and later) or import the archive, restoring those recovery points to your repository.

Related tasks 
Attaching an archive
Importing an archive

Uses for archives

Once an archive is created, it can be used in the following ways:

•
An archive can be attached to the Core Console, and mounted as a file system for simple file or folder recovery. Some restrictions apply.
•
An archive can be imported into a repository, restoring its recovery points if they have been rolled up or deleted.
•
An archive can be used as the source for a bare metal restore.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating