Attaching an archive lets you see recovery points from the archive.
You must have a pre-existing archive created in Rapid Recovery Core release 6.0.1 or later to complete this procedure. For more information, see Creating an archive.When you attach an archive, the archive name you provide appears as an archive menu in the left navigation menu of the Core Console. Each protected machine with recovery points in the archive is listed separately below the archive menu. You can click any machine name in the archive and browse its recovery points. You can then take the same actions as with any other recovery points currently visible in your Core.
Attaching the archive also caches the credentials for accessing the information. Unless you delete the attached archive permanently, you can easily detach and re-attach an archive, making its recovery points easily accessible without cluttering the Core Console. For information about detaching an archive, see Detaching an archive.
Use this procedure to attach an archive.The value you type in this field appears in the left navigation menu as the archive menu name.
Following best practice for display names, the archive name should contain between 1 and 64 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.
Option | Text Box | Description | ||
---|---|---|---|---|
Local |
Location |
Enter the path to the archive; for example, D:\Work\Archive. | ||
Network |
Location |
Enter the path to the archive; for example, \\servername\sharename. | ||
User name |
Enter user name for logging in to the network share. | |||
Password |
Enter the password for logging in to the network share. | |||
Cloud |
Account |
Select an account from the drop-down list.
| ||
Container |
Select the container of the archive associated with your account from the drop-down menu. | |||
Folder name |
Enter the name of the folder of the archived data; for example, Rapid-Recovery-Archive-[DATE CREATED]-[TIME CREATED]. |
You must have an archive attached to your Core to perform this task.
When an archive is attached to your Core, you can navigate through the data in the archive as if the data were currently protected machines.Once you attach an archive, its credentials are cached and it remains visible in your Core until you detach it.
Perform this task after you have accomplished your objectives for attaching the archive, to remove it from view on your Core.
|
NOTE: Detaching the archive does not delete the data; it only removes the data from current view. |
You can use this procedure to import an archive one time, or schedule an archive to import on a recurring basis.
When you want to recover archived data, you can import the entire archive to a specified location.
|
Caution: Perform this step only after careful consideration. Importing an archive repopulates the repository with the contents of the archive, replacing any new data in the repository since the archive was captured. |
To import an archive, complete the steps in the following procedure.
The Import Archive Wizard opens.
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. |
Option | Description |
---|---|
Use an existing Repository |
Select a repository currently associated with this Core from the drop-down list. |
Create a Repository |
In the Server text box, enter the name of the server on which you want to save the new repository—for example, servername or localhost—and then see Creating a DVM repository. |
Option | Description | ||
---|---|---|---|
Daily | Click the clock icon and use the up and down arrows to select at what time you want to the archive job to begin.
If you are using a 12-hour time system, click the AM or PM button to specify the time of day. | ||
Weekly | Select the day of the week and then the time you want the archive job to begin.
If you are using a 12-hour time system, click the AM or PM button to specify the time of day. | ||
Monthly | Select the day of the month and the time you want the archive job to begin.
If you are using a 12-hour time system, click the AM or PM button to specify the time of day. | ||
Pause initial importing |
Select this option if you do not want the import job to begin at the next scheduled time after you complete the wizard.
|
Rapid Recovery lets you define connections between existing cloud storage or cloud service providers and your Rapid Recovery Core. Compatible cloud services include Microsoft Azure, Amazon Web Services (AWS), any OpenStack-based provider (including Rackspace), and Google Cloud. US government-specific platforms include AWS GovCloud (US) and Azure Government. You can add any number of cloud accounts to the Core Console, including multiple accounts for the same provider.
The purpose of adding cloud accounts to your Core Console is to work with them as described in the topic About cloud accounts.
Once added, you can manage the connection between the Core and the cloud accounts. Specifically, you can edit the display name or credential information, configure the account connection options, or remove the account from Rapid Recovery. When you edit or remove cloud accounts in the Core Console, you do not change the cloud accounts themselves—just the linkage between those accounts and your ability to access them from the Core Console.
This section describes how to define links between existing cloud storage provider or cloud service provider accounts, and the Rapid Recovery Core Console. It also describes how to manage those cloud accounts in Rapid Recovery.
Topics include:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center