Chat now with support
Chat with Support

Rapid Recovery 6.3 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings Managing privacy Encryption 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 Credentials Vault Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore BMR Windows and Linux 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

Managing report settings

You can generate reports for the Rapid Recovery Core or for protected machines. For information on the reports you can generate, see Reporting.

Complete the steps in this procedure to manage report settings for Core reports.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings]
    (Settings), and then do one of the following:
    • From the list of Core settings on the left side of the Settings page, click Reports.
    • Scroll down on the right side of the Settings page until you can see the Reports heading.

    The Reports Core settings appear. Report settings are described in the following table.

    Option Description
    Restore Default

    This option restores all report settings to the default settings. Defaults are listed below for each setting.

    Font

    This option controls the default font used for reports. The default typeface is Trebuchet MS. You can change this font to any typeface available to your system.

    Paper size

    This option controls the default paper size for printing reports. The default is letter. You can choose from the following paper sizes:

    • A3
    • A4
    • B4
    • Executive
    • Ledger
    • Legal
    • Letter
    • Tabloid
    Page orientation

    This option controls the page orientation for exported reports. The default orientation is Landscape. You can choose from the following layout options:

    • Landscape
    • Portrait
  3. To change any of the settings for Reports, click in the appropriate setting field.

    The setting field appears as a configurable drop-down menu.

  4. Click the drop-down menu, and select one of the values available.

    For example, in the Font field, click Times New Roman.

  5. For each setting, when satisfied with your changes, click [Check mark]
    to save the change and exit edit mode, or click [Cancel]
    to exit edit mode without saving.

    The option you selected now appears as the new setting for the selected Reports parameter.

Managing Core SQL attachability settings

SQL attachability checks occur as part of the Rapid Recovery nightly jobs. To ease licensing costs, Rapid Recovery gives you two options for performing attachability checks: using a licensed instance of SQL Server installed on the Rapid Recovery Core machine or using the instance of SQL Server already installed on your protected machine. This second option is now the default setting. However, if your protected machine is already exerted during the time when the nightly jobs occur, consider performing the checks with an instance of SQL Server on the Core.

The ability to perform attachability checks using the SQL Server instance on a protected machine is a function of the Rapid Recovery Agentsoftware. This feature does not work if the SQL Server is protected agentlessly. Therefore, if using agentless protection on the SQL machine, configure this Core setting to Use SQL Server on the Core, as shown in step 3 of this procedure.

In summary, the process of managing Core SQL attachability settings involves the following tasks:

  • Mount the latest recovery point for protection groups containing databases.
  • Connect to the database from SQL Server.
  • Open the database.
  • Close the database.
  • Dismount the recovery point.

    To enable this nightly check, specify a SQL Server instance to use to perform attachability checks for SQL Server databases on protected machines.

    NOTE: This option does not appear if you are not protecting a SQL Server in your Core.

To configure the Core to perform SQL attachability checks as part of the nightly jobs, complete the following steps.

NOTE: If you select the default option to use the instance of SQL Server installed on the protected machine, that SQL Server instance will manage SQL attachability for all protected SQL machines. If you do not want this setting to apply to all protected SQL machines, select Use SQL Server on the Core. To perform attachability checks on the Core, you must install or use a licensed version of SQL Server on the Core machine.

  1. Navigate to the Rapid Recovery Core Console.
  2. On the icon bar, click [Settings] 
    (Settings), and then do one of the following:
    • From the list of Core settings on the left side of the Settings page, click Attachability.
    • Scroll down on the right side of the Settings page until you can see the Attachability heading.
  3. To use the SQL Server instance installed on the protected SQL Server machine, select Use SQL Server on the protected machine. This is the default option.
  4. To use the SQL Server instance installed on the Rapid Recovery Core, select Use SQL Server on the Core, and then enter the authentication information as described in the following table.
    Table 29: SQL Server credentials information
    Text Box Description
    SQL Server From the SQL Server drop-down menu, select the appropriate SQL Server instance from the Core server.
    Credential Type Select the appropriate authentication method for your credentials from the following options:
    • Windows
    • SQL
    User Name Specify a user name for accessing the SQL Server on the Core based on your selected credential type.
    Password Specify a password for accessing the SQL Server on the Core based on your selected credential type.
  5. Click Test Connection.

    NOTE: If you entered the credentials incorrectly, a message displays to alert you that the credentials failed. Correct the credential information and test the connection again.

  6. After you are satisfied with your changes, click Apply.

Understanding Core jobs

Core jobs are processes that the Rapid Recovery Core performs to support its operations, including backing up to recovery points, replicating data, archiving data, exporting data to VMs, maintaining repositories, and so on. Core jobs are initiated automatically for some operations, such as replicating or archiving on an established schedule. You can also invoke some jobs on demand from various elements on the Core Console.

  • When viewing or editing Core job settings, each Core job has two parameters: Maximum concurrent jobs and Try count.
    • The Maximum concurrent jobs parameter determines how many jobs of that type can be run at the same time.
    • The Try count parameter determines how many times the job should be tried before abandoning the job, if network or other communication errors prevent the job from succeeding the first time.
  • In the Core Jobs table, the Settings column indicates if the job listed is included in Core job settings by default or must be explicitly added.

