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

Adding a storage location to an existing DVM repository

Adding a storage location to a DVM repository lets you define where you want the repository or volume to be stored.

Complete the steps in the following procedure to specify the storage location for the repository or volume.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [More] (More), and then select Repositories.

    The Repositories page appears.

    The DVM Repositories pane appears.

  3. In the repositories summary table, from the row representing the DVM repository for which you want to add a storage location, click Settings and select Add Storage Location.

    The Add Storage Location dialog box displays.

  4. Specify how to add the file for the storage location. You can choose to add the file on the local disk or on a CIFS share.
    • Select Add file on local disk to specify a local machine and then enter the information as described in the following table.
      Table 1. Local disk settings
      Text Box Description
      Data Path Enter the location for storing the protected data.

      For example, type X:\Repository\Data.

      The same limitations to the path apply; use only alphanumeric characters, hyphen, or period, with no spaces or special characters.

      Metadata Path Enter the location for storing the protected metadata.

      For example, type X:\Repository\Metadata.

      When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

    • Or, select Add file on CIFS share to specify a network share location and then enter the information as described in the following table.
      Table 2. CIFS share credentials
      Text Box Description
      UNC Path Enter the path for the network share location.

      If this location is at the root, define a dedicated folder name (for example, Repository).

      The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

      User Name Specify a user name for accessing the network share location.
      Password Specify a password for accessing the network share location.
  5. In the Storage Configuration pane, click More Details and enter the details for the storage location as described in the following table.
    Table 3. Storage location details
    Text Box Description
    Size Set the size or capacity for the storage location.The default size is 250 GB. You can choose from the following:
    • GB
    • TB
      Note: The minimum size is 1 GB. The size that you specify cannot exceed the size of the volume.

      If the storage location is a New Technology File System (NTFS) volume using Windows XP or Windows 7, the file size limit is 16 TB.

      If the storage location is a NTFS volume using Windows 8, 8.1 or Windows Server 2012, 2012 R2, the file size limit is 256 TB.

      Note: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.
    Write Caching Policy The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations.

    Set the value to one of the following:

    • On
    • Off
    • Sync

      If set to On, which is the default, Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.

      Note: Setting the write caching policy to On could result in faster performance. If you are using Windows Server 2008 SP2 or Windows Server 2008 R2 SP2, the recommended setting is Off.

      If set to Off, Rapid Recovery controls the caching.

      If set to Sync, Windows controls the caching as well as the synchronous input/output.

    Bytes per Sector Specify the number of bytes you want each sector to include. The default value is 512.
    Average Bytes per Record Specify the average number of bytes per record. The default value is 8192.
  6. Optionally, if you want to perform the repository optimization job for the selected repository, select Run Repository Optimization Job for [Repository name].

    Dell recommends performing the Repository Optimization Job when adding storage locations to an existing repository. This job optimizes the free space by applying deduplication to data stored in the repository.

    Based on factors such as the size of your repository, amount of data in your repository, available network bandwidth, and existing load on the input and output of your system, performing a Repository Optimization Job could take a substantial amount of time and bandwidth in your environment.

    For more information about the repository optimization job, see About the Repository Optimization Job.

  7. Click Save.

    The dialog box closes and the storage location is saved. In the repositories summary table, the storage location you created is visible if you expand the repository details.


Was this topic helpful?

[Select Rating]



About checking the integrity of DVM repositories

In AppAssure release 5.3.6 and earlier releases, replication included the process of copying recovery points from the source Core to the target Core regularly. Rollup of aging recovery points occurred only at the source Core. Combined older recovery points were synchronized daily when running the nightly job.

Starting with AppAssure version 5.4.1 and in current releases of Rapid Recovery Core, users can to set disparate retention policies between source and target Cores. For replication to work properly with different retention policies, the target Core must have the same software version (or newer) than the source Core.

Note: The Cores must share the same three digits for the release number (for example, both start with 6.0.1.xxxx, or 5.4.3.xxxx). The build number (represented by xxxx) can be different only if the target Core is newer.

Administrators can now configure rollup on a target Core at a different rate than on the source Core. Similarly, you can now define a custom retention policy for any replicated machine. For example, you can roll up recovery points in the target Core at a faster rate and with less granularity than on the source Core, saving space. Or you can roll up recovery points for any selected replicated machine at a slower rate in the target Core, maintaining more granularity, which may be useful for compliance purposes. For more information on using a retention policy that differs from the default in the Core, see Customizing retention policy settings for a protected machine.

