Migrate Data Domain to HPE StoreOnce repository

[Marcus1414]

We are planning to replace our current Dell EMC data domain to HPE StoreOnce catalyst store.
All backup files will be migrate to HPE StoreOnce and decommission the data domain.
What is the best way to move the backup files from data domain to StoreOnce?

[HannesK]

Hello,
"best" depends on amount of restore points. As deduplication appliances are very slow at read speed and all data needs to be de-hydrated, I would try to age it out and leave it where it is. Meaning using the sealed mode in scale-out-repositories or start a new repository on the StoreOnce.

You can also try migration aka "evacuate" in SOBR. From what I heard from customers, that can take very long. Very low read rates. Can take weeks.

Best regards,
Hannes

[Marcus1414]

Can I use Backup Copy Job to copy data from Data Domain repository to StoreOnce repository, and then modify existing backup jobs to point to StoreOnce repository?

Is this doable and is there any concerns on the retention points?

[HannesK]

backup jobs cannot be mapped to backup copy job backups. Also file copy jobs cannot be used, because StoreOnce cannot be source or target of a file copy job

Backup copy jobs would also only copy the latest restore point (well, there is the BackupCopyMirrorAll registry key, but this only allows to copy the latest increments. Not the old GFS restore points you probably like to copy)

Off-topic: In general, backup jobs should always point to "dumb" storage (if talking about HPE, that would be Apollo servers). Dumb block storage with XFS / REFS is much faster and has better price / value ratio than dedupe appliances (except if you require active full for whatever reason)