Comprehensive data protection for all workloads
Post Reply
Posts: 9
Liked: never
Joined: Apr 13, 2017 7:05 pm
Full Name: WLCU

Data Domain as secondary storage (archive) + primary for DEV

Post by wlcu » Apr 13, 2017 7:21 pm

To start, I've never used Data Domain before. We just implemented Veeam backing up to a Dell Server + DAS as primary storage and purchased a DD for archive storage. What I've done is create a Backup Copy Job that uses the DD as the repository with a GFS type retention. What I did was create a single DD Storage Unit for Veeam, to access, using DDBoost over FC. Called it veeam_dd_su01.

My question is, should I use the same Storage Unit (or mtree) for my DEV servers which will use the DD as primary backup storage? We don't need DEV on fast disks or instant recovery. Or should I create a second Storage Unit (or mtree)? Does it matter?


Product Manager
Posts: 5506
Liked: 516 times
Joined: May 19, 2015 1:46 pm

Re: Data Domain as secondary storage (archive) + primary for

Post by PTide » Apr 17, 2017 12:54 pm


Since all data on the Data Domain is globally deduplicated there will be no difference in space savings if you create another Storage Unit or stay within the existing one. On the other hand a separate Storage Unit allows you to manage your DEV separately from production (e.g. different quotas, separate stats, retention locks etc).


Post Reply

Who is online

Users browsing this forum: JaySt and 66 guests