Some customers experienced inconsistencies in recovery points that were replicated to a target Core prior to AppAssure release 5.3.6. To address this issue, AppAssure release 5.4.1 and later include a Core job to run on each DVM repository. Dell recommends performing this job a single time on each DVM repository on a replicated target Core if the repository was created prior to release 5.4.x (if it was created in release 5.3.x or earlier).

Note: In AppAssure Core versions, this job was called Integrity Check job. In Rapid Recovery Core this job is named Check Repository Job.

For instructions on how to perform this check, see the procedure Running the Check Repository Job on a DVM repository.

You do not need to run this job:

  • On a new DVM repository on a target Core created in AppAssure release 5.4.1 or later or created in Rapid Recovery.
  • On a source Core.
  • If you have already run the Integrity Check Job (or Check Repository Job) on this repository.
  • If you have not used replication.

If your Core has been upgraded at any point from AppAssure 5.3.x and you used replication, you must run this job before you can configure dissimilar retention policies between the source Core and a target Core, or configure a custom retention policy on a replicated machine.

You will not see or be able to run this job unless you have one or more eligible repositories (created prior to 5.4.x and not yet performed).

Running this job verifies the integrity of all data stored in the specified repository, ensuring you can recover data from each snapshot or base image. If the integrity check discovers any issue with data in your repository, the job ceases immediately. The event details for that job on the Core prompt you to contact Dell Rapid Recovery Support, so you can schedule time to work with a Dell representative to perform additional procedures to identify and remediate data inconsistencies.

CAUTION:
Running this job is expected to take an extended period of time. The amount of time differs based on the amount and type of data in your repository, and on the underlying storage system. While the job is running, no other transactions can be performed in that repository, including transfers (snapshot and base image backups, and replication), nightly jobs, and so on.

You can perform other operations in other repositories while this job is running.

Note: This job checks the integrity of all of the contents within a repository. For information about the Integrity Check job, which you can use to ensure that a repository is mountable and usable, see Checking a repository.

Was this topic helpful?

[Select Rating]



Running the Check Repository Job on a DVM repository

Perform this procedure to check the integrity of an entire DVM repository. This is recommended for replicated target cores when upgrading from AppAssure 5.3.x to release 5.4. During the execution of the integrity check, which can be lengthy, no other actions can be performed in the repository.

If you have multiple DVM repositories for a target Core, perform this process once for each repository.

Note: If you have another DVM repository on the target Core for which the Integrity Check job has already been completed, or if you create a new additional repository for this target Core, you can perform operations in that secondary repository while the integrity check job is running on the DVM repository you specified.
  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [More] (More), and then select Repositories..

    The Repositories page appears.

    The DVM Repositories pane appears.

  3. In the repositories summary table, from the row representing the repository you want to check, click [Actions] and from the drop-down menu, select Check Repository Job.

    A confirmation message appears.

    CAUTION:
    Before you confirm that you want to perform the job, you should carefully consider the duration of time required. While the job is running, no other transactions can be performed in that repository, including transfers (snapshot and base image backups, and replication), nightly jobs, and so on.
  4. From the Check Repository Job dialog box, to perform the integrity check, click Yes.

    The dialog box closes. Any jobs that were queued or that are in progress are canceled, and the integrity check job begins.

  5. To monitor the progress of the Check Repository Job for a repository, including a determination of whether additional steps are required after the check, from the icon bar, click [Events] (Events).
  6. From the Events page, click [Job Details] Job Details for the job to view more information about the job status.
    • If you see an error in any child tasks for this job, note the error and provide the information to a Dell technical support representative.
    • If the Check Repository Job completes all child tasks successfully, you can then establish a custom retention policy for this repository.

Was this topic helpful?

[Select Rating]



Checking a repository

Rapid Recovery lets you perform a diagnostic check of a DVM repository volume when errors occur. Core errors could be the result of it being improperly shut down, a hardware failure, or other environmental, lower IP stack factors that can be exposed in Rapid Recovery functionality.

Note: This procedure should only be performed for diagnostic purposes. For example, run this check in the event of hardware failure, improper shutdown of the Core, or failure when importing a repository.
  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [More] (More), and then select Repositories.

    The Repositories page appears.

    The DVM Repositories pane appears.

  3. To check a DVM repository, in the DVM Repositories pane, in any row of the summary table representing a DVM repository, click [Actions] and then select Check.
    The Check Repository dialog box appears.
  4. In the Check Repository dialog box, confirm that you understand that all active tasks associated with this repository will be canceled and that you want to proceed.
    Active jobs are canceled and the Check Repository Job starts.
  5. Optionally, can you track the status of the job by clicking the Running tasks drop-down menu in the button bar, and selecting the Maintaining repository job.

Was this topic helpful?

[Select Rating]



Related Documents