-
Titel
How to: Detach Repository from the Core -
Beschreibung
Sometimes, there's a need to detach the existing repository from the Core without losing any data. Clicking on Delete menu item in the repository drop-down will completely destroy all data and remove the repository immediately, so it's not possible to detach the repository using the GUI. -
Ursache
Possible scenario: repository was cloned and stored on separate storage, but now historical data is removed by rollups in the current repository. Data can be only restored by opening a cloned repository -
Lösung
Core is working with repositories by their unique IDs and paths. So to resolve the issue, original repository should be detached, before cloned repository can be opened on the same Core.
If possible, the temporary Core machine/VM can be spun, and cloned repository can be opened there.
Windows Registry Disclaimer
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article Windows registry information for advanced users.To detach the repository, please perform the following steps:
- Make sure that Core is not performing any tasks and either wait for their completion or cancel active tasks if possible.
- Stop the Core service gracefully.
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Repositories and export it.
- Each subkey is a unique repository ID. Make sure that the proper repository is being selected before deleting it.
- Re-start the Core service.
Repository is now detached.
UPDATE: Starting with Rapid Recovery 6.9, there is an option to unmount a repository using the GUI and without stopping the Core service.