dpm 2010 storage calculator for hyper-v

System Center Data Protection Manager 2010 Storage Requirements Calculator For Hyper-V

Check Version Changes tab for change details & assumptions

Hyper-V Backup Storage Requirements Input Factors

Hyper-V Node CapacityDisk I/O Throughput per CSV, Dedicated to Backup 20 MBps

Disk I/O Throughput per CSV, Dedicated to Restore 30 MBps

LAN Bandwidth dedicated to Backup & Restore 1024 Mbps

Hyper-V Cluster Server ConfigurationImport VM Size Data? YesNumber of Hyper-V Nodes 15Number of Cluster Shared Volumes (CSV) in a Cluster 3Number of Virtual Machines (VMs) on each CSV 32Average size of a Virtual machine 50 GBAverage RAM allocated per virtual machine 3 GBAverage expected churn in a day(% of file size) 10%

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 2

Number of Cluster Shared Volumes (CSV) in a Cluster 2

Total number of Virtual Machines (VMs) in each CSV 10

Authors: Prateek SharmaContributors: Krishna MangipudiQuestions: Email [email protected]

Legal Information: This is provided "AS IS" with no warranties, and confers no rights. Use of this application is subject to the Terms of Use - http://technet.microsoft.com/en-us/library/aa997216.aspx.

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 let the calc generate the number. The calculator will do the rest.

Important: This tool should only be used for storage modeling purposes. Please consult with the storage vendor regarding storage design and follow recommended storage design testing processes. The example configuration provided within this calculator is just that, an example, and as such, each input option needs to be evaluated as to how it will affect your design.

In This Tab - Please enter in the appropriate information for cells that are blue and choose the appropriate drop-downs for cells that are red concerning your server configuration.

Help

Help

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:

Help

C28

This is the number of physical servers hosting the Hyper-V VMs

C29

This is the number of CSV volumes hosting the VMs

C30

This is the number of VMs on each CSV

Import VM Size Data

Host Name CSV Name VM Name Size of VM

Host 1 CSV 1 VM1 15 GB 1 GBHost 1 CSV 1 VM2 50 GB 1 GB

Host 1 CSV 2 VM3 25 GB 1 GB


Host 1 CSV 3 VM5 32 GB 1 GBHost 1 CSV 3 VM6 55 GB 1 GBHost 2 CSV 4 VM7 63 GB 1 GBHost 2 CSV 5 VM8 42 GB 1 GBHost 2 CSV 6 VM9 25 GB 1 GBHost 2 CSV 7 VM10 25 GB 1 GB




RAM Allocated to

VM

System Center Data Protection Manager 2010 Storage Requirements Calculator For Hyper-V



DPM Server CapacityAggregate 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 ParametersBackup 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 ConfigurationCo-located Replica Size

Co-location factor (Number of VMs/ Replica)

This is provided "AS IS" with no warranties, and confers no rights. Use of this application is subject to the Terms of Use - http://technet.microsoft.com/en-us/library/aa997216.aspx.

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

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

This tool should only be used for storage modeling purposes. Please consult with the storage vendor regarding storage design and follow recommended storage design testing processes. The example configuration provided within this calculator is just that, an example, and as such, each input option needs to be evaluated as to how it will affect your design.

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

Churn

15%15%

15%

15%

15%15%15%15%15%15%

15%

15%

12%

Help

System Center Data Protection Manager 2010 Storage Requirements Calculator For Hyper-VVersion: 1.09



240 MBps

120 MBps

1024 MBps

Once/day

7Yes

33

15 Hrs

250 GB8

This is provided "AS IS" with no warranties, and confers no rights. Use of this application is subject to the Terms of Use - http://technet.microsoft.com/en-us/library/aa997216.aspx.

This tool should only be used for storage modeling purposes. Please consult with the storage vendor regarding storage design and follow recommended storage design testing processes. The

concerning your server configuration.

Help

Help

Help

DPM Primary Backup Requirements Results Pane

Hyper-V Server ConfigurationNumber of Hyper-V servers protected 2Number of VMs per Hyper-V Node 5Total Number of VMs in the Hyper-V Cluster 10Total Size of all VMs 357 GB

Hardware: DPM Number of Servers & Total Storage Total Replica Volume Size 539 GBTotal Recovery Point Volume Size 266 GBTotal Storage Required .8 TBNumber of DPM Servers 1

DPM Configuration: Recommended Protected Group Configuration

Protected Group

PG1 VM1-VM10

Storage Requirements and Backup SLA

#N/A #N/A #N/A #N/A #N/A #N/A #N/A

#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A

#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A

Note: Do not edit the entries in this sheet

Help

Help

VM Grouping

Host Name Protecting

VMs

Number of VMs Per

Host

Size of all VMs Per Host

Total Replica size Per Host

Recovery Point Volume Size

Per Host

Storage Required to

backup Per Host

Time Taken for Initial Replication Per Host1

1, 2, 3 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.

DPM Primary Backup Requirements Results Pane

Hardware: DPM Server & Storage RequirementRecommended Number of cores / DPM Server 4Recommended RAM Configuration / DPM Server 8 GBServer Architecture 64 bitReplica Volume Size 539 GBRecovery Volume Size 266 GB

Total Storage per DPM Server .8 TBHardware: DPM Server Internal Storage Requirements

Storage required for DPM install bits 1 GBStoarge required for SQL install bits 2 GBStorage required for DPM Config DB 10 GBStorage required for DPM diagnostic log files 1 GBRecommended Page File size 20 GBTotal Internal Disk Storage for DPM 33 GB

DPM Configuration: Recommended Protected Group Configuration

Backup Window

Once/day 7 days 6 #N/A #N/A #N/A


#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A

#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A

#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A#N/A #N/A #N/A #N/A #N/A #N/A #N/A #N/A

Check here for Best Practices Recommendations for DPM Disk Allocation

Help

Help

Synchronization Frequency

Retention Range

Number of parallel threads

Help

Time Taken for Initial Replication Per Host1

Time taken to create a Recovery Point Per Host2

VM Recovery TimePer Host3

Help

DPM Backup Requirements Calculations Pane

Backup Config ParamsMax Number of parallel backups on DPM server 6Effective Backup Connection Throughput / VM 7 MB/sEffective Restore Connection Throughput / VM 10 MB/sEffective Throughput for Replica Point Creation 7 MB/s

Hyper-V Server ConfigurationTotal Number of VMs in the Hyper-V Cluster 10Number of Hyper-V servers protected 2Number of VMs per Hyper-V Node 5Total Size of all VMs 357 GB

DPM Storage Requirements

Host Name CSV Name VM Name Size of VM Replica size

Host 1 CSV 1 VM1 15 GB 23 GBHost 1 CSV 1 VM2 50 GB 75 GBHost 1 CSV 2 VM3 25 GB 38 GBHost 1 CSV 2 VM4 25 GB 38 GBHost 1 CSV 3 VM5 32 GB 48 GBHost 1 CSV 3 VM6 55 GB 83 GBHost 2 CSV 4 VM7 63 GB 95 GBHost 2 CSV 5 VM8 42 GB 63 GBHost 2 CSV 6 VM9 25 GB 38 GBHost 2 CSV 7 VM10 25 GB 38 GB-- -- -- -- ---- -- -- -- ---- -- -- -- ---- -- -- -- ---- -- -- -- ---- -- -- -- ---- -- -- -- ---- -- -- -- ---- -- -- -- ---- -- -- -- ---- -- -- -- --

Note: Do not edit the contents of this worksheet.

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

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


Hardware: DPM Number of Servers & Total Storage Total Replica Volume Size 539 GBTotal Recovery Point Volume Size 266 GBEstimated max time for IR with 6 parallel threads #N/AEstimated max time time for EF 6 parallel threads #N/A

DPM Storage Requirements Backup & Recovery SLAs

12 GB 35 GB 46 Mins 2 GB 46 Mins37 GB 112 GB 136 Mins 5 GB 136 Mins19 GB 57 GB 72 Mins 3 GB 72 Mins19 GB 57 GB 72 Mins 3 GB 72 Mins24 GB 72 GB 90 Mins 3 GB 90 Mins40 GB 123 GB 149 Mins 6 GB 149 Mins46 GB 141 GB 170 Mins 6 GB 170 Mins31 GB 94 GB 116 Mins 4 GB 116 Mins19 GB 57 GB 72 Mins 3 GB 72 Mins19 GB 57 GB 72 Mins 3 GB 72 Mins

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

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

Recovery Point Volume Size

Storage Required to

backup a VM

Time Taken for Initial

Replication

Amount of data

transferred / VM / Backup

period

Time taken to create a Recovery

Point

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

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


Hardware: DPM Number of Servers & Total Storage 539 GB266 GB

#N/A#N/A

Backup & Recovery SLAs

26 Mins86 Mins43 Mins43 Mins55 Mins94 Mins

108 Mins72 Mins43 Mins43 Mins

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

VM Recovery Time

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

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

Cost Variables CostNumber of DPM Servers 1 $500.00Number of Processor Cores / DPM Server 4 $0.00Recommended RAM Configuration / DPM Ser 8 GB $0.00Virtual Memory Configuration / DPM Server 20 GB $0.00Server Architecture 64 bit --Total Storage Capacity Needed 1 TB $0.00Number of DPM Enterprise agent Licenses 2 $500.00Number of DPM server Licenses 1 $0.00

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

Sample DPM Server BOMNote

Cost Amountper Machine $500.00per Processor $0.00per GB $0.00per GB $0.00

-- --per GB $0.00per License $1,000.00per License Total $1,500.00

This sheet is provided as an example only, it does not reflect the true prices. Refer to the proper corp sources for the actual pricing

Sample DPM Server BOMNote

Help for: Hyper-V Node Capacity Help for: DPM Server Capacity

Help for: Backup Parameters

Help for: DPM ConfigurationHelp for: Hyper-V Cluster Server Configuration

Help for Input Tab

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 BackupThe 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 you’re 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 networkDisk I/O Throughput per CSV, Dedicated to RestoreThis 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.

Use this table to enter the storage and network parameters on theDPM Server that will be allocated for backup and restore

Back

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/snapshot-provider-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.aspx2. http://technet.microsoft.com/en-us/library/ff634220.aspx3. http://technet.microsoft.com/en-us/library/ff634216.aspx4. 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.

Back

Back

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-location before you edit these values:

1. Co-Locating Data on Disk: http://technet.microsoft.com/en-us/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 ProtectionCo-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/information-about-dpm2010-scalability-and-new-features.aspx

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.

Help for: Hyper-V Cluster Data: Summary Table

Import VM Size Data

Churn

Deletes

No Change

Edits

Additions

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

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

If you selected "Yes" in the "Import VM Size Data?" row in the Hyper-V 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

Back

Back

Help for DPM Requirements Tab

Help for: Hyper-V Server Configuration Help for: Hardware: DPM Server & Storage Requirement

Help for: Hardware: DPM Number of Servers & Total Storage


This table contains a summary of the data entered in the Input tab of this worksheet.

The information in this table provides you with the DPM Server sizing parameters. Use this to generate a BOM for a DPM server.

Back Back

Help for: DPM Configuration: Recommended Protected Group ConfigurationAbout 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.

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"

Back

Back

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

es Recommendations for

DPM Disk

Allocation

Although Windows

In Summary

References:

* Do not to exceed 17 TB

1. Disks And Volume

Back

Help for: DPM Server Capacity

Help for: Backup Parameters

Help for: DPM Configuration

Input Tab

Use this table to enter the storage and network parameters on theDPM Server that will be allocated for backup and restore

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/snapshot-provider-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.aspx2. http://technet.microsoft.com/en-us/library/ff634220.aspx3. http://technet.microsoft.com/en-us/library/ff634216.aspx4. 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.







Churn

Before After Churn

A ACNo Change

D

C C A + C + D

D







B B

DPM Requirements Tab

Help for: Hardware: DPM Server & Storage RequirementThe 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"

dpm 2010 storage calculator for hyper-v

Documents

backup duty

cluster shared

backup window

recovery point

dpm server

located replica

dpm server

servers protected