By default the Recovery Manager console uses its own set of TLS keys to communicate with the Secure Storage server. To set up a Secure Storage server to be available on multiple Recovery Manager consoles you must use the same set of TLS keys on each console.
Add Secure Storage server in primary console. Refer to Adding a Secure Storage server
Open or create a recovery project in Forest Recovery Console.
On the menu bar, select Tools | Fault Tolerance.
Click Export secure communication keys…. Browse or type the file name in the field Secure Communication Keys file and type the password.
IMPORTANT |
Ensure communication keys and access credentials are kept secret and protected. |
Then, launch the other instance of Forest Recovery Console.
On the menu bar, select Tools | Fault Tolerance | Import secure communication keys…. Browse and select the Secure Communication Keys file saved in step 4 and click Open.
Open the other instance of the Recovery Manager console.
In the Recovery Manager for Active Directory console, click the Secure Storage node.
In the Secure Storage Servers pane, click Add Server.
Type the DNS name or IP address of original existing Secure Storage server.
In the Agent port field, type port number used when Secure Storage server was first created.
From the Agent installation method drop-down list, select Manual (recommended).
Click OK.
After the Recovery Manager console connects to the existing Secure Storage agent running on the existing Secure Storage server, all backups will appear in the console for viewing.
WARNING |
It is not recommended to use Recovery Manager consoles that are in different forests because if one of the forests is breached it may affect the backups of the other forest. |
The Secure Storage server is used to store critical backups. A server can have multiple volumes available for storage of backup files. Recovery Manager for AD provides the ability to configure which volumes are allowed to store backups, the order of the volumes to be used or you can allow RMAD to determine which volume to use automatically.
If no policy is set for allowed volumes, the Secure Storage server will use the first volume found. The system drive with the operating system will only be selected if it is the only available volume on the server.
Ensure your Secure Storage server has sufficient space for storing of backup files. The amount of space used on each volume is displayed for the Secure Storage server and the available free space. Recommendation is to monitor available free space and ensure that there is space available for backups. If a volume is running out of free space, a warning icon will be displayed in the Properties dialog.
To configure the policy for allowed volumes on Secure Storage server
To get the current policy for allowed volumes on Secure Storage server
After a Secure Storage server has been added, backups can be copied to the Secure Storage server. To enable and configure backups on the Secure Storage server you must enable backups for each Computer Collection separately. For more information on configuring backups on a Secure Storage server refer to Secure Storage server backups.
To view backups on Secure Storage server
Secure Storage is enabled and configured for each Computer Collection separately. The Secure Storage backup can be enabled for both local and remote storage. When a backup is run for a Computer Collection with Secure Storage enabled, a copy of the backup is saved to the Secure Storage server.
Prerequisites
You must have completed the following steps before you can copy backups to your Secure Storage server.
NOTE |
Both Active Directory and Bare Metal Recovery backups can be copied to a Secure Storage server. |
To enable a Secure Storage server for a Computer Collection
In the Recovery Manager for Active Directory console, expand the Computer Collections node.
Right-click the Computer Collection and select Properties.
On the Secondary Storage tab, select the Enable a Secure Storage server check box.
Select the radio button below Enable a Secure Storage server to choose the primary storage location for the backup file to be copied from. Select Copy backup from remote storage location to the selected Secure Storage server to pull the backup file from th remote storage location. Select Copy backup from local storage location to the selected Secure Storage server to pull backup file from the local storage location. If using both local and remote storage options for primary storage, the recommendation is to configure your Secure Storage server to communicate with the primary storage location closest for optimal network performance.
Copy backup from remote storage location to the selected Secure Storage server. Select the DNS name or IP address of a Secure Storage host.
Copy backup from local storage location to the selected Secure Storage server. Select the DNS name or IP address of a Secure Storage host.
Determine which primary location the backup file should be read from to copy to the Secure Storage server and specify access credentials with read permissions. In the Select an account to be used to read data from remote storage location or Select an account to be used to read data from local storage location, click the Select Account button, type the user name and password and click OK.
NOTE |
You can modify existing credentials by clicking Select Account, which opens the Select Account dialog. |
To create backups and copy them to the Secure Storage server
TIP |
You can schedule backup creation on the Schedule tab on the Computer Collections Properties window. |
To perform an integrity check
When a backup is created, a checksum is calculated for the backup file and saved in the Backups database when the backup is registered. An integrity check recalculates the checksum and compares it to the checksum stored in the Backups database.
In the Recovery Manager for Active Directory console, expand the Secure Storage node.
Click the Secure Storage server that contains the backup you want to perform the integrity check on.
In the Backups on the Secure Storage Server pane, right-click the backup and click Check Integrity.
The following statuses can be displayed after running the integrity check:
Status | Description |
---|---|
Passed | The newly calculated checksum value matches the previously calculated checksum stored in the Backups database. |
Unknown | The integrity check was not performed. |
Running | The integrity check is in progress. |
No Checksum | The previously calculated checksum could not be read. This could be due to the backup being created by a previous version of the product. The backup also may have been damaged in such a way that the checksum was also affected. |
Corrupted | The newly calculated checksum value does not match the previously calculated checksum stored in the Backups database. |
You can copy backups stored on the Secure Storage server to another location.
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center