Dpm4 Data Center


Published on

DPM 4 Data Center

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Dpm4 Data Center

  1. 1. Data Protection Manager – SAN integration Vu Nguyen Cao Son EPG Technical Specialist Microsoft Vietnam
  2. 2. Integrating DPM 2007 with SAN <ul><li>Feature Summary </li></ul><ul><li>Allow the DPM customer to perform quick file and application recoveries and Initial Replication (SAN Media Load) of data sources using hardware based snapshot and clone technology, available in a SAN environment. </li></ul>
  3. 3. DPM Initial Replication using SAN Clone technology
  4. 4. Install the DPM agent on the Production Server
  5. 5. Clone the production LUN using the SAN UI
  6. 6. Validate that the cloned LUN is visible in the SAN UI
  7. 7. Fracture the cloned LUN and attach to DPM server
  8. 8. Assign Drive letter and name the cloned LUN
  9. 9. Create Recovery Point LUN & assign drive letter
  10. 10. Create new Protection Group via DPW
  11. 11. State data protection intent
  12. 12. State replication and retention intent
  13. 13. Select Custom volumes in “Disk Allocation” pane
  14. 14. Allocate cloned volume to new PG
  15. 15. “ Do not format” the cloned volume
  16. 16. Select “Manual” Replica creation method
  17. 17. Close wizard and review data structure created by DPM
  18. 18. Move the data on the replica volume into the directory named “Full”. DPM stores the data to be protected into this directory .
  19. 19. Final folder structure on DPM Cloned Replica volume
  20. 20. Run Consistency Check for this new PG
  21. 21. Initial Replication using Cloned Volume is complete
  22. 22. DPM Recovery using SAN hardware snapshot technology
  23. 23. Cancel all running jobs for data source being recovered
  24. 24. Create software snapshot of data source to be recovered Execute the CreateShadowCopy.ps1 power shell script on the DPM server. Provide the data source name and protection group name as input parameters
  25. 25. Create Hardware snapshot of Replica and Recovery Point volumes of data source using SAN UI
  26. 26. Activate the Hardware snapshots using SAN UI
  27. 27. Mount H/w snapshots to Protected server
  28. 28. In Recovery wizard select “SAN Recovery” option
  29. 29. Run Consistency Check after Recovery is complete
  30. 30. Performance impact on Protected server during IR using SAN Clone technology
  31. 31. Performance Impact using EMC SAN <ul><li>Scenario: </li></ul><ul><ul><li>Protection of Exchange Server 2007 (64 bit) using DPM </li></ul></ul><ul><li>Platform: </li></ul><ul><ul><li>Intel Xeon 3.0 GHz, 8 GB RAM, Windows 2003 64 bit operating system </li></ul></ul><ul><li>Exchange Server Configuration: </li></ul><ul><ul><li>This production server has two storage groups supporting 2000 users of 200MB mailbox size. </li></ul></ul><ul><li>LoadGen configuration: </li></ul><ul><ul><li>LoadGen was used to simulate workload on the Production server. LoadGen was running at MMB3 level while cloning the production LUNs. </li></ul></ul><ul><li>CLARiiON Array configuration: </li></ul><ul><ul><li>CLARiiON CX3 model 40 was used for this analysis. </li></ul></ul><ul><ul><li>Two LUNs of 400 GB each were carved out for holding the 2 Exchange Storage Groups (ESG1-DB and ESG2-DB) </li></ul></ul><ul><ul><li>Two LUNs of 60 GB each were carved out for holding the 2 Exchange Storage Group Logs (ESG1-Log and ESG2-Log) </li></ul></ul><ul><ul><li>Two more LUNs of 400 GB each were carved out for holding the 2 Exchange Storage Group Clones (ESG1-Clone and ESG2-Clone). This LUN will be used as the IR volume on the DPM Server. </li></ul></ul><ul><li>Time taken for cloning the entire 800 GB storage groups (2 X 400 GB LUNs): </li></ul><ul><ul><li>~ 4 hours </li></ul></ul><ul><li>Transfer rate achieved: </li></ul><ul><ul><li>(800/(4*60*60))* 1024 = 56.8 MB/Sec. (2X performance over LAN) </li></ul></ul>
  32. 32. PS Performance Impact using EMC SAN <ul><li>CPU Utilization </li></ul><ul><li>Response Time </li></ul>