Chat now with support
Chat mit Support

Rapid Recovery 6.6 - User Guide

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

Managing aging data

This section describes how to manage aging snapshot data saved to your repository. It includes information about retaining recovery points in your repository, retention policies, and the resulting process of rolling up recovery points to conserve space.

This section also describes how to manage retention policies that control rollup, and how to force rollup on demand.

Topics include:

Data retention and archiving

Each time your Core captures a snapshot, the data is saved as a recovery point to your repository. Recovery points naturally accumulate over time. The Core uses a retention policy to determine how long snapshot data is retained in the repository. When nightly jobs run (specifically, during the rollup process), the Core enforces the retention policy to reduce the amount of storage space consumed. The date of each recovery point is compared to the date of the most recent recovery point. The Core then rolls up (combines) older recovery points. Over time, older recovery points in the repository are continually replaced with newer ones as the oldest recovery points eventually reach the oldest age defined in the retention period.

To keep recovery points that would otherwise be combined and eventually deleted, you can create an archive from the Core Console. An archive is a file containing a copy of the full set of recovery points for machines protected on your Core at the point in time in which it was created. You can later access archived information from the Core Console. In contrast with recovery points in the repository, recovery points in an archive do not get rolled up.

Archives are useful for maintaining compliance data; backing up your Core; seeding replication data to a remote replica Core; and for saving space in your Core for retaining recent business-critical transaction while maintaining backups for a longer period of time.

For more information about archives, see Archiving.

Managing retention policies

A retention policy is a set of rules that dictates the length of time for the Core to retain recovery points before starting to roll them up. Retention policies can be set to roll up based on hours, days, weeks, months and years. You can set up to six rules (the default policy sets five rules).

Since you can back up as frequently as every 5 minutes, the first rule in the retention policy typically sets how long to retain all recovery points. For example, if you back up a machine every quarter hour, 96 recovery points are saved to the repository for that machine per day, until rollup begins. Without managing your retention policy, that amount of data can quickly fill a repository.

NOTE: Administrators should note that frequent backups can have an impact on network traffic. Other factors affecting network traffic include other transfers (such as replication), the change rate of your data, and your network hardware, cables and switches.

The Core comes preset with a default retention policy. The default policy retains:

  • All recovery points for three days
  • One recovery point per hour for two days
  • One recovery point per day for four days
  • One recovery point per week for three weeks
  • One recovery point per month for two months
  • One recovery point per year for X years (disabled in default policy).

Following this default policy, the oldest recovery point is typically 92 days old. Data past that origination date for a default policy is deleted.

Setting the retention policy at the Core level applies automatically to all machines that the Core protects. You can change the default policy to suit your needs.

For any machine, you can also create a custom retention policy. Setting the policy at the machine level lets you specify a different retention policy than the default Core policy. For more information about configuring retention policies, see Configuring Core default retention policy settings and Customizing retention policy settings for a protected machine.

Configuring Core default retention policy settings

The retention policy for the Core specifies how long the recovery points for a protected machine are stored in the repository.

The Core retention policy is enforced by a rollup process which is performed as one component of running nightly jobs. Then, recovery points beyond the age specified in the retention policy are “rolled up” (combined) into fewer recovery points that cover a less granular period of time. Applying the retention policy on a nightly basis results in the ongoing rollup of aging backups. This eventually results in the deletion of the oldest recovery points, based on the requirements specified in that retention policy.

Different retention settings can be configured for source and target Cores.

NOTE: This topic is specific to customizing retention policy settings on the Rapid Recovery Core. When you save customized retention policy settings on the Core, you establish the default retention policy settings which can be applied to all machines protected by this Core. For more information on customizing retention policy settings for individual protected machines, see Customizing retention policy settings for a protected machine.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings] (Settings), and then do one of the following:
    • From the list of Core settings on the left side of the Settings page, click Nightly Jobs.
    • Scroll down on the right side of the Settings page until you can see the Nightly Jobs heading.

    The Nightly Jobs settings for the Core appear.

  3. Under Nightly Jobs, click [Change] Change.

    The Nightly Jobs dialog box displays.

  4. To specify the time intervals for retaining the backup data as needed, in the Nightly Jobs pane, select Rollup, and then click Settings.

    The Retention Policy dialog box for the Core default retention policy displays.

  5. To restore Core retention policy settings to the default values at any time, at the bottom of the dialog box, click Restore Defaults and then click Yes to confirm.

    All settings are restored to the default values described in the table in step 6.

  6. Enter the default schedule for retaining recovery points as described in the following table. The first setting specifies the primary retention period for all recovery points saved to the repository. Each additional setting, when enabled, provides a more granular level of retention by specifying the intervals between which recovery points should be rolled up. These settings define the duration for which recovery points are maintained.

    The retention policy options are described in the following table.

    Table 151: Schedule options for default retention policy
    Text Box Description

    Keep all recovery points for n [retention time period]…

    Specifies the primary retention period for all recovery points saved to the repository.

    Enter a number to represent the retention period and then select the time period. The default is 3 days. You can choose from days, weeks, months, and years.

    …and then keep one recovery point per hour for n [retention time period]

    If selected, this setting keeps one recovery point per hour for a time period that you specify. The default is 2 days. You can choose from days, weeks, months, and years.

    If you do not want to save at least one recovery point hourly, clear this option.

    …and then keep one recovery point per day for n [retention time period]

    If selected, this setting keeps one recovery point per day for a time period that you specify. The default is 4 days. You can choose from days, weeks, months, and years.

    If you do not want to save at least one recovery point daily, clear this option.

    …and then keep one recovery point per week for n [retention time period]

    If selected, this setting keeps one recovery point per week for a time period that you specify. The default is 3 weeks. You can choose from weeks, months, and years.

    If you do not want to save at least one recovery point weekly, clear this option.

    …and then keep one recovery point per month for n [retention time period]

    If selected, this setting keeps one recovery point per month for a time period that you specify. The default is 2 months. You can choose from months and years.

    If you do not want to save at least one recovery point monthly, clear this option.

    …and then keep one recovery point per year for n [retention time period]

    If selected, this setting keeps one recovery point per year for a number of years that you specify. The default (1 year) is disabled by default.

    If you do want to save at least one recovery point yearly, select this option and specify a number of years. If you do not want to save at least one recovery point yearly, clear this option.


    The oldest recovery point is determined by the retention policy settings.

    The following is an example of how the retention period is calculated.

    Keep all recovery points for three days.

    …and then keep one recovery point per hour for three days

    …and then keep one recovery point per day for four days

    …and then keep one recovery point per week for three weeks

    …and then keep one recovery point per month for two months

    …and then keep one recovery point per month for one year

    In this example, the oldest recovery point would be one year and three months old.

  7. When satisfied with your retention policy settings, click Save.

    The Retention Policy dialog box closes.

  8. In the Nightly Jobs dialog box, click OK.

    The Nightly Jobs dialog box closes. The retention policy you defined is applied during the nightly rollup.

    You can also to apply these settings when specifying the retention policy for any individual protected machine. For more information about setting retention policies for a protected machine, see Customizing retention policy settings for a protected machine.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen