System Center Data Protection Manager 2010 Storag

Authors: Prateek Sharma Contributors: Krishna Mangipudi Questions: Email dpmcalc@microsoft.com

Legal Information: This is provided "AS IS" with no warranties, and confers no rights. Use of this application is subject to th

Requirements: If using Excel 2003, this calculator requires the Analysis Toolpack to be loaded.

Instructions: Fill in the blue variables. Either choose the appropriate drop-downs for the red variables when available or le

Important: This tool should only be used for storage modeling purposes. Please consult with the storage vendor r example configuration provided within this calculator is just that, an example, and as such, each input option need Check Version Changes tab for change details & assumptions

Hyper-V Backup Storage Requirem

In This Tab - Please enter in the appropriate information for cells that are blue and choose the appropriate drop

Hyper-V Node Capacity

Disk I/O Throughput per CSV, Dedicated to Backup Disk I/O Throughput per CSV, Dedicated to Restore LAN Bandwidth dedicated to Backup & Restore

Help 20 MBps 30 MBps 1024 Mbps Help Yes 15 3 32 50 GB 3 GB 10%

Hyper-V Cluster Server Configuration

Import VM Size Data? Number of Hyper-V Nodes Number of Cluster Shared Volumes (CSV) in a Cluster Number of Virtual Machines (VMs) on each CSV Average size of a Virtual machine Average RAM allocated per virtual machine Average expected churn in a day(% of file size)

Note: Do not edit this table, the contents are automatically generated. Note: if this Message is RED, then one of the following threshold has been exceeded:

Messages
1. There is a limit of 16 Nodes in a CSV cluster. 2. There is a limit of 400 VMs, each VM of ~50GB, on a 16 Node CSV cluster.

Hyper-V Cluster Data: Summary Table

Number of Hyper-V Nodes Number of Cluster Shared Volumes (CSV) in a Cluster

Help 2 2

Total number of Virtual Machines (VMs) in each CSV

10

Import VM Size Data RAM Allocated to VM

1 GB 1 GB 1 GB 1 GB 1 GB 1 GB 1 GB 1 GB 1 GB 1 GB 1 GB 1 GB 1 GB

Host Name
Host 1 Host 1 Host 1 Host 1 Host 1 Host 1 Host 2 Host 2 Host 2 Host 2 Host 1 Host 2 Host 3

CSV Name
CSV 1 CSV 1 CSV 2 CSV 2 CSV 3 CSV 3 CSV 4 CSV 5 CSV 6 CSV 7 CSV 8 CSV 8 CSV 8

VM Name
VM1 VM2 VM3 VM4 VM5 VM6 VM7 VM8 VM9 VM10 VM11 VM12 VM13

Size of VM
15 GB 50 GB 25 GB 25 GB 32 GB 55 GB 63 GB 42 GB 25 GB 25 GB 52 GB 34 GB 22 GB

n Manager 2010 Storage Requirements Calculator For Hyper-V

of this application is subject to the Terms of Use - http://technet.microsoft.com/en-us/library/aa997216.aspx.

aded.

ed variables when available or let the calc generate the number. The calculator will do the rest.

nsult with the storage vendor regarding storage design and follow recommended storage design testing processes. The s such, each input option needs to be evaluated as to how it will affect your design.

Backup Storage Requirements Input Factors

d choose the appropriate drop-downs for cells that are red concerning your server configuration.

DPM Server Capacity

Aggregate Disk I/O Throughput on the DPM Server Dedicated to Backup Aggregate Disk I/O Throughput on the DPM Server Dedicated to Restore DPM Server Network Bandwidth

Backup Parameters
Backup Frequency Retention Range (days) Hardware Snapshot enabled? Max Number of parallel backups / CSV Max Number of parallel backups / Node Hours per day you want to run backup (Backup duty Cycle)

DPM Configuration
Co-located Replica Size Co-location factor (Number of VMs/ Replica)

Help Churn
15% 15% 15% 15% 15% 15% 15% 15% 15% 15% 15% 15% 12%

Version: 1.09

aspx.

testing processes. The

on. Help

