Chat now with support
Chat with Support

Rapid Recovery 6.3 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings Managing privacy Encryption 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 Credentials Vault Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore BMR Windows and Linux 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 rollup for a protected machine

You can bypass your scheduled retention policy by forcing recovery points to roll up at the protected machine level.

  1. From the Protected Machines menu of the Rapid Recovery Core Console, click the name of a specific protected machine.

    The Summary page for the selection machine appears.

  2. Click the More drop-down menu at the top of the protected machine view, and then select [Retention Policy] Retention Policy.
    The Retention Policy page for the specified machine appears.
  3. Click Force Rollup.
  4. In the dialog box, click Yes to confirm.
    Rapid Recovery Core initiates rollup for this machine, regardless of the retention policy schedule.

Archiving

This section provides conceptual information about Rapid Recovery archives, including business cases for creating them, storage options, and uses. It also describes how to create a one-time archive, or how to create an archive that is continually updated on a schedule. Topics describe how to pause or edit scheduled archives, how to force or check an archive, and how to attach or import an archive.

Topics include:

Understanding archives

The Rapid Recovery Core saves snapshot data to the repository. While a repository can reside on different storage technologies (such as SAN, DAS, or NAS), the most critical performance factor is speed. Repositories use short-term (fast and more expensive) media. To prevent a repository from filling up quickly, the Core enforces a retention policy, which over time rolls up recovery points and eventually replaces them with newer backup data.

If you need to retain recovery points, whether for historical significance, legal compliance, to fulfill offsite data storage policies, or other reasons, you can create an archive. An archive is a copy of recovery points from your repository for the specified machines over a date range that you designate. Archiving a set of recovery points does not delete the original recovery points in your repository. Instead, the archive freezes the collection of recovery points at the point in time in which the archive was created, as a separate copy in a storage location that you specify. Unlike recovery points in your repository, the data in an archive are not subject to rollup.

You can create, import, and attach archives from the [Archives] Archive option on the button bar, or from the Archives page accessible from the [Archive] (More) icon on the Core Console.

Related topics:

Archive creation and storage options

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

You can also define requirements for continual scheduled 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 about defining a cloud account in the Core, see Adding a cloud account.

If storing your archive in an Amazon cloud storage account, you must define the storage class when creating the account. To archive directly to Amazon Glacier, you can specify Glacier storage when defining the location in the Archive Wizard. For more information about Amazon storage classes, see Amazon storage options and archiving.

  • 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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating