A protection schedule defines when backups are transferred from protected agent machines to the Rapid Recovery Core.
The first backup transfer for any machine added to protection on the Core is called a base image snapshot. All data on all specified volumes (including the operating system, applications, and settings), are saved to the repository, which can take a significant amount of time depending on the amount of data being transferred. Thereafter, incremental snapshots (smaller backups, consisting only of data changed on the protected machine since the last backup) are saved to the repository regularly, based on the interval defined (for example, every 60 minutes). This type of backup contains less data than a base image, and therefore takes a shorter amount of time to transfer.
Protection schedules are initially defined using the Protect Machine Wizard or the Protect Multiple Machines Wizard. Using a wizard, you can customize protection schedules (choosing either periods or a daily protection time) to accommodate your business needs. You can then modify the existing schedule or create a new schedule at any time in the Protection Schedule dialog box from the summary page of a specific protected machine.
Rapid Recovery provides a default protection schedule, which includes a single period spanning all days of the week, with a single time period defined (from 12:00 AM to 11:59 PM). The default interval (the time period between snapshots) is 60 minutes. When you first enable protection, you also activate the schedule. Thus, using the default settings, regardless of the current time of day, the first backup will occur every hour, on the hour (12:00 AM, 1:00 AM, 2:00 AM, and so on).
Selecting periods lets you view the default protection schedule and make adjustments accordingly. Selecting a daily protection time causes Rapid Recovery Core to back up the designated protected machines once daily at a time you specify.
You can customize the schedule to define peak and off-peak times using the weekday and weekend periods available. For example, if your protected machines are mostly in use on weekdays, you could decrease the interval for the weekday period to 20 minutes, resulting in three snapshots every hour. Or you can increase the interval for the weekend period from 60 minutes to 180 minutes, resulting in snapshots once every three hours when traffic is low.
Alternatively, you can change the default schedule to define peak and off-peak times daily. To do this, change the default start and end time to a smaller range of time (for example, 12:00 AM to 4:59 PM), and set an appropriate interval (for example, 20 minutes). This represents frequent backups during peak periods. You can then add an additional weekday time range for the remaining span of time (5:00 pm to 11:59 pm) and set an appropriate (presumably larger) interval (for example, 180 minutes). These settings define an off-peak period that includes 5:00 PM to midnight every day. This customization results in snapshots every three hours from 5:00 PM through 11:59 PM, and snapshots every 20 minutes from 12:00 AM until 4:59 PM.
When you modify or create a protection schedule using the Protection Schedule dialog box, Rapid Recovery gives you the option to save that schedule as a reusable template that you can then apply to other protected machines.
Other options in the protection wizards include setting a daily protection time. This results in a single backup daily at the period defined (the default setting is 12:00 PM).
When protecting one or multiple machines using a wizard, you can initially pause protection, which defines the protection schedule without protecting the machines. When you are ready to begin protecting your machines based on the established protection schedule, you must explicitly resume protection. For more information on resuming protection, see Pausing and resuming protection. Optionally, if you want to protect a machine immediately, you can force a snapshot. For more information, see Forcing a snapshot.
For more information, see Creating multiple protection schedule periods in Advanced Mode.
The protecting procedure requires the following tasks be completed before you begin:
This topic describes how to start protecting the data on a single machine that you specify using the Protect Machine Wizard. To protect multiple machines using one process simultaneously, see About protecting multiple machines.
|
NOTE: Unless using agentless protection on a VMware or ESXi host, or a Hyper-V host, the machine you want to protect must have the Rapid Recovery Agent software installed to be protected. You can choose to install the Agent software prior to this procedure, or you can deploy the software to the target machine as a part of completing the Protect Machine Wizard. For more information about agentless protection and its restrictions, see Understanding Rapid Snap for Virtual. |
For more information about installing the Agent software, see “Installing the Rapid Recovery Agent software” in the Rapid Recovery Installation and Upgrade Guide. If the Agent software is not installed prior to protecting a machine, you will not be able to select specific volumes for protection as part of this wizard. In this case, by default, all volumes on the agentlessly protected machine will be protected.
??Rapid Recovery supports the protection and recovery of machines configured with EISA partitions.
When you add protection, you need to define connection information such as the IP address and port, and provide credentials for the machine you want to protect. Optionally, you can provide a display name to appear in the Core Console instead of the IP address. If you change this, you will not see the IP address for the protected machine when you view details in the Core Console. You will also define the protection schedule for the machine.
The protection process includes optional steps you can access if you select an advanced configuration. Advanced options include repository functions and encryption. For example, you can specify which Rapid Recovery repository you want to use. You can also specify an existing encryption key (or add a new encryption key) to apply to the data saved to the Core for this machine. For more information about encryption keys, see Encryption.
The workflow of the protection wizard may differ slightly based on your environment. For example, if the Rapid Recovery Agent software is installed on the machine you want to protect, you will not be prompted to install it from the wizard. Likewise, if a repository already exists on the Core, you will not be prompted to create one.
|
Caution: Rapid Recovery does not support bare metal restores (BMRs) of Linux machines with ext2 boot partitions. Any BMR performed on a machine with this type of partition results in a machine that does not start. If you want to be able to perform a BMR on this machine in the future, you must convert any ext2 partitions to ext3 or ext4 before you begin protecting and backing up the machine. |
|
NOTE: If you have not yet create a repository, a dialog box alerts you that no repository was found and prompts you to create one. Clicking Yes opens the Create Repository wizard. For more information about repositories, see Repositories. |
The Protect Machine Wizard appears.
Optionally, if you do not wish to see the Welcome page for the Protect Machine Wizard in the future, select the option Skip this Welcome page the next time the wizard opens.
The Connection page appears.
Text Box | Description |
---|---|
Host | The host name or IP address of the machine that you want to protect. |
Port | The port number on which the Rapid Recovery Core communicates with the Agent on the machine.
The default port number for Windows machines is 8006. The default port number for Linux machines is 22 (SSH). |
User name |
The user name used to connect to this machine; for example, Administrator (or, if the machine is in a domain, [domain name]\Administrator). Enter the user name or, to use a set of credentials saved to Credentials Vault, use the drop-down list and select a user name. Optionally, to save your credentials to Credentials Vault, click the plus sign next to the text box. For more information, see Credentials Vault. |
Password | Enter the password used to connect to this machine, or select a set of credentials from the drop-down list, which are listed by user name. |
If the Install Agent page appears next in the Protect Machine Wizard, that means that Rapid Recovery does not detect the Rapid Recovery Agent on the machine and will install the current version of the software. Go to step 6.
If the Upgrade Agent page appears next in the wizard, that means that an older version of the Agent software exists on the machine you want to protect.
|
NOTE: The Agent software must be installed on the machine you want to protect, and that machine must be restarted, before it can back up to the Core. To have the installer reboot the protected machine, select the option After installation, restart the machine automatically (recommended) before clicking Next. |
The Protection page appears.
You can enter up to 64 characters. Do not use the special characters described in the topic prohibited characters. Additionally, do not begin the display name with any of the character combinations described in the topic prohibited phrases.
With a default protection schedule, the Core will take snapshots of all volumes on the protected machine once every hour. To change the protection settings at any time after you close the wizard, including choosing which volumes to protect, go to the Summary page for the specific protected machine.
Schedule options are added to the wizard workflow.
The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) will transfer to the repository on the Rapid Recovery following the schedule you defined, unless you specified to initially pause protection.
|
NOTE: Typically, it is good practice to protect, at minimum, the System Reserved volume and the volume with the operating system (typically the C drive). |
If you already have repository information configured, did not indicate that you want to change the repository, and you selected the Advanced option in step 2, then the Encryption page appears. Proceed to step 16.
If you already have repository information configured, and you selected the Advanced option in step 2, or if you indicated you want to change the repository, then the Repository page appears. Proceed to step 13.
Text Box | Description |
---|---|
Name | Enter a name for the encryption key.
Encryption key names must contain between 1 and 64 alphanumeric characters. Do not use prohibited characters and prohibited phrases. |
Description | Enter a descriptive comment for the encryption key. This information appears in the Description field when viewing a list of encryption keys in the Rapid Recovery. Descriptions may contain up to 254 characters.
Best practice is to avoid using prohibited characters and prohibited phrases. |
Passphrase | Enter a passphrase used to control access.
Best practice is to avoid using prohibited characters. Record the passphrase in a secure location. Quest Data Protection Support cannot recover a passphrase. Once you create an encryption key and apply it to one or more protected machines, you cannot recover data if you lose the passphrase. |
Confirm passphrase | Re-enter the passphrase. It is used to confirm the passphrase entry. |
|
NOTE: This option is enabled by default, so if you do not want to encrypt data in this fashion, clear this option. |
|
NOTE: The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) transfers to the repository indicated in your Rapid Recovery Core following the schedule you defined, unless you specified that the Core should initially pause protection. For information on pausing and resuming protection, see Pausing and resuming protection. |
This topic describes how to add a cluster for protection in Rapid Recovery. When you add a cluster to protection, you need to specify the host name or IP address of the cluster, the cluster application, or one of the cluster nodes or machines that includes the Rapid Recovery Agent software.
|
NOTE: A repository is used to store the snapshots of data that are captured from your protected nodes. Before you start protecting data in your cluster, you should have set up at least one repository that is associated with your Rapid Recovery Core. |
For information about setting up repositories, see Understanding repositories.
The Protect Cluster Wizard opens.
Text Box | Description | ||
---|---|---|---|
Host | The host name or IP address of the cluster, the cluster application, or one of the cluster nodes. | ||
Port | The port number on the machine on which the Rapid Recovery Core communicates with the Agent.
The default port is 8006. | ||
User name | The user name of the domain administrator used to connect to this machine: for example, domain_name\administrator.
| ||
Password | The password used to connect to this machine. |
|
NOTE: If the cluster nodes already have an older version of the Rapid Recovery Agent installed, an Upgrade page appears in the wizard and offers the opportunity to upgrade the Agent. |
The system automatically verifies each machine you selected.
If the Protection page appears next in the Protect Cluster Wizard, skip to step 11.
If the Agent software is not yet deployed to the machines you want to protect, or if any of the machines you specified cannot be protected for another reason, then the selected machines appear on the Warnings page.
|
NOTE:Quest recommends this option. You must restart agent machines before they can be protected. |
The Protection page appears.
You can enter up to 64 characters. Do not use the special characters described in the topic prohibited characters. Additionally, do not begin the display name with any of the character combinations described in the topic prohibited phrases.
With a default protection schedule, the Core will take snapshots of all volumes on the protected machine once every hour. To change the protection settings at any time after you close the wizard, including choosing which volumes to protect, go to the Summary page for the specific protected machine.
You can enter up to 64 characters. Do not use the special characters described in the topic prohibited characters. Additionally, do not begin the display name with any of the character combinations described in the topic prohibited phrases.
With a default protection schedule, the Core will take snapshots of all volumes on the protected machine once every hour. To change the protection settings at any time after you close the wizard, including choosing which volumes to protect, go to the Summary page for the specific protected machine.
|
NOTE: Typically, it is good practice to protect, at minimum, the System Reserved volume and the volume with the operating system (typically the C drive). |
If you already have repository information configured, and you selected the Advanced option in step 1, then the Encryption page appears. Proceed to step 22.
The Encryption page appears. Skip to step 22 to optionally define encryption.
If you want to create a repository, then on the Repository page, enter the information described in the following table, and then click Next or Finish, as appropriate.Text Box | Description | ||
---|---|---|---|
Name | Enter the display name of the repository.
By default, this text box consists of the word Repository and a number, which corresponds to the number of repositories for this Core. For example, if this is the first repository, the default name is Repository 1. Change the name as needed. Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases. | ||
Location | Enter the location for storing the protected data. This volume should be a primary storage location. The location could be local (a drive on the Core machine) or it could be a CIFS share network drive.
For a CIFS share, 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.
For example, type When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted. | ||
User name | Enter a user name for a user with administrative access. This information is only required when the repository location specified is a network path. | ||
Password | Enter the password for the user with administrative access. This information is only required when the repository location specified is a network path. | ||
Metadata path | Enter the location for storing the protected metadata.
For example, type When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted. |
Text Box | Description | ||
---|---|---|---|
Bytes per sector |
Specify the number of bytes you want each sector to include. The default value is 512.
| ||
Bytes per record |
Specify the average number of bytes per record. The default value is 8192. | ||
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. As of release 6.4, the default for this setting is Off. Set the value to one of the following:
|
If you chose the Advanced option in Step 1, the Encryption page appears.
Text Box | Description |
---|---|
Name | Enter a name for the encryption key.
Encryption key names must contain between 1 and 64 alphanumeric characters. Do not use prohibited characters or prohibited phrases. |
Description | Enter a descriptive comment for the encryption key. This information appears in the Description field when viewing a list of encryption keys in the Rapid Recovery. Descriptions may contain up to 254 characters.
Best practice is to avoid using prohibited characters and prohibited phrases. |
Passphrase | Enter a passphrase used to control access.
Best practice is to avoid using prohibited characters. Record the passphrase in a secure location. Quest Data Protection Support cannot recover a passphrase. Once you create an encryption key and apply it to one or more protected machines, you cannot recover data if you lose the passphrase. |
Confirm passphrase | Re-enter the passphrase. It is used to confirm the passphrase entry. |
|
NOTE: The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) transfers to the repository indicated in your Rapid Recovery Core following the schedule you defined, unless you specified that the Core should initially pause protection. For information on pausing and resuming protection, see Pausing and resuming protection. |
This task requires that you first protect a cluster. For more information, see Protecting a cluster.
This topic describes how to protect the data on a cluster node or machine that has a Rapid Recovery Agent installed. This procedure lets you add individual nodes to protection that you may have omitted when you protected a cluster.
Text Box | Description |
---|---|
Host | A drop-down list of nodes in the cluster available for protection. |
Port | The port number on which the Rapid Recovery Core communicates with the Agent on the node. |
User name | The user name of the domain administrator used to connect to this node; for example, example_domain\administrator or administrator@example_domain.com. |
Password | The password used to connect to this machine. |
|
NOTE: The default settings ensure that all volumes on the machine are protected with a schedule of every 60 minutes. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center