foggy wrote:If you've copied the files into the folder that is one level down the path used by one of the extents, it should be ok. For example, if the extent points to E:\Backups, then folder containing the backup files for the migrated job should be copied there: E:\Backups\Job1.
I can confidently say that that does NOT work if you move the backups to only one of the volumes within the SOBR. I'm on version 18.104.22.1681. I've tried moving the files with File Explorer (right click -> copy; right click -> paste) as well as with robocopy. Here are the procedures I used:
The SOBR is made up of three volumes: G:\, H:\, & L:\ and mapped to the "Backups" directory within each.
I also have three stand-alone repositories: I:\Backups, J:\Backups, and K:\Backups.
1. Copy entire backup job directory from I:\Backups\DNS Servers to L:\Backups\DNS Servers. All that exists within the DNS Servers folder are the backup files, there are no nested folders or anything like that.
2. Rescan my SOBR repository. During this process all 3 volumes within the SOBR show "0 added, 0 encrypted, 0 removed, X skipped".
3. Attempt to point existing backup job at SOBR repository. At this point I receive an error message stating: "Move all backup files to the new backup repository first."
I also tried copying the full backup directory to one of the volumes and then adding an empty folder on each of the other volumes, did a rescan again, but got the same results.
I'm guessing that because there are multiple volumes within the SOBR it's not as simple as just moving the backups to one of the volumes and re-scanning anymore probably due to the way the backup files are tracked within the SOBR. I'll open a support ticket if needed, just let me know if I should do that instead of proceeding further on the forums. Thanks!