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

Backing up and restoring Core settings

You can back up Core setting information to a file, and later restore these settings if you have problems with the Core machine or if you want to migrate those settings to a different machine. Information that gets backed up includes repository metadata (such as the repository name, data path, and metadata path); machines protected in the Core; replication relationships (targets and sources); which machines are configured for virtual standby; and information about encryption keys.

This process restores the configuration settings only, not the data. Security information (such as authentication credentials) is not stored in the configuration file. There is no security risk to saving a Core configuration file.

Note: You must first back up Core setting information before you can use this process to restore Core settings.

Use this procedure to back up and restore Core settings.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings] (Settings).

    The Settings page appears. At the top of the Settings pane, above the categories of settings, you see two buttons, Back Up Settings and Restore Settings.

  3. If you want to back up Core settings, proceed to Step 4. If you want to restore Core settings, proceed to Step 6.
  4. To back up the current settings in an XML file, from the top of the Settings page, click Back Up Settings.

    The Back Up Core Configuration dialog box appears.

  5. In the Local path text box, type a directory path accessible locally to the Core machine where you want to store core settings as an XML file, and then click Back Up.

    For example, type C:\Users\Your_User_Name\Documents\AA5CoreSettings and then click Back Up.

    A file named AppRecoveryCoreConfigurationBackup.xml is saved to the local destination you specified.

  6. To restore Core settings from a backup XML file saved previously using this method, perform the following steps.
    Note: When you restore the Core configuration settings, the Rapid Recovery Core service restarts.
    1. From the top of the Settings page, click Restore.

      The Restore Core Configuration dialog box appears.

    2. In the local path text box, enter the local path of the location where you stored the core configuration settings.

      For example, type C:\Users\Your_User_Name\Documents\AA5CoreSettings.

    3. If you do not want to restore repository information, proceed to Step g.
    4. Optionally, if you want to restore repository information as configured in the backup file, select Restore Repositories and then click Restore.

      The Restore Repositories dialog box appears.

      If you choose to restore repository information from the backed-up configuration data, then any repositories configured when the Core settings were saved appear for verification. By default, each existing repository is selected.

    5. Verify the repository information you want to restore. If multiple repositories appear in the lists for verification, and you only wish to restore information for some of them, then clear the selection for each repository you do not want.
    6. When you are satisfied with the selection of repositories you want to restore, click Save.

      The Restore Repositories dialog box closes.

    7. In the Restore Repositories dialog box, click Restore.

      The Restore Repositories dialog box closes, and the restore process begins. An alert appears indicating that the repository service configuration has changed.

    8. If any configuration settings could not be restored you will see an error message. Review the details of the error to see if any action is required on your part. For more information, see Viewing events using tasks, alerts, and journal. To continue, click Close to clear the error dialog box.
    9. After restoring the configuration, verify the following:
      • Unlock all encryption keys. For more information, see Unlocking an encryption key.
      • If virtual standby is configured to continually update a VM to a network destination, you must specify the network credentials in the virtual standby settings before a successful synchronization. For more information, see Exporting protected data to virtual machines.
      • If scheduled archive is configured to archive to a cloud storage account, you must specify credentials so the Core can connect to the cloud account. For more information on linking the Core with a cloud storage account, see Adding a cloud account.
      • If replication is set up and you want to restore to a target Core, verify the target Core settings (particularly the host) on the source Core. For more information, if managing your own Core, see Replicating to a self-managed target Core. If replicating to a Core managed by a third party, see Replicating to a third-party target Core.
      • If the SQL attachability check is configured, and if the SQL Server instance performing the check is on the Core machine, then specify the SQL credentials in Attachability settings. For more information, see Managing Core SQL attachability settings.

        Verify that the Replay Engine configuration was restored, and update the settings if they were not to ensure effective communication. For more information, see Configuring Replay engine settings.


Was this topic helpful?

[Select Rating]



Understanding system information for the Core

Rapid Recovery lets you view information about the Rapid Recovery Core. You can view general information, information about local volumes, and information about mounted volumes.

In the General pane, you can see the information described in the following table.

Table 1. System information
UI Element Description
Host name The machine name of your Rapid Recovery Core.
OS version The version of the operating system installed on the Rapid Recovery Core.
OS architecture Lists the underlying structure and design of the machine hosting your Rapid Recovery Core. Potentially includes chipset and lists 64-bit system. Rapid Recovery Core supports 64-bit systems only.
Memory (physical) Lists the amount of Random Access Memory installed on the Core machine.
Display name Shows the display name of the Core, which is configurable (see Configuring Core general settings).
Fully qualified domain name Shows the fully qualified domain name for the Core machine.
Metadata cache location Shows the path of the metadata cache location.

For more information, see Understanding deduplication cache and storage locations.

Primary cache location Shows the path of the primary deduplication cache location.

For more information, see Understanding deduplication cache and storage locations.

Secondary cache location

Shows the path of the secondary deduplication cache location.

For more information, see Understanding deduplication cache and storage locations.

The Volumes pane includes the following information about storage volumes for the Core machine: Name, device ID, file system, raw capacity, formatted capacity, used capacity, and mount points.

The Replay Engine Connections pane displays detailed information about currently mounted recovery points. You can view the local end point, remote end point, mounted image agent ID, mounted image ID, and the mounted image display name. You can see if the mount is writable, view the authenticated user, bytes read, and bytes written.

You can dismount recovery points that are mounted locally on a Core from the Mounts page. For more information about dismounting recovery points, see Dismounting recovery points.

For more information, see Viewing system information for the Core.


Was this topic helpful?

[Select Rating]



Viewing system information for the Core

System information for the Core includes general information, information about local volumes, and information about mounted volumes for the Core. For a detailed description of the information available on this page, see Understanding system information for the Core.

Complete the steps in this procedure to view system information for the Core.

Note: You can also see system information for a specific protected machine. For more information, see Viewing system information for a protected machine.
  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [More] (More) and then click [System Information] System Information.

    The System information page appears.


Was this topic helpful?

[Select Rating]



Accessing Core logs

Information about various activities for the Rapid Recovery Core are saved to the Core log file. This file, AppRecovery.log, is stored by default in the path C:\ProgramData\AppRecovery\Logs.

Note: Depending on your settings, the AppRecovery directory may not be visible on the Rapid Recovery Core. To see this directory, you may need to change the Folder Options control panel to show hidden files, folders, and drives. If these settings include the option to hide extensions for known file types, the Core log file may appear as AppRecovery with no .log extension.

The core log includes information about completed Core jobs, connection failures, results of attempts on the part of the Core to contact the License Portal, and other information. Each statement stored in the Core log file is preceded by one of four qualifiers: INFO, DEBUG, ERROR, and WARN. These qualifiers help categorize the nature of information stored in the log when diagnosing an issue.

Note: Similarly, a log file is also stored on each protected machine containing information relating to its attempts at communicating with the Core. For more information about machine logs, see Accessing protected machine diagnostics.

The ability to access logs can be useful when troubleshooting an issue or working with Dell Rapid Recovery support. To access logs, see the following procedures:


Was this topic helpful?

[Select Rating]



Related Documents