240 MBps 120 MBps 1024 MBps

Help

Once/day 7
Yes

3 3 15 Hrs
Help

250 GB 8

DPM Primary Backup Requirements Results Pane Note: Do not edit the entries in this sheet Hyper-V Server Configuration Number of Hyper-V servers protected Number of VMs per Hyper-V Node Total Number of VMs in the Hyper-V Cluster Total Size of all VMs Hardware: DPM Number of Servers & Total Storage Total Replica Volume Size Total Recovery Point Volume Size Total Storage Required Number of DPM Servers
Help

2 5 10 357 GB
Help

539 GB 266 GB .8 TB 1

DPM Configuration: Recommend Protected Group PG1 VM Grouping VM1-VM10

Storage Requirements and Backup SLA Host Name Protecting VMs Host 1 Host 2 -------------1, 2, 3

Number of VMs Per Host 6 4

Size of all VMs Per Host

Total Replica size Per Host

Recovery Point Volume Size Per Host 151 GB 115 GB

Storage Required to backup Per Host 456 GB 349 GB

Time Taken for Initial Replication 1 Per Host

202 GB 155 GB

305 GB 234 GB

0 Day(s) 0 Day(s)

Caveats 1. SLAs are estimated based on physical resources such as disk IOPS and network IOPS allocated for backup. In actual implmentations, several factors influence the actual IOPS available for backup and hence the estimates at any instant may not exactly match measured values. At best, these estimates will be close apporximation of the measured values. 2. The variability between the measured SLA and these estimates may be larger when the VMs are not of uniform size. 3. In estimating recovery SLA, it is assumed that the DPM server is fully utilized for recovery of the VMs of a Host node and that there are no other backups or recovery processes running.

uirements Results Pane

Help Hardware: DPM Server & Storage Requirement Recommended Number of cores / DPM Server 4 Recommended RAM Configuration / DPM Server 8 GB Server Architecture 64 bit Replica Volume Size 539 GB Recovery Volume Size 266 GB Total Storage per DPM Server .8 TB Hardware: DPM Server Internal Storage Requirements Storage required for DPM install bits 1 GB Stoarge required for SQL install bits 2 GB Storage required for DPM Config DB 10 GB Storage required for DPM diagnostic log files 1 GB Recommended Page File size 20 GB Total Internal Disk Storage for DPM 33 GB

DPM Configuration: Recommended Protected Group Configuration Synchronization Frequency Once/day Retention Range 7 days Number of parallel threads 6

Help

Backup Window 0 Day(s) 5 Hrs ######

d Backup SLA

Help

Time Taken for Initial Replication 1 Per Host

Time taken to create a Recovery 2 Point Per Host

VM Recovery TimePer 3 Host

4 Hrs 3 Hrs

42 Mins 34 Mins

0 Day(s) 0 Day(s)

4 Hrs 3 Hrs

42 Mins 34 Mins

0 Day(s) 0 Day(s)

2 Hrs ###### 2 Hrs ######

Check here for Best Practices Recommendations for DPM Disk Allocation
Help

DPM Backup Requirements Calcu Note: Do not edit the contents of this worksheet. Backup Config Params Max Number of parallel backups on DPM server Effective Backup Connection Throughput / VM Effective Restore Connection Throughput / VM Effective Throughput for Replica Point Creation Hyper-V Server Configuration Total Number of VMs in the Hyper-V Cluster Number of Hyper-V servers protected Number of VMs per Hyper-V Node Total Size of all VMs

6 7 MB/s 10 MB/s 7 MB/s

10 2 5 357 GB

DPM Storage Requirements

Host Name

CSV Name

VM Name

Size of VM

Replica size

Host 1 Host 1 Host 1 Host 1 Host 1 Host 1 Host 2 Host 2 Host 2 Host 2 -----------

CSV 1 CSV 1 CSV 2 CSV 2 CSV 3 CSV 3 CSV 4 CSV 5 CSV 6 CSV 7 -----------

VM1 VM2 VM3 VM4 VM5 VM6 VM7 VM8 VM9 VM10 -----------

