When you need to access the data in an archived recovery point, you have two options.
|
Caution: Since the Core recognizes the original dates of recovery points in an archive, recovery points imported from an archive may be rolled up or deleted during the next nightly job period, if their age exceeds the retention period. If you want to retain older recovery points imported from an archive, you can disable rollup or extend the retention period for the relevant protected machines. |
When you need to access the data in an archived recovery point, you can attach (for Rapid Recovery 6.x and later) or import the archive, restoring those recovery points to your repository.
Once an archive is created, it can be used in the following ways:
You can use this procedure to create a one-time or scheduled archive.
If you plan on creating an archive to a cloud location, first add your cloud account to the Rapid Recovery Core Console. For more information, see Adding a cloud account.
A one-time archive is an archive created on demand for a specified machine. A scheduled archive is an archive that automatically recurs on the date and time you specify in the wizard. When you schedule a recurring archive, you meet the need for archiving data from protected machines frequently without the inconvenience of repeatedly defining a one-time archive.
Before creating a scheduled archive, ensure that you are satisfied with the name of each folder and subfolder in the archive structure. After performing an initial archive, Quest recommends making no changes to the resulting folder structure. Changing any folder name in the archive path may result in capturing a base image instead of an incremental image. It could also cause difficulty restoring or importing data from an archive due to an inability to properly locate the files.
When creating your archive, you must decide whether to include a full recovery point chain in your archive. For more information, see Recovery point chain options for archives.
Option | Text Box | Description | ||
---|---|---|---|---|
Local |
Location |
Enter the local path where you want the archive to reside; for example, | ||
Network |
Location |
Enter the network path where you want the archive to reside; for example, | ||
User name |
Enter the user name for the user with access to the network share. | |||
Password |
Enter the password for the user with access to the network share. | |||
Cloud |
Account |
Select an account from the drop-down list.
| ||
Container |
Select a container associated with your account from the drop-down menu. | |||
Folder name |
Enter a name for the folder in which the archived data is saved. | |||
Use Glacier storage |
To store your archive in Amazon Glacier storage, select this option. This option is intended for long-term storage of archives. For more information, see Amazon storage options and archiving. |
Option | Text Box | Description |
---|---|---|
Daily | At time | Select the hour of the day you want to create a daily archive. |
Weekly | At day of week | Select a day of the week on which to automatically create the archive. |
At time | Select the hour of the day you want to create an archive. | |
Monthly | At day of months | Select the day of the month on which to automatically create the archive. |
At time | Select the hour of the day you want to create an archive. |
|
NOTE: You may want to pause the scheduled archive if you need time to prepare the target location before archiving resumes. If you do not select this option, archiving begins at the scheduled time. |
Text Box | Description |
---|---|
Replace this Core | Overwrites any pre-existing archived data pertaining to this Core but leaves the data for other Cores intact. |
Erase completely | Clears all archived data from the directory before writing the new archive. |
Incremental | Lets you add recovery points to an existing archive. It compares recovery points to avoid duplicating data that exist in the archive. |
Text Box | Description | ||
---|---|---|---|
Maximum size |
Large archives of data can be divided into multiple segments. Select the maximum amount of space you want to reserve for creating the archive by doing one of the following:
| ||
Recycle action |
Select one of the following recycle action options:
| ||
Comment |
Enter any additional information that is necessary to capture for the archive. The comment is displayed if you import the archive later. | ||
Build complete recovery points chains, including referenced base images outside the date range. |
Select this option to archive the entire recovery point chain. This option is selected by default. | ||
Include only the recovery points in the date range. This saves space, but you are responsible for archiving any needed base images. |
Select this option to archive only the incremental recovery points and no base images.
For more information about recovery point chain options, see Recovery point chain options for archives. |
When data reaches the end of a retention period, you may want to extend that retention by creating an archive of the aged data. When you archive data, there is always the matter of where to store it. Rapid Recovery lets you upload your archive to a variety of cloud providers directly from the Core Console. Compatible clouds include Microsoft Azure, Amazon S3, any OpenStack-based provider, Rackspace Cloud Files, and Google Cloud.
Exporting an archive to a cloud using Rapid Recovery involves the following procedures:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center