HP StoreOnce shares to catalyst stores

[rdrost]

To summarise :

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

[foggy]

Thanks for the request. Merging your post into existing thread discussing similar matter.

[Bjornulf]

Hi all

Is there a way to move backupfiles from Windowsserver to StoreOnce Catalyst? For most of the backupjobs I'll just clone the jobs and point to the new repository. But for some jobs with long retention I would like to move the backupfiles if possible.

Bjørnulf

[foggy]

Hi Bjørnulf, there's a workaround to migrate via SOBR evacuation functionality, however, I'd advise you to start anew and keep the old chains on the Windows server for some time, until the new chains reach the required retention On StoreOnce.

[Bjornulf]

Hi Alexander

Thank you for your response

Bjørnulf

[kte]

You can do in the veeam console in files a copy from a windows server repository to a storeonce repository or other copy jobs
And then rescan the repository

[foggy]

Wouldn't work (unless we're talking CIFS) - you can only copy backups from the Catalyst Store via the Files node, the functionality behind it is not able to create Catalyst objects due to the metadata specifics, so this ability is blocked.