Chat now with support
Chat with Support

Rapid Recovery 6.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings
Core settings key functions Rapid Recovery Core settings Core-level tools
Repositories 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 Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines 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 The Local Mount Utility Core Console references REST APIs About us Glossary

Understanding nightly jobs

Nightly jobs are daily automated tasks that occur at a predetermined time outside of normal business hours. These jobs are memory-intensive, and include various integrity checks and data consolidation tasks that are best conducted when the Rapid Recovery Core is less active.

All the nightly jobs, and the scope for which they can be applied, are described in the following table. Nightly jobs can be managed at the Core level (which applies to all machines protected on the Core). Those nightly jobs which can also be applied for a specific protected machine list the scope as "Protected machine."

Table 10. Nightly jobs information

Job Name

Scope

Description

[Change] Change

N/A

This control opens the Nightly Jobs dialog box, where you can enable, disable, or change settings for each nightly job.

Nightly jobs time

All

This setting represents the time that nightly jobs are scheduled to start running. Quest recommends configuring your Core to run nightly jobs during a time of low activity.

The default time is 12:00 AM.

Check attachability of SQL databases

Protected machine

Checks the integrity of recovery points containing SQL databases. For more information, see Managing Core SQL attachability settings.

Check checksum of Exchange databases

Protected machine

Checks the integrity of recovery points containing Exchange Database (EDB) files.

Check integrity of Oracle databases

Core or protected machine

Checks the integrity of Oracle databases using the DBVERIFY utility.

Process:

Check integrity of recovery points

Core or protected machine

Checks the integrity of recovery points for each protected machine. By default, the Check integrity of recovery points option is not enabled.

Process:

Clean orphaned registry keys on Hyper-V agents

For Hyper-V hosts using Rapid Recovery release 6.1.x agentless protection, this nightly job cleans orphaned keys made in the Windows registry for each attach and detach operation. The registry entries are harmless, but over time can accumulate, leading to slower performance.

NOTE: As of Rapid Recovery release 6.2, an improved approach to obtaining storage metadata for Hyper-V agentless protection precludes creating registry entries.

Consolidate VMware snapshots for protected virtual machines

Core or protected machine

This nightly job is relevant if you use native VMware APIs to protect machines without the Rapid Recovery Agent software.

You should periodically consolidate VMware snapshots. Enabling this nightly job lets you perform these consolidations on a daily basis. This nightly job contains one parameter, Maximum simultaneous consolidations, which must be set to a number between 1 and 100.

Deferred Delete

Core

This setting lets you defer removal of recovery points from the repository until the time specified in your Core to perform nightly jobs. When enabled, then after other nightly jobs run, Core processing is dedicated to running the "Deleting records previously flagged for deletion" job. That job removes marked recovery points from the repository until they are all removed, or until four hours have passed from the nightly jobs execution time. Nightly jobs then end, and other queued jobs resume. Any remaining deletions occur in the background, concurrent with other tasks, until the next day's nightly jobs run.

By default, the Deferred Delete option is not enabled.

Quest recommends leaving this nightly job disabled unless you are encountering transfer performance issues related to backed-up recovery point deletions.

If you enable this option, Quest recommends reviewing your Core jobs to ensure most recovery points marked for deletion are removed from the repository within a one-week period. This approach helps to balance maximum transfer performance with maximum reclamation of repository space.

Delete old events and jobs

Core

Maintains the scale of the events database by removing old events. The number of days is configurable, defaulting to 30 days.

Log truncation for Exchange

Protected machine

Maintains the size of Exchange logs by truncating the exchange database transaction log to match the last recovery point.

Log truncation for Oracle

Protected machine

Controls truncation for Oracle logs. Unless disabled, truncation occurs once daily when nightly jobs run.

You can follow the Core Automatic deletion policy (enabled by default), which truncates all locally stored Oracle logs when nightly jobs run. Logs for the current day still persist in the backup snapshots preceding running of the nightly job.
You can select a custom deletion policy for a specific protected Oracle server. The Keep newest policy lets you specify the duration of time before which Oracle logs are truncated, and the Keep specified number policy lets you keep a specified number of log files before truncating the older ones.