15 GB 50 GB 25 GB 25 GB 32 GB 55 GB 63 GB 42 GB 25 GB 25 GB -------------

23 GB 75 GB 38 GB 38 GB 48 GB 83 GB 95 GB 63 GB 38 GB 38 GB

---------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

-----------------------

-----------------------

-----------------------

-----------------------

-----------------------

DPM Backup Requirements Calculations Pane

Hardware: DPM Number of Servers & Total Storage Total Replica Volume Size Total Recovery Point Volume Size Estimated max time for IR with 6 parallel threads Estimated max time time for EF 6 parallel threads

539 GB 266 GB 5 Hrs 5 Hrs

irements

Backup & Recovery SLAs Amount of data Time taken to transferred / create a Recovery VM / Backup Point period 2 GB 5 GB 3 GB 3 GB 3 GB 6 GB 6 GB 4 GB 3 GB 3 GB ----------46 Mins 136 Mins 72 Mins 72 Mins 90 Mins 149 Mins 170 Mins 116 Mins 72 Mins 72 Mins

Recovery Point Volume Size

Storage Time Taken Required to for Initial backup a Replication VM

12 GB 37 GB 19 GB 19 GB 24 GB 40 GB 46 GB 31 GB 19 GB 19 GB -------------

35 GB 112 GB 57 GB 57 GB 72 GB 123 GB 141 GB 94 GB 57 GB 57 GB

---------

46 Mins 136 Mins 72 Mins 72 Mins 90 Mins 149 Mins 170 Mins 116 Mins 72 Mins 72 Mins -- --- ----------

---------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

-----------------------

-----------------------

-----------------------

-----------------------

-----------------------

Storage 539 GB 266 GB 19 Mins 19 Mins

overy SLAs

VM Recovery Time

26 Mins 86 Mins 43 Mins 43 Mins 55 Mins 94 Mins 108 Mins 72 Mins 43 Mins 43 Mins -----------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

----------------------------------------------

-----------------------

Note: This sheet is provided as an example only, it does not reflect the true prices. Refer to the proper corp so information.

Sample DPM Server BOMNote Cost Variables

Number of DPM Servers Number of Processor Cores / DPM Server Recommended RAM Configuration / DPM Server Virtual Memory Configuration / DPM Server Server Architecture Total Storage Capacity Needed Number of DPM Enterprise agent Licenses Number of DPM server Licenses

1 4 8 GB 20 GB 64 bit 1 TB 2 1

Cost $500.00 $0.00 $0.00 $0.00 -$0.00 $500.00 $0.00

es. Refer to the proper corp sources for the actual pricing

BOMNote Cost
per Machine per Processor per GB per GB -per GB per License per License

Amount $500.00 $0.00 $0.00 $0.00 -$0.00 $1,000.00 Total $1,500.00

Help for Input Tab Help for: Hyper-V Node Capacity Use this table to enter the storage and network parameters on the Hyper-V Nodes that will be allocated for backup and restore. Disk I/O Throughput per CSV, Dedicated to Backup The backup rate helps to provide an estimation of how long it will take to complete backup on an DPM server. The backup rate is based on the assumption that the backup process can sustain the rate against each PG concurrently. The backup window is a critical section of planning to ensure that the backup window is run within a timeframe to minimize the impact on other workloads. The actual back rate that can be achieved will depend on three things: 1. Read rate from source LUN if designed properly, this should not be a huge problem unless you run backup during peak times or youre running multiple threads from the same set of disks. 2. Effective write rate at the medium- This is the speed with which DPM can write to the storage pool disks. When doing initialization, the writes are typically sequential in nature. However for express fulls, the writes are typically random in nature. 3. The network rate - It is recommended that you use a Gbps network connectivity between the protected server and the DPM server. DPM can also be configured to use a dedicated NIC to perform the backups thereby getting a higher throughput without loading your corporate network Disk I/O Throughput per CSV, Dedicated to Restore This is the effective rate at which you can restore data. Restores typically require sequential reads off the DPM disks. Hence the throughput is greater than what you get for express fulls. Note: DPM supports SAN based hardware snapshot mode of recoveries. You can use this feature if you need is to perform very fast recoveries (which cannot be met with the network based recovery model of DPM). You will need the proper software from the storage vendors for this, and there may be addtional costs involved.
Back

