So my understanding is that you have two solutions - Networker+Data Domain and Avamar.
Per my knowledge, you can not migrate data from Data Domain to Avamar.
Avamar and Data Domain uses different file types to write the data to its storage. Generally we point our existing client backup to Avamar in such situation and leave the old data on DD to expire. In your case you will need to repoint your DB backup to Avamar but thats not a good choice.
vm backups work best on DD (from what EMC says) but
I would just change the vm backups to land on Avamar, and let the DD copies expire on schedule and you would slowly gain back space.
beware, the first backup landing on Avamar make take longer has it might have to copy more to it (it might no have matching dedup chucks and have to create them)
Change Block Tracking puts a heavier load on Avamar than it does on Data Domain because we have to retrieve chunks from the Avamar, integrate the changed blocks, then write the updated data back to the Avamar server. This can have an impact on backup performance.
I recommend being very cautious about how much data you send to the Avamar server. Sending backups to Avamar will create atomic data stripes that consume metadata capacity. There is no way to remove these stripes even if you expire the backup data that is stored in them.
Pawan_Kumawat
1 Rookie
•
46 Posts
425
0
Posted May 23rd, 2017 05:00
Hi,
So my understanding is that you have two solutions - Networker+Data Domain and Avamar.
Per my knowledge, you can not migrate data from Data Domain to Avamar.
Avamar and Data Domain uses different file types to write the data to its storage. Generally we point our existing client backup to Avamar in such situation and leave the old data on DD to expire. In your case you will need to repoint your DB backup to Avamar but thats not a good choice.
Regards,
Pawan