- Posts: 10
- Liked: never
- Joined: Jan 10, 2018 9:27 am
- Full Name: rdrost
There’s two options to migrate Backup (Copy) jobs to additional Storeonce:
1.Create new repository on new Storeonce. Clone the existing backup (copy) job and point the backup (copy) job to the new Storeonce. This would create a new backup chain on the new Storeonce and does not migrate data from the current Storeonce to the new Storeonce. The current Storeonce would stay Full.
2.Create a new repository on the new Storeonce. Create a Scale-Out Repository and add the new repository and repository from current Storeonce as extents. After this the existing backup jobs will point to the new Scale-Out Repository. Putting the repository extent from current Storeonce in Maintenance mode would evacuate all backupjobs/data to the repository extent on the new Storeonce.
It would have been so much nicer if we could migrate individual backup (copy) jobs including current backup chains/data. Preserving GFS retention.
Case # 02445420
Users browsing this forum: No registered users and 13 guests