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:

• If the original Core containing the repository is functioning, temporarily stop protection of machines on that Core.
• Then, stop the Core service of the original Core while you transfer ownership.
• After connecting the repository to the new Core as described in this procedure, return to the original Core. Ensure that all machines you continue to protect have a repository associated with them.
• Then restart the Core services on the original Core.

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.

1. Navigate to the Rapid Recovery Core Console.
2. On the icon bar, click (More), and then select Repositories.

   The Repositories page displays.

3. To select a repository type, click the drop-down menu next to Connect to Existing.
4. In the Connect Existing DVM Repository dialog box, enter the following information for the repository you want to open, and then click Connect.

   Table 14: Open Existing DVM Repository options

   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.

5. On the Cores page of the wizard, click to select the appropriate Core, and then click Next.
6. On the Details page of the wizard, to ensure that the selected Core is the one to which you want to connect, review the displayed details, and then click Finish.

   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.