There is a lack of space in the old repository. Customer wants to move all existing savepoints from an old repo to a new one. Also he has a strong desire to redirect the existing jobs to the same new repo ideally preserving retention.
This could be achieved only partially by going through GUI.
Savepoints (with GlobalManifest) can be moved to a new location, then new repo created pointing to a new share. Ranger will prompt to import SPs.
Also, existing jobs can be edited to point them to a new repo. It can be cumbersome for multiple jobs. Think about dozen of jobs.
Unfortunately, imported SPs won't be associated with old jobs. Retention won't be executed against them. Modified jobs apparently will perform Full backup on first run after editing.
Method suggested requires some basic sql skills and MS SQL Management Studio installed. Advanced users can run commands in sqlcmd.
Here is a procedure:
1. Create vRangerPro DB backup!
2. Do not delete old repo yet! Designate a new share, keep it empty. Create a new repo pointing to this share.
3. Move old repo content to a new location. You will overwrite blank GlobalManifest file.
4. Open Management Studio.
5. Find RepositoryId for old and new repos:
select*from Repository
6. Redirect existing jobs to a new repository. All in one shot and only those that used old repo as a destination. Replace <> with actual values from step 5.
update BackupTemplateTask
set RepositoryId ='<new_RepositoryId>'
where RepositoryId ='<old_RepositoryId>'
7. Re-register savepoints from old repo into a new one:
update SavePoint
set RepositoryId ='<new_RepositoryId>'
where RepositoryId ='<old_RepositoryId>'
and IsDeleted = 0
8. Restart vRanger Service. Just single main service is sufficient. Open Ranger GUI.
At this point you should not see any savepoints under the old repo. Everything will be under the new one.
Switch to My Jobs view. Modified jobs should point to the new repo.
You can delete old repo now. Next run will follow your retention cycle.
