Using this procedure, you can force Rapid Recovery to perform the archive job on a scheduled archive at any time.
To force an archive job, you must have an archive scheduled on the Core.Checking an archive verifies whether an archive and its contents are healthy enough to be restored.
You can scan an archive for the integrity of its structure, data segments, and index files by performing an archive check. The archive check verifies the presence of all necessary files within the archive and that the files are healthy. To perform an archive check, complete the steps in the following procedure.
Option | Text Box | Description | ||
---|---|---|---|---|
Local | Location | Enter the local path for the archive. | ||
Network | Location | Enter the network path for the archive. | ||
User name | Enter the user name. It is used to establish logon credentials for the network share. | |||
Password | Enter the password for the network path. It is used to establish logon credentials for 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 | Select the folder in which the archived data is saved; for example, Rapid-Recovery-7-Archive-[DATE CREATED]-[TIME CREATED] . |
|
NOTE: Do not clear all checks. You must select at least one option. |
Option | Description |
---|---|
Index files mapping offsets | This option checks that all the data on the internal structure of the archive is in the correct location. |
Structure integrity | This option verifies the presence of certain internal files and the folder structure of the archive. If any files or folders are missing, the check fails. |
Checksum integrity | This option checks the integrity of the data segments in the archive to ensure that the segments are healthy. |
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. |
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center