Help for: D Use this table to enter the sto theDPM Server that will be al
Back

Help for: Use this table to specify how how long you want to keep th should also indicate the snap The options are Hardware Sn more about this at the followi http://blogs.technet.com/b/as provider-considerations-while

Hardware Snapshot enable using Hardware VSS provide to the following links for more 1. http://technet.microsoft.com 2. http://technet.microsoft.com 3. http://technet.microsoft.com 4. http://technet.microsoft.com

Best practices guidline is to s CSV to 3 when backing up le recommended to set it to 2.

Max Number of parallel bac enabled? is Yes this is equal CSV; else it is equal to 1.

Backup duty cycle is the nu backup to run; this is the bac exceeds this number then it w Requirements pane.
Back

Help for: Help for: Hyper-V Cluster Server Configuration Use the parameters in this table to specify how you want to model the storage. If all the VMs are of uniform size or if you have a small number of VMs whose average is approximately the same then select "No" in the "Import VM Size Data?" row. If there is a large variation in the size of the VMs, then select "Yes" in the "Import VM Size Data?" row. If you select "No" then go on to answer the rest of the questions in this table. If you select "Yes", then go on to fill the values in the "Import

About this table: Use this table to specify the D In general, you will not need may be situations in which yo thumb, if the VM size is less t change the collocation to 12; use collocation and if the VM default value for collocation o

Refer to following links in the

Use the parameters in this table to specify how you want to model the storage. If all the VMs are of uniform size or if you have a small number of VMs whose average is approximately the same then select "No" in the "Import VM Size Data?" row. If there is a large variation in the size of the VMs, then select "Yes" in the "Import VM Size Data?" row. If you select "No" then go on to answer the rest of the questions in this table. If you select "Yes", then go on to fill the values in the "Import VM Size Data" table. Back Help for: Hyper-V Cluster Data: Summary Table You have a choice of either Importing data pertaining to each VM or developing a model based on a uniform VM size. You can choose one or the other option in the Hyper-V Cluster Server Configuration table above, by selecting the proper option in the "Import VM Size Data?" row. Back Import VM Size Data If you selected "Yes" in the "Import VM Size Data?" row in the HyperV Cluster Server Configuration table above, then you need to fill in this table. To populate this table, you need to refer to your Hyper-V configuration and enter the specific details for each Node and each VM as shown below. Back

Use this table to specify the D In general, you will not need may be situations in which yo thumb, if the VM size is less t change the collocation to 12; use collocation and if the VM default value for collocation o

Refer to following links in the location before you edit these

1. Co-Locating Data on Disk: us/library/ff399498.aspx

Co-located Replica Size: Thi each for the replica volume a number is stored in the regist HKEY_LOCAL_MACHINE Protection Co-location factor: This is th or a recovery point. This valu Manager\Collocation\Hype

These parameters help in ke within the Servers' LDM limits blog:

http://social.technet.microsof about-dpm2010-scalability-an
Back

Deletes No Change Edits Additions

Back

Help for DPM Requirements Tab

Help for: Hyper-V Server Configuration This table contains a summary of the data entered in the Input tab of this worksheet.
Back

Help for: Hardware: DPM S The information in this table p sizing parameters. Use this t
Back

Help for: Hardware: DPM Number of Servers & Total Storage About This Table: The maximum number of DPM servers per Hyper-V cluster should always be 1, because VMs cannot be migrated between DPM servers. If more than one DPM server is indicated, then you have the following options: - Increase the input colocation factor (in the Input tab) - Consider splitting the CSVs to be protected into several smaller clusters - Reduce the number of input VMs that are protected - Reduce the Retention Range Note on co-location: A best guess at the storage savings in the Recovery Point volume is shown in this table . Due to the random nature of the optimization with the co-location algorithm it is difficult to accurately predict the exact savings.
Back

