지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Customizing retention policy settings for a protected machine

The retention policy for a protected machine specifies how long recovery points are stored in the repository. By default, each protected machine uses the retention policy established for the Core unless you specify a custom retention policy, as described in this procedure.

Starting with AppAssure version 5.4.1, Rapid Recovery includes the ability to set disparate retention policies between a protected machine on the source Core and the corresponding replicated machine on the target Core.

Use this procedure to define a custom retention policy for a protected machine, including a replicated machine.

NOTE: The following applies to environments upgrading from AppAssure release 5.3.x to release 5.4.1 or any version of Rapid Recovery Core. If you want to customize a retention policy for any replicated machine, first upgrade the source and target Cores to AppAssure Core release 5.4.1, and then perform the Checking Repository job on each repository in that target Core. Completing this job is likely to take a substantial amount of time, based on the size of your repository and the underlying storage system. For background information about this job, see About checking the integrity of DVM repositories. For information on how to perform this job, see Performing an integrity check on a DVM repository.

  1. From the Protected Machines menu of the Rapid Recovery Core Console, click the name of the machine that you want to modify.

    The Summary page for the selected machine displays.

  2. Click the Settings menu.

    The Settings page displays, showing configuration settings for the selected machine.

  3. Optionally, click the Nightly Jobs link to scroll down in the Settings page to view nightly jobs settings.
  4. Under the Nightly Jobs heading, click [Change] 
    Change.

    The Nightly Jobs dialog box displays.

  5. To specify the time intervals for retaining the backup data as needed, select Rollup and then click Settings.

    The Retention Policy dialog box displays.

  6. If customizing retention policies settings for a replicated machine, and if you see a caution notifying you to perform an Integrity Check on your repository, proceed with this step. Otherwise, skip to step 7.
    1. If you are prepared to perform the job, click Check Integrity
    2. Click Yes to confirm the Integrity Check job.

      NOTE: Running this job could take a substantial amount of time, based on the size of your repository. During this time, you can perform no other actions (snapshots, replication, virtual export, and so on) in the repository. For information about this job, see About checking the integrity of DVM repositories.

    Once the Checking Repository job completes all child jobs successfully, return to this procedure and continue with the next step.
  7. In the Retention Policy dialog box, do one of the following:
    • To use the default retention policy for this protected machine, select Use Core default retention policy, and then click Save. The default policy is applied to this protected machine.
    • To define a custom retention policy for this agent, select Use custom retention policy, and then continue with the next step.
    The Retention Policy dialog box expands to show custom retention policy information.
  8. Enter the custom 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.
    Table 152: Schedule options for custom 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 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, 3 months old.

  9. Click Save.

    The Retention Policy dialog box closes.

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

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

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:

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택