vmniels wrote:You can just add your excisting repositories to a scale out repository and everything will be done for you (changing job targets).
EugeneK wrote:The standard procedure should work, we migrated files around using it, when the new SOBR was introduced by a few of our clients into existent environments.
I'd recommend to make sure the path selected to files is correct - can it be that the SOBR repo is mounted to a different path than the files were copied to?
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.
foggy wrote: ...the job should exist on the extent at the moment it is added to SOBR, otherwise the backups can be skipped during SOBR rescan (which occurs in John's case). In your procedure everything should be smooth.
Users browsing this forum: Bing [Bot], DonZoomik and 1 guest