Help for: DPM Configurati Co If Backup Window cell below meeting your backup SLA sp Frequency column of this tab the following, in the Input tab - "Aggregate Disk I/O Throug Backup" - "DPM Server Network Band
Back

Storage Requirements and Backup SLA About This Table: This table shows the backup storage requirement and various backup SLAs on a per Hyper-V server basis. The values in this table show you how much storage is required to backup the VMs associated with a Hyper-v node and do not account for storage savings as a result of enabling co-location on the DPM server.
Back

Best Practic Althoug h

In Summ * Do not to

References: 1. Disks
Back

lp for Input Tab Help for: DPM Server Capacity Use this table to enter the storage and network parameters on theDPM Server that will be allocated for backup and restore

Help for: Backup Parameters Use this table to specify how often you want to backup the data and how long you want to keep the backed up data. In this table, you should also indicate the snapshot technology at the Hyper-V Node. The options are Hardware Snapshot or Software Snapshot. Read more about this at the following link: http://blogs.technet.com/b/asim_mitra/archive/2009/12/11/snapshotprovider-considerations-while-backing-up-a-csv-cluster.aspx Hardware Snapshot enabled?: This parameter is used if you are using Hardware VSS provider for creating a snapshot. Please refer to the following links for more information on protecting a CSV. 1. http://technet.microsoft.com/en-us/library/ff634189.aspx 2. http://technet.microsoft.com/en-us/library/ff634220.aspx 3. http://technet.microsoft.com/en-us/library/ff634216.aspx 4. http://technet.microsoft.com/en-us/library/ff634192.aspx Best practices guidline is to set Max Number of Parallel backups / CSV to 3 when backing up less than 12 Hosts, beyond that it is recommended to set it to 2. Max Number of parallel backups / Node: If Hardware Snapshot is enabled? is Yes this is equal to Max Number of Parallel backups / CSV; else it is equal to 1. Backup duty cycle is the number of hours for which you want backup to run; this is the backup SLA. If the estimated backup exceeds this number then it will be flagged in RED in the DPM Requirements pane.

Help for: DPM Configuration About this table: Use this table to specify the DPM server configuration parameters. In general, you will not need to modify the default values , but there may be situations in which you may need to do so. As a rule of thumb, if the VM size is less than 15 GB, then you may want to change the collocation to 12; if the VM size is 150GB, then do not use collocation and if the VM size is about 50GB, then use the default value for collocation of 8. Refer to following links in the DPM documentation about Data co-

Use this table to specify the DPM server configuration parameters. In general, you will not need to modify the default values , but there may be situations in which you may need to do so. As a rule of thumb, if the VM size is less than 15 GB, then you may want to change the collocation to 12; if the VM size is 150GB, then do not use collocation and if the VM size is about 50GB, then use the default value for collocation of 8. Refer to following links in the DPM documentation about Data colocation before you edit these values: 1. Co-Locating Data on Disk: http://technet.microsoft.com/enus/library/ff399498.aspx Co-located Replica Size: This is the default size allocated by DPM each for the replica volume and recovery point volume . This number is stored in the registry at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Co-location factor: This is the number of VMs co-located in a replica or a recovery point. This value is stored in the registry at: Manager\Collocation\HyperV\DSCollocationFactor These parameters help in keeping the number of volumes allocated within the Servers' LDM limits. Read more about this in the following blog: http://social.technet.microsoft.com/wiki/contents/articles/informationabout-dpm2010-scalability-and-new-features.aspx

Churn

Before

After

Churn

A
No Change

B C

B C D

C D
A+C+D

PM Requirements Tab

Help for: Hardware: DPM Server & Storage Requirement The information in this table provides you with the DPM Server sizing parameters. Use this to generate a BOM for a DPM server.

Help for: DPM Configuration: Recommended Protected Group Configuration If Backup Window cell below is RED, it means that you are not meeting your backup SLA specified in the Synchronization Frequency column of this table. To fix this, you can try to Increase the following, in the Input tab: - "Aggregate Disk I/O Throughput on the DPM Server Dedicated to Backup" - "DPM Server Network Bandwidth"