Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently evaluating Microsoft System Center Data Protection Manager 2010.

When creating a new protection group, I can select to co-locate the client data in the storage pool.

enter image description here

Now, the documentation states:

System Center Data Protection Manager (DPM) allows you to co-locate your protection groups on a volume or tape. Co-locating your protection groups allows you to use your storage more effectively.

Awesome! So, let's enable it.

enter image description here

Now I require almost 10x as much storage space. Why?

share|improve this question
I was unable to find any Data Protection Manager tag and can't create one either. A little help would be appreciated :) – Oliver Salzburg Mar 6 '12 at 15:57
I found the scdpm tag-- that's not exactly the easiest name to find, and its worthless for google. I'll write a meta post asking for re-name suggestions. – Joel Coel Mar 6 '12 at 16:03
up vote 1 down vote accepted

According to this post on Microsoft's forums, it is to do with the initial setup and configuration of co-location. Don't have a better source than it aside from the response is from a Microsoft Employee.

When you configure client protection - in the PG wizard, it asks for the amount of data per client you expect to backup. The Default for "Data per computer" is 5GB. By default, DPM will co-locate 10 clients per Replica / Diff volume, so you will see by default DPM will allocate 61.56 GB the first time you create the PG. This is assuming 10 clients at 5GB / client.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.