The following table describes the primary Core jobs available and their functions.

Table 30: Core jobs
Job Name Description Maximum Concurrent Jobs Try Count Settings

Check attachability of SQL databases in snapshots

Lets the Core check the consistency of SQL databases and ensures that all supporting MDF (data) and LDF (log) files are available in the backup snapshot. Process:

  • Mount the latest recovery point for protection groups containing SQL databases.
  • Mount the database. If performing attachability from the protected SQL server, mount using UNC path.
  • Connect to the database from SQL Server.
  • Perform the attachability check.
  • Perform cleanup operations.
  • Close the database.
  • Dismount the database.
  • Dismount the recovery point.

1

0

Default

Check checksum of Exchange databases

Checks the integrity of recovery points containing Exchange databases. Process:

  • Mount the latest recovery point for protection groups containing SQL databases.
  • Connect to the database from SQL Server.
  • Open the database.
  • Close the database.
  • Dismount the recovery point.

1

0

Default

Check mountability of Exchange databases

Checks that Exchange databases are mountable.

1

0

Default

Replicate protected machines data from remote source

Transfers a copy of recovery points for a protected machine from a source Core to a target Core. This job runs on the target Core receiving the incoming replicated recovery points.

3

0

Default

Replicate protected machines data to remote target

Transfers a copy of recovery points for a protected machine from a source Core (on which they were originally saved) to a target Core. This job runs on the source Core and controls outgoing replication.

1

3

Default

Roll up recovery points

Applies the retention policy to your backed-up data by combining or "rolling up" recovery points on the schedule defined in the retention policy.

1

0

Default

Check recovery points

Checks the integrity of recovery points.

1

0

Add

Delete all recovery points

Deletes the full set of recovery points on a protected machine.

1

0

Add

Delete chain of recovery points

Deletes a complete recovery point chain on a protected machine.

1

0

Add

Delete range of recovery points

Deletes a set of recovery points on a protected machine, by recovery point identifier or date range.

1

0

Add

Deploy Agent software to machines

Deploys Rapid Recovery Agent software to the specified machine or machines.

1

0

Add

Download Exchange libraries

Downloads Microsoft Exchange libraries from the protected machine to the Core machine at path C:\ProgramData\AppRecovery\ExchangeLibraries.

1

0

Add

Export to archive

Creates backup in the specified path with an archive of the selected recovery points. Process:

  • Mount recovery points.
  • Write data to backups.
  • Dismount the recovery point.

1

0

Add

Export to virtual machine

Exports data from specified recovery point of protected machine to destination path as a virtual machine. Process:

  • Mount recovery point.
  • Create virtual machine from the recovery point data in the destination path.
  • Dismount the recovery point.

1

0

Add

Import archives

Imports recovery point from the specified backup on a previously created Core archive.

1

0

Add

Maintain repository

Performs a check of the repository. Process:

  • Check repository file system.
  • Mount recovery point.
  • Recalculate deduplication cache for repository.
  • Load recovery points from repository.

1

0

Add

Mount recovery point snapshots

Performs mount of recovery point to the specified path.

1

0

Add

Protect ESX virtual machines

Adds all specified virtual machines to agentless protection.

Job is performed immediately after adding agentless protection of one or more VMs to the Core using the Protect Multiple Machines Wizard.

Job sets ID number for each specified VM, writes information about the Core to a configuration file, and retrieves metadata from the file.

1

0

Add

Restore from recovery point

Performs a restore from a recovery point to a specified target machine. Process:

  • Mount recovery point.
  • Write all data from the recovery point to the specified machine.
  • Dismount the recovery point.

1

0

Add

Uploading logs

Uploads logs to specified server.

1

0

Add

Some Core jobs are included in Settings. The Jobs settings let you specify how many concurrent jobs of the same type the Core can run, and how many retries should be attempted if the first job attempt fails.

For more information about these Settings, see Core job settings.

For information on adding jobs to Core Settings, see Adding Core jobs to settings.

For information on editing settings for jobs in the Settings list, see Editing Core job settings.

Core job settings

When you select [Settings]
    (Settings) from the icon bar, you can access settings for some Core jobs. The Jobs area on the Core settings page lets you determine two settings for each job type listed:

  1. The maximum number of jobs of this type for the Core to attempt at one time. This must be set to a value between 1 to 50.
  2. The number of times a job should be attempted if a network or other communication error prevents the job from succeeding the first time. This must be set to a value between 0 to 10.

Several jobs are automatically included in Core settings. These jobs include a value of "Default" in the Settings column (as shown in the topic Understanding Core jobs).

You can add some other jobs to settings if you want to configure those settings to control the maximum number of jobs or retries for those functions. These jobs include a value of "Add" in the Settings column. For information on how to add these jobs to the Settings table, see Adding Core jobs to settings.

Core jobs not available in Settings do not provide the ability to set these two parameters.

For jobs that are listed in settings, you can edit existing settings. This lets you customize the two parameters, delete a job type from the job settings list, or restore default settings. For detailed information, see the topic Editing Core job settings.

Related Documents