When you set up a new protection group under DPM, the software will recommend the amount of space to be allocated for storage. You should generally accept the recommendation, keeping in mind that you may have to increase the allocation later.
However, if you are only protecting part of the data on the protected volume, you can use the DPM guidelines to calculate how much space you will need for the different functions.
DPM needs storage in two different areas. One is the data storage pool, which is the space DPM allocates for itself in the protected storage pool. The second piece of storage DPM needs is space for the synchronization logs.
The pool is used for the replicas of the data DPM creates, as well as the transfer logs it uses to help manage those replicas.
Most of the data storage pool is given over to the replicas. The replicas themselves need a minimum of 1.5 times the storage space of the data being protected. Note: This is a minimum. Based on your enterprise's patterns of use, you may need to add more space.
The next largest element in the data storage pool is the space allocated for the shadow copies. They should be allocated at least 20% of the space given
Requires Free Membership to View
The data storage pool also stores the transfer logs DPM uses to keep up with the synchronization logs. The transfer logs need a minimum of 1.4 times the size of the synchronization logs. Again, usage patterns may indicate that you should increase this allocation.
The final piece of storage DPM needs is space for the synchronization logs. Unlike the other three components, this is not in the DPM storage pool; it is in the protected volume on the file server. It needs to be at least 10% of the size of the protected volume.
For the past 20 years, Rick Cook has written about issues related to storage and storage management.
More information from SearchWinComputing.com:
- Tip: Measuring the impact of Microsoft Data Protection Manager 2006
- Topics: Backup
- RSS: Sign up for our RSS feed to receive expert advice every day.
This was first published in March 2006
Enterprise Server Strategies for the CIO
Join the conversationComment
Share
Comments
Results
Contribute to the conversation