1 / 20

MirrorView Agenda

Learn about the new enhancements in MirrorView, including additional mirroring relationships, the ability to share I/O and mirror data on the same SP port, and increased connectivity. Explore the benefits of fracture log persistence and the consolidation of remote mirroring. Discover how to create secondary mirrors, fracture mirrors, and perform partial synchronizations. Gain insight into MirrorView's internal protection mechanisms and the use of fracture logs.

pjiles
Download Presentation

MirrorView Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MirrorView Agenda • Review MirrorView • MirrorView enhancements • Additional mirroring relationships • I/O and mirror data can share same SP port • Fracture log persistence

  2. Mirror A Production B Production A Mirror B MirrorView Today Site A Site B Production host Standby host SAN Synchronous, bi-directional mirror Primary system Secondary system

  3. Mirror A Production B Secondary system MirrorView over IP Networks Site A Site B Synchronous, bi-directional mirror Production host Standby host IP = FC to IP converter Production A Mirror B Primary system

  4. Production A Mirror B Production C Mirror A Mirror D Production B Mirror C Primary Location B Production D Secondary Location C Primary Location D MirrorView Relationships Remote Primary and Secondary System • One Array can be both a source and a target • Up to four relationships per Array Secondary Location A

  5. Configuration Guidelines MirrorView and SAN Copy software cannot share the same SP port. Before installing the MirrorView enabler, you must deselect any MirrorView ports that a SAN Copy session is using. Otherwise, any SAN Copy sessions using the MirrorView port will fail. Note: The mirrored data is inaccessible until the secondary image is promoted to a primary image.

  6. Remote Mirroring Consolidation “Fan-In” Secondary Production A Mirror A Mirror B Mirror C Production B Mirror D Primary Mirror Location A 4:1 Fan-In Ratio Production C Primary Mirror Location B Production D Primary Location D Primary Location C

  7. Concurrent Mirroring • One source mirroring to two target arrays • Creates two off-site copies of the production data • Can be used snapped and presented to applications, development, or backup server “Fan-Out” Remote Secondary A Mirror A Primary A Production A Mirror A Remote Secondary A

  8. Creating a Secondary Mirror Adding a secondary mirror is accomplished through the Navisphere window

  9. Advanced Mirror Creation

  10. Multiple Mirrors Navisphere View Secondary mirrors New Orleans_ New Orleans_

  11. Fracturing a Mirror MirrorView allows mirrors to be administratively fractured through the GUI or command line via NaviCLI

  12. Increased Connectivity • Mix mirror and host I/O on same SP port • Increases maximum number of host attaches from 32 to 64 high availability hosts • FC/IP will still use this port for exclusive access for extended replication

  13. Brocade 2800 Brocade 2800 Brocade 2800 Brocade 2800 40 Km 18 Km SITE A SITE B RS6000 F80 (7) AIX 5.1 Windows NT W2000 Adv Server Brocade2800 CLARiiON 3 FC4700 Access Logix MirrrorView 50 secondary LUs Memory cache 80% W - 20% R CLARiiON 2 FC4700 Access Logix MirrrorView 24 primary LUs NetWare Novell e-mail File and print server CLARiiON 1 FC4700 Access Logix MirrrorView 26 primary LUs Data Center

  14. Primary host Secondary host MirrorView mirror Production information Mirror Partial resynchronization Primary CLARiiON FC4700 Secondary CLARiiON FC4700 MirrorView’s Internal Protection • Write intent log • Recently modified regions of the LUN • After a short period of time the bits in the WIL are cleared • If one or both SPs fail, only the LU regions marked in the WIL are recovered • LU trespass when both SPs are healthy does not require the use of a WIL to maintain mirror consistency • Fracture log • Tracks changed regions on primary disk when secondary system is unreachable due to link failure • When secondary system becomes reachable, fracture log is used to resynchronization changed data

  15. Fracture Log Persistent fracture log • Fracture log references write intent log stored on disk • Persistent when write intent log (WIL) is enabled • Avoids full sync with secondary in the event of a rolling disaster • That is, primary SP fails when secondary is fractured • Nothing to configure, the WIL just protects more scenarios

  16. Persistent Fracture Log Scenario Partial Synchronization Only 1. A link failure starts primary fracture logs 3. Only a partial synchronization is needed after the hardware recovers 2. Changes are also recorded in the write intent log on the primary image’s array Array A Array B

  17. MirrorView Summary • Looked at the new MirrorView features • Additional mirroring relationships • Four arrays fan in to a single array • Single array to two secondaries • I/O and mirror data can share same SP port • Increases initiators to 128 • Fracture log persistence

  18. Summary • MirrorView • Support for secondary mirrors • Added flexibility for mirror relationships • 4:1 fan in mirrors • Persistent fracture log • Mirror and I/O traffic on high port

  19. Reference • Powerlink.emc.com • EMC.com Technical Library • Your local EMC Systems Engineer

  20. Closing Slide

More Related