Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Rapid Recovery 6.9 - 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 Authentication 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

Restoring clusters and cluster nodes

A restore is the process of restoring the volumes on a machine from recovery points. For a server cluster, you perform a restore at the node, or machine, level. This section provides guidelines for performing a restore for cluster volumes.

Performing a restore for CCR and DAG (Exchange) clusters

Complete the steps in this procedure to perform a restore for CCR and DAG (Exchange) clusters.

  1. Turn off all nodes except one.
  2. Perform a restore using the standard Rapid Recovery procedure for the machine as described in About restoring volumes from a recovery point and Restoring volumes for a Linux machine using the command line.
  3. When the restore is finished, mount all databases for the cluster volumes.
  4. Turn on all other nodes.
  5. For Exchange, navigate to the Exchange Management Console, and, for each database, perform the Update Database Copy operation.

Performing a restore for SCC (Exchange, SQL) clusters

Complete the steps in this procedure to perform a restore for SCC (Exchange, SQL) clusters.

  1. Turn off all nodes except one.
  2. Perform a restore using the standard Rapid Recovery procedure for the machine as described in About restoring volumes from a recovery point and Restoring volumes for a Linux machine using the command line.
  3. After the restore is finished, mount all databases from the cluster volumes.
  4. Turn on all other nodes one-by-one.

    NOTE: You do not need to roll back the quorum disk. It can be regenerated automatically or by using cluster service functionality.

Restoring from an attached archive

There are two ways you can restore data from an archive: You can use an archive as a source for a bare metal restore (BMR); or you can attach an archive, mount a recovery point from the archive, and then restore the archived data.

When you attach an archive, it appears under Attached Archives on the Archives page of the Core Console, while the contents of the archive become accessible from the left navigation area. The contents appear under the name of the archive. Machines that were archived appear as recovery-points-only machines so that you can access the recovery points in the same way that you would for a currently protected machine: by mounting a recovery point, locating the item that you want to recover, and using Windows Explorer to copy and paste the item to your destination.

There are advantages to restoring from an attached archive rather than importing an archive to a repository.

  • Restoring from an attached archive saves the time you may spend importing an entire archive to a repository.
  • Also, when you import an archive, the archived recovery points are added to the repository.
    Because these archived recovery points are likely the oldest items in the repository, they may be rolled up according to your retention policy during the next nightly job. (Although, this action does not delete them from the archive; you could re-import them the next day.)
  • Lastly, the Core remembers the attachment association with archives, even after you detach an archive, making it easier and faster to attach the archive again later.

    You can remove the association by deleting the attachment.

To restore data from an attached archive, complete the following steps using the related links:

NOTE: The procedure for restoring from an attached archive assumes that you already have an archive of rolled-up recovery points.

  1. Attach the archive.
  2. Mount the recovery point that contains the data that you want to recover.
  3. Restore data using any of the following methods:
    • Restore data, such as file or folder, from the recovery point.
    • Restore the entire recovery point.
    • Export the recovery point to a virtual machine.

For more information, see the following related topics:

Mail Restore in Rapid Recovery

The Mail Restore feature in Rapid Recovery lets you restore a mailbox, folder, or item — such as a message, calendar event, or contact — from the data store of a protected Exchange Server machine. You can restore your selection to a recovery folder, to the original source, or to one or more PST files.

You can access the Mail Restore page from the [More] (More) menu of the Rapid Recovery Core Console. From there, you can complete the following actions:

  • Open an Exchange database
  • Restore an item from the open database
  • Close the database
  • Search for an item in the open database

For more information, see Opening an Exchange database in Rapid Recovery Core and Restoring a mail item in Rapid Recovery.

Mail Restore prerequisites

Before you can restore mail items, you must meet the following prerequisites:

  • Outlook 2007 or later is installed on the Core machine.
  • There is at least one profile configured in Microsoft Outlook.
  • The Outlook profile has full-control permissions, including Send As and Receive As permissions. For more information, see Granting the required permissions in Microsoft Exchange Server.
  • The Outlook Cached Exchange Mode option under the Outlook profile associated with Rapid Recovery is disabled.
  • The Core machine is in the same domain as the Exchange database.
  • The required Exchange database is open and you are on the Mail Restore page of the Rapid Recovery Core Console. For more information, see Opening an Exchange database in Rapid Recovery Core.

Without the proper permissions and an instance of Outlook installed on the Core machine, it is not possible to perform Exchange-item recovery, even if the Exchange server is protected by a Rapid Recovery Core.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation