This task requires a DVM repository to exist in your Core, with a running repository optimization job.
When you initiate the Optimize Repository Job, the selected DVM repository is deduplicated. This deduplication optimization is a processor-intensive job intended to save space in the repository. For more information, see About DVM repository optimization.
Once this job has been initiated, you can interrupt the job using the following procedure. This pauses deduplication. If you have already interrupted a optimization, you can resume the process using this procedure.
Complete the steps in this procedure to interrupt or resume a repository optimization job.
The Repositories page appears.
A warning prompt appears asking you to confirm the interruption.
A warning prompt appears asking you to confirm the optimization.
The dialog box closes, and the repository optimization job resumes from the point where it was last interrupted.
To perform this procedure, you must have the appropriate credentials for the original Core, and you must have the local or network path, IP address or server name.
If connecting to a DVM repository that is currently owned by another functioning Core, you must first prepare for the impending transfer of ownership. The following prerequisites apply:
For more information about pausing protection, see Pausing and resuming protection. For more information about shutting down and restarting the Core service, see Restarting or shutting down the Core service.
From your Rapid Recovery Core Console, you can connect to an existing repository that is currently managed in a different Core. The repository you connect to must be accessible on a shared network location, or on a storage device accessible to the second Core.
This process is useful if your original Core is down and you wish to stand up a replacement Core. If you later wish to change ownership again from the second Core to a third Core (or to the original), you can do so. The same rules apply.
|
Caution: Connecting to a repository from another Core changes ownership of the repository. After you connect to the repository, the information is then accessible only to the second Core. The original Core losing the repository must not be in use. For example, the machine must be turned off, not accessible to the network, or the Core services must be stopped. |
Complete the following procedure to connect to an existing repository.
The Repositories page displays.
Text Box | Description |
---|---|
Path |
The path for the repository (for example, D:\work\machine for a local path, or \\10.10.99.155\repositories by IP address, or \\servername\sharename for a network path). |
User name |
If the repository has a network path, enter the user name for logging in to the network share. |
Password |
If the repository has a network path, enter the password for logging in to the network share. |
The dialog box closes, and the selected repository is added to your current Core.
If you see an error indicating that the selected repository is in use, log into that Core and prepare it for transferring ownership of its repository to this Core. Pause any existing protection; pause any existing replication; wait for queued jobs to complete, or cancel them. Shut down the Core services or gracefully power down the Core server, and then repeat this procedure. For more information on pausing protection, or resuming protection that is paused, see Pausing and resuming protection. For more information on pausing replication, or resuming replication that is paused, see Pausing and resuming replication. For more information about shutting down and restarting the Core service, see Restarting or shutting down the Core service.
In the DVM Repositories pane, each DVM repository added to the Core is displayed.
Repository details differ based on the repository technology type. To view or modify repository details, use the following procedure.
The Repositories page is displayed.
Option | Description | ||
---|---|---|---|
Create |
This option opens the Create Repository Wizard, a workflow that helps you define all requirements to create a new DVM repository. For more information, see Creating a DVM repository. | ||
Connect to Existing |
This option opens the Connect Existing DVM Repository dialog box. When you provide the local or CIFS share path and connection credentials, this lets you open a repository from another Core.
For more information, see Connecting to an existing repository. | ||
Refresh |
Refreshes the list of repositories shown on the page. |
Option | Description | ||
---|---|---|---|
Expand repisotiry |
Expand the existing repository by adding a storage location.
| ||
Check |
Perform a repository check. | ||
Settings |
View or modify repository settings. These settings include:
| ||
Optimize |
Perform a repository optimization job. For more information, see About DVM repository optimization. | ||
Delete |
Delete a repository.
|
Rapid Recovery lets you perform a diagnostic check of a repository volume when errors occur on the Core. Errors could be the result of the Core being improperly shut down, a repository failing to mount or unmount, a hardware failure, or other environmental, lower IP stack factors that can be exposed in Rapid Recovery functionality.
For all repository technology types, the check performs the following tasks:
The check also performs the "Recalculate deduplication cache for repository" task.
|
NOTE: This procedure should only be performed for diagnostic purposes. For example, run this check in the event of hardware failure, improper shutdown of the Core, or failure when importing a repository. |
The Repositories page appears.
The Check Repository dialog box appears.
Active jobs are canceled and the Checking Repository job starts.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center