Non scale-out repositories. What is a consistent way to move a backup job from one repository to another without losing anything?
I have done this:
1. disable the backup copy job
2. Move the \backups job directory to the other repository volume (same server different disk)
3. re-scanned both repositories. The first re-scan of the destination repository gave me errors that the backup directory couldn't be sync'd. I ran the scan again and got no errors. I did the re-scan on the source repository first then the target.
4. I then re-mapped the backup copy job to the new repository/directory.
when the backup copy job ran again there were errors and I had to run a new active full. This has happened twice in the last week when I had to move jobs around to make space.
I can't use the scale-out because we have to be able to had the customer their backup data if they request it. We are an MSP with a managed backup offering.