Log truncation for SQL

Protected machine

Maintains the size of SQL Server logs by truncating the database transaction log to match the last recovery point.

Rollup

Core or protected machine

Applies the retention policy to your backed-up data by combining or "rolling up" recovery points on the schedule dictated in the policy. You can customize the policy on the Core, which applies by default to all protected machines. By default, the rollup job is run for the whole Core; or click [Expand] [Expand] to expand the view of protected machines. You can then define the set of protected machines you want to roll up using the Core policy.

For more information about using a retention policy on a protected machine that differs from the default policy set in the Core, see Customizing retention policy settings for a protected machine.

Configuring nightly jobs for the Core

When any nightly job option is enabled on the Rapid Recovery Core, the selected job executes once daily at the time specified for all machines that are protected by the Core. Conversely, if you disable any nightly job at the Core level, the specified job no longer executes for all machines protected by the Core.

NOTE: If the scope of a nightly job, as described in the topic Understanding nightly jobs, includes protected machines, you can configure that nightly job to apply only for one or more specific protected machines individually. For more information about applying nightly job settings specific to a protected machine, see Customizing nightly jobs for a protected machine.

Because nightly jobs are memory-intensive, Quest recommends configuring your Core to execute them during a time of low activity. The default schedule to run nightly jobs is 12:00 am. If another time is more suitable, change this setting in the Nightly Jobs Time field using this procedure.

1.
Navigate to the Rapid Recovery Core Console.
Scroll down on the right side of the Settings page until you can see the Nightly Jobs heading.

The Nightly Jobs dialog box displays.

6.
Click OK.
The Nightly Jobs dialog box closes and your nightly jobs settings for the Core are saved.

Modifying transfer queue settings

Transfer queue settings are Core-level settings that establish the maximum number of concurrent transfers and the maximum number of retries for transferring data.

Complete the steps in this procedure to modify transfer queue settings.

1.
Navigate to the Rapid Recovery Core Console.

The setting you selected becomes editable.

Table 11. Transfer queue settings information

Text Box

Description

Maximum concurrent transfers

Enter a value to update the number of concurrent transfers.

Set a number from 1 to 60. The smaller the number, the lesser the load on network and other system resources. As the number of agents that are processed increases, so does the load on the system.

Maximum retries

Enter a value to set the maximum number of attempts before canceling the transfer operation.

Set a number from 1 to 60.

Adjusting client timeout settings

Client timeout settings control the length of time that various operations are attempted before the operation times out.

NOTE: Quest recommends leaving default timeout settings unless you experience specific issues in your environment, and you are advised by a Quest Support representative to modify the settings.

Complete the steps in this procedure to adjust client timeout settings.

1.
Navigate to the Rapid Recovery Core Console.

The setting you selected becomes editable.

5.

Table 12. Client timeout settings information

Setting

Description

Connection timeout

Controls the timeout for the connection between the Core and protected machines when sending data across the hypertext transfer protocol (http).

Enter the amount of time you want to lapse before a connection timeout occurs. Uses HH:MM:SS format.

Read/Write timeout

Controls the timeout for the connection between the Core and protected machines when reading or writing stream data across http. An example is receiving changed data blocks from a protected machine to the Core for an incremental snapshot.

Enter the amount of time you want to lapse before a timeout occurs during a read/write event. Uses HH:MM:SS format.

Connection UI timeout

Controls the timeout for the connection between the graphic user interface and the Rapid Recovery Core service across http.

Enter the amount of time you want to lapse before a connection UI timeout occurs. Uses HH:MM:SS format.

Read/Write UI timeout

Controls the timeout for the connection for reading and writing data streams between the graphic user interface and the Rapid Recovery Core service across http.

Enter the amount of time you want to lapse before a timeout occurs during read or write events. Uses HH:MM:SS format.

Related Documents