1. EMC SRDF and TimeFinder on Symmetrix with Open Systems

4. Decision Drivers to Consider Recovery-Point Objectives PRIMARY DECISION DRIVERS Business Considerations Technical Considerations Cost Recovery-Time Objectives Performance Bandwidth Capacity Recovery and Consistency Functionality, Availability

9. SRDF/S Functional Capabilities Yes – with TimeFinder Can use consistent remote point-in-time restore for disaster restart with immediate host access Yes – with SRDF/CG Can span a database over multiple storage frames and ensure application restart with consistent data 64,000 Maximum number of SRDF pairs with Enginuity 5874 Yes Can ensure all changed data captured for site-failback resynchronization Yes Can use space saving TimeFinder/Snap on remotely – replicated volumes Yes – with TimeFinder Can perform remote point-in-time operations (such as point-in-time splits) nondisruptively Yes – with TimeFinder Can have a consistent (restartable) point-in-time image for remotely - replicated volumes Yes Can be used with three site SRDF solutions Yes Can service I/O from remote volume, avoiding application failover SRDF/S Feature/Function

11. SRDF/S Mirror Advantage Site B Site A I/O request is serviced from R2 mirror volumes, avoiding application restart on Target with integrated cluster solutions LAN/WAN SRDF R2 R1 R1 R2

13. SRDF Incremental Resynchronization R1 and R2 invalid track tables merged for resynchronization Changed tracks on both the Primary and Secondary will be reflected for resync ensuring the highest level of data integrity Resynchronization from Secondary to Primary R1 UPDATED TRACK UPDATED TRACK Primary Secondary R1 R2 UPDATED TRACK UPDATED TRACK

14. SRDF Timestamp for Suspend/Resume SRDF Device Link Status :Not Ready (NR) Time of Last Device Link Status Change :Mon Oct 27 15:30:41 2008 Assist administrator in identifying that intersite network issues may exist and aids in determining data currency in event of site disaster Secondary Site Production Site Timestamp gets updated when link status changes occur and will be reported on both the R1 and R2 R2 R1

15. SRDF Group Support: Number Increased from 128 to 250 Groups Provides granularity and control for environment with a large number of mutually independent applications Maximum of 64 SRDF Groups per RA Director SRDF Secondary Site Production Site

16. Moving Dynamic Devices between SRDF Groups SRDF Group A SRDF Group B Can move SRDF devices between SRDF groups without requiring a full copy resynchronization Production Site Secondary Site R1 R1 R1 R1 R1 R1 R1 R2 R2 R2 R2 R2 R2 R2

21. SRDF/A Functional Capabilities Yes Can be used with three site SRDF solutions 64,000 Maximum number of SRDF pairs with Enginuity 5874 Yes Changed data resynchronization available for failback to primary site due to unplanned outage at primary site (failover to remote site occurs) Yes - SRDF Mode Change feature Can change asynchronous mode of operation to synchronous Yes Can have a consistent (restartable) point-in-time image on remotely – replicated volumes Yes – with TimeFinder Can perform remote point-in-time operations (such as consistent point-in-time splits) nondisruptively Yes – with TimeFinder Can use remote point-in-time restore for disaster restart with immediate host access Yes Can ensure all changed data captured for site failback resynchronization Yes Can insulate local application from remote I/O replication operation SRDF/A Feature/Function

30. SRDF/A and Adding or Removing Devices SRDF/A session remains active while adding or removing devices Production Site Secondary Site R1 R1 R2 R2 Can dynamically add and remove device pairs in an active session while maintaining the consistency of the existing set of devices WAN R2

31. SRDF/A R2 Site Consistency Indicator SRDF/A R2 Data is Consistent :True Production Site Secondary Site Provides administrator with consistency state of SRDF/A target data to aid in determining required disaster restart operations Now also reported on the R2 host as well as the R1 when the SRDF/A session is active and inactive R1 R2

32. SRDF/A Minimum Cycle Time SRDF/A now reduces data loss exposure to an absolute minimum for large workload environments ensuring data consistency Previous Cycle Times: 5 to 60 seconds Enginuity 5773 Cycle Times: 1 to 60 seconds Enginuity 5773 Cycle Times with SRDF/CG: 3 to 60 seconds Target Source N-1 Receive N-2 Apply N Capture N-1 Transmit R2 DSE DSE WAN

39. SRDF/A Customer Example Use with Open Replicator DMX HP-UX DMX HP-UX SRDF/A (>500 km) Production Environment Test and Dev CX HP-UX Open Replicator Clone Source LUN TF R2 TF R1

41. SRDF/AR Single-Hop No data loss achievable while reducing extended distance intersite network bandwidth requirements resulting in lower costs SRDF/AR Secondary Site Production Site TF R2 WAN TF/ R1 Std

42. Clustered SRDF/AR Single-Hop SRDF/AR restart and resumption when application restart occurs on other available cluster node Host Cluster SRDF/AR Secondary Site Production Site TF R2 WAN TF/ R1 Std

50. SRDF Migrate Option 1 of 2 Site A Site A Primary Secondary Facilitates migration of an existing R1 or R2 device to a new device and reconfigures the R1 and R2 relationship SRDF Migrate Set-up establishes a concurrent SRDF relationship New Site B R11 R2 R2

51. SRDF Migrate Option 2 of 2 Site A SRDF Migrate Replace pairs the new R1 to the existing R2 An integrated process to minimize planning and implementation time to migrate to newly deployed Symmetrix systems New Site A Primary Secondary Site B Relationships dissolved R11 R2 R2

54. Decision Drivers to Consider RPO PRIMARY DECISION DRIVERS Business Considerations Technical Considerations Cost RTO Performance Availability Capacity Recovery and consistency Functionality

57. TimeFinder/Clone Functional Capabilities 16 Maximum number of Clones for each production volume 8 Maximum number of Clones for each production volume providing changed data resynchronization with production volume Yes Can use consistent remote point-in-time restore for disaster restart with immediate host access at either secondary or primary SRDF site Yes – with TF/CG Can span a databases over multiple storage frames and ensure application restart with consistent data >50,000 Maximum number of TimeFinder/Clone pairs with Enginuity 5874 Yes Can ensure all changed data captured for resynchronization Yes – with SRDF Can perform remote point-in-time operations (such as point-in-time splits) nondisruptively Yes Provides protective restore with immediate host access during a restore Yes Can be used with three site SRDF solutions Yes Provides RAID 1, RAID 5, and RAID 6 protection TimeFinder/Clone Feature/Function

59. Remote TimeFinder/Clone Restore to SRDF R2 with R2 to R1 Restore Application access at production site as write protected restore from remote TimeFinder/Clone occurs Enables faster production site restoration when data restore from TimeFinder/Clone is required Secondary Site Production Site SRDF R1 R2 Clone

61. TimeFinder/Clone Consistent Split and Clustered Applications Ensures dependent-write consistency across multiple systems or across multiple devices within a system Oracle RAC Shared Cache Std Std Std Clone Clone Clone Std Std Std Clone Clone Clone ECA Split

65. TimeFinder/Snap Functional Capabilities 128 Maximum number of Snaps for each production volume 128 Maximum number of Snaps for each production volume providing changed data resynchronization with production volume Yes Can use consistent remote point-in-time restore for disaster restart with immediate host access at secondary SRDF site Yes – with TF/CG Can span a databases over multiple storage frames and ensure application restart with consistent data >50,000 Maximum number of TimeFinder/Snap pairs with Enginuity 5874 Yes Can ensure all changed data captured for resynchronization Yes – with SRDF/S Can perform remote point-in-time operations (such as point-in-time splits) nondisruptively Yes Provides protective restore with immediate host access during a restore Yes – on Workload site Can be used with three site SRDF solutions Yes Provides RAID 1, RAID 5, and RAID 6 protection TimeFinder/Snap Feature/Function

66. TimeFinder/Snap Device Support Large number of Snap device support per standard device for PiT operations Support for up to 128 Snap devices per standard device Snap Snap Snap Snap Snap Snap Snap Snap Standard Device

67. TimeFinder/Snap Economics Enable Frequent Copies 12:00 p.m. 9:00 a.m. 6:00 a.m Based on a 30% change rate Database checkpoints every three hours in a 24-hour period Point-in-time “images” Requires ~900 GB of additional capacity 3:00 a.m. 12:00 a.m. 9:00 p.m. 6:00 p.m. 3:00 p.m. Full-volume copies Database checkpoints every six hours in a 24-hour period Requires 12 TB of additional capacity Source 3 TB 12:00 a.m. 3 TB 6:00 p.m. 3 TB 12:00 p.m. 3 TB 6:00 a.m. 3 TB Source 3 TB Save Area ~900 GB

69. TimeFinder/Snap Consistent Split and Clustered Applications Ensures dependent-write consistency across multiple systems or across multiple devices within a system Oracle RAC Shared Cache ECA Split Std Std Std Std Std Std VDEV VDEV VDEV VDEV VDEV VDEV