Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Rapid Recovery 6.0.2 - User Guide

*** Legend Introduction to Dell Data Protection | Rapid Recovery Understanding the Rapid Recovery Core Console Working with repositories Managing Rapid Recovery Core settings Using custom groups Working with encryption keys Protecting machines using the Rapid Recovery Core Working with Microsoft Exchange and SQL Servers Protecting server clusters Exporting protected data to virtual machines Managing protected machines Understanding replication Managing events Generating and viewing reports Restoring data Understanding bare metal restore for Windows machines Retention and archiving Managing cloud accounts Working with Linux machines Understanding the Local Mount Utility Central Management Console Understanding the Rapid Recovery Command Line Management utility Understanding the Rapid Recovery PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Extending Rapid Recovery jobs using scripting Rapid Recovery 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. Typically, each protected machine uses the default 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 Integrity Check 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 Running the Check Repository Job 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 selection machine appears.

  2. Click the Settings menu.

    The Settings page appears, 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 appears.

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

    The Configuration dialog box for the retention policy appears.

  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 the next step.
    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 Check Integrity job completes all child job successfully, return to this procedure and continue with the next step.
  7. In the Configuration 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 agent.
    • To define a custom retention policy for this agent, select Use custom retention policy, and then continue with the next step.
    The Configuration dialog box expands to show custom retention policy information.
  8. Enter the custom schedule for retaining the recovery points as described in the following table.
    Table 1. Schedule options for custom retention policy
    Text Box Description
    Keep all recovery points for n [retention time period] Specifies the retention period for the recovery points.

    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] Provides a more granular level of retention. It is used as a building block with the primary setting to further define how long recovery points are maintained.

    Enter a number to represent the retention period and then select the time period. The default is 2 days.

    You can choose from: Days, Weeks, Months, and Years

    …and then keep one recovery point per day for n [retention time period] Provides a more granular level of retention. It is used as a building block to further define how long recovery points are maintained.

    Enter a number to represent the retention period and then select the time period. The default is 4 days.

    You can choose from: Days, Weeks, Months, and Years

    …and then keep one recovery point per week for n [retention time period] Provides a more granular level of retention. It is used as a building block to further define how long recovery points are maintained.

    Enter a number to represent the retention period and then select the time period. The default is 3 weeks.

    You can choose from: Weeks, Months, and Years

    …and then keep one recovery point per month for n [retention time period] Provides a more granular level of retention. It is used as a building block to further define how long recovery points are maintained.

    Enter a number to represent the retention period and then select the time period. The default is 2 months.

    You can choose from: Months and Years

    …and then keep one recovery point per year for n [retention time period] Enter a number to represent the retention period and then select the time period.

    You can choose from: Years

    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.

Was this topic helpful?

[Select Rating]



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.
    The Retention Policy page for the specified machine appears.
  3. Click Force Rollup.
  4. In the dialog box, click Yes to confirm.
    Rapid Recovery initiates rollup for this machine, regardless of the retention policy schedule.

Was this topic helpful?

[Select Rating]



Understanding archives

Retention policies enforce the periods for which backups are stored on short-term (fast and expensive) media. Sometimes certain business and technical requirements mandate extended retention of these backups, but use of fast storage is cost prohibitive. Therefore, this requirement creates a need for long-term (slow and cheap) storage. Businesses often use long-term storage for archiving both compliance and non-compliance data. The archive feature in Rapid Recovery is used to support the extended retention for compliance and non-compliance data; and it is also used to seed replication data to a remote replica core.

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

  • An archive can be mounted as a file system for simple file or folder recovery.
  • An archive can be used as the source for a bare metal restore.
  • An archive can be imported into a repository.

Was this topic helpful?

[Select Rating]



Attaching an archive

Attaching an archive lets you see recovery points from the archive.

You must have a pre-existing archive created in Rapid Recovery Core 6.0.1 or later to complete this procedure. For more information, see Creating an archive.

When you attach an archive, the archive name you provide appears as an archive menu in the left navigation menu of the Core Console. Each protected machine with recovery points in the archive is listed separately below the archive menu. You can click any machine name in the archive and browse its recovery points. You can then take the same actions as with any other recovery points currently visible in your Core.

Attaching the archive also caches the credentials for accessing the information. Until you delete the attached archive definition, you can easily re-attach and detach the archive, making its recovery points easily accessible.

Use this procedure to attach an archive.
  1. On the Rapid Recovery Core Console, click the Archive drop-down menu, and then select Attach Archive.
    The Attach Archive dialog box appears.
  2. In the Name text box, enter a name for this attached archive.

    The value you type in this field appears in the left navigation menu as the archive menu name.

    Following best practice for display names, the archive name should contain between 1 and 64 alphanumeric characters, including spaces. Do not use prohibited characters. or prohibited phrases.

  3. In the Location type drop-down list, select the location type of your archive from the following options:
    • Local
    • Network
    • Cloud
  4. Enter the details for the archive as described in the following table based on the location type you selected in Step 3.
    Table 1. Location type details
    Option Text Box Description
    Local Location Enter the path to the archive; for example, D:\Work\Archive.
    Network Location Enter the path to the archive; for example, \\servername\sharename.
    User name Enter user name for logging in to the network share.
    Password Enter the password for logging in to the network share.
    Cloud Account Select an account from the drop-down list.
    Note: To select a cloud account, you must first have added it in the Core Console. For more information, see Adding a cloud account.
    Container Select the container of the archive associated with your account from the drop-down menu.
    Folder name Enter the name of the folder of the archived data; for example, Rapid-Recovery-Archive-[DATE CREATED]-[TIME CREATED].
  5. Click Attach.
    The archive attaches to this Core and mounts the contents as a file system.

Was this topic helpful?

[Select Rating]



Related Documents