1 / 39

SnapView Overview for Local Replication

SnapView Overview for Local Replication. Replication Options with EMC CLARiiON. SnapView Point-in-time Replicas Snapshots Full Binary Replicas BCVs Instant Recovery. MirrorView/ Synchronous Synchronous Remote Replication Solution for Disaster Recovery. MirrorView/

bryant
Download Presentation

SnapView Overview for Local Replication

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. SnapView Overview for Local Replication

  2. Replication Options with EMC CLARiiON • SnapView • Point-in-time Replicas • Snapshots • Full Binary Replicas • BCVs • Instant Recovery MirrorView/ Synchronous Synchronous Remote Replication Solution for Disaster Recovery • MirrorView/ • Asynchronous • Low Cost and Long • Distance Mirroring • Consistency Groups SAN Copy Inter Array Data Mobility Full/Incremental Copy

  3. Agenda • SnapView Overview • SnapView BCVs • SnapView Snapshots • SnapView Instant Restore • SnapView Management

  4. SnapView: Two Local Replication Methods Full Image Copy • SnapView is a software product for the CLARiiON CX300 and up (also FC4700) • Storage-based product; uses no host cycles • Provides up to 8 replicas per source – each • Full image copies of production information, called business continuance volumes (BCVs or clones) • Logical point-in-time views of production information, called snapshots • SnapView replicas provide concurrent data access • Enables increased operational efficiencies BCV Clone Production Information Snap snapshot Logical Point-In-Time View

  5. SnapView – Instant Restore ProductionHost • Production Host remains online • Can be taken offline if needed • SnapView Replica restores Source • Return to original production data at time of split • Can be mounted to secondary host to verify data consistency Production Recovered Production SecondaryHost BCVorSnapShot 

  6. LUN Driver Stack Location Host I/O • SnapView driver lies below other layered drivers, so it can be used with any of them • Provides read/write replica of LUN, without affecting contents of LUN • Normal LUN • Secondary MirrorView image • BCV image • Can serve as source LUNfor SAN Copy Front-end driver Host-side driver SAN Copy driver Clone driver SnapView driver FLARE driver Back-end driver physical disks

  7. Agenda • SnapView Overview • SnapView BCVs • SnapView Snapshots • SnapView Instant Restore • SnapView Management

  8. BCVs: Full Image Copies • Physically independent point-in-time copies of source volume • Available after initial synchronization • Once established, no performance impact between source / BCV • Can be used to restore or replace source in event of hardware or software error • Can be incrementally re-established • Only changed BCV data overwritten by source • Up to eight BCVs can be established against a single source LUN concurrently • Can be any RAID type or drive type(regardless of source) Full Image Copies BCV BCV BCV BCV BCV BCV BCV BCV Clone Production Information

  9. BCV Synchronization Operation • After initial copy, BCV accessible as independent LUN • BCV must be fractured • Must be in different storage group from Source/other BCVs • Refresh BCVs with contents of Source • Overwrites BCV with Source data • Host access allowed to Source / not to BCV BCV 1 refreshed to contents of source LUN SourceLUN BCV 1 fractured from source LUN… Production Host x BCV 1 BCV 2 BCV 8 … and presented to backup host . . . X Secondary Host

  10. BCV1 BCV3 BCV2 B B B A A A Source B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Fracture Log • Write to an extent on Source • BCV not changed • Entry in Fracture Log • Extent copied during sync • Write to an extent on BCV 3 • Source not changed • Entry in Fracture Log • Both extents copied during sync 1 ’ 1 1 1 ’ Fracture Logs

  11. Agenda • SnapView Overview • SnapView BCVs • SnapView Snapshots • SnapView Instant Restore • SnapView Management

  12. SnapShots: Logical Point-in-Time Views Logical Point-In-Time View • Pointer-based copy of data • Takes only seconds to create a complete snapshot • Requires only a fraction of original file system • Snapshots can be persistent across re-initialization of the array • Can be used to restore Source data • Up to eight snapshots can be created per Source LUN snapshot snapshot snapshot snapshot snapshot snapshot snapshot snapshot Snap Production Information

  13. Block A Block B Block C Block D 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SnapView “Copy-on-First-Write” Block C in the Reserved LUN now reflects the change that the Production Application made and the pointer is updated to point to the Reserved LUN for Block C Source LUN Block A Production Host Reserved LUN Block B Updated Block C Block D 1 OriginalBlock C SP Memory Secondary Host

  14. SnapView Sessions • Multiple concurrent sessions per Source • Source LUN can have up to 8 sessions • Each secondary host can view a single session SourceLUN Production Host 9:00 amsession Secondary Host1 10:00 amsession . . . 11:00 amsession 4:00 pmsession Secondary Host8

  15. Source LUN A Source LUN B Reserved LUN 1 Reserved LUN 1 Reserved LUN 2 Reserved LUN 3 Reserved LUN 4 Reserved LUN 5 Reserved LUN 2 Reserved LUN 6 Reserved LUN 3 SnapView Sessions and Reserved LUNs • Source LUN A • Active sessions A-1 and A-2 – Reserved LUN 1 • Source LUN B • Active session B-1 – Reserved LUN 2; 3 when needed Session A-1 Session A-2 Reserved LUN Pool Controlled by SPB Reserved LUN 1 Reserved LUN 2 Reserved LUN 3 Session B-1 Controlled by SPA

  16. Using Snapshots with BCVs • BCVs can be snapped • Snapping a BCV delays snap performance impact until BCV is refreshed or restored • Increases max copies of data Source BCVs 1, 8 fractured from source LU Production Host X X BCV 1 BCV 2 BCV 8 ... Secondary Host … … 1_ss1 1_ss2 1_ss8 8_ss8

  17. Agenda • SnapView Overview • SnapView BCVs • SnapView Snapshots • SnapView Instant Restore • SnapView Management

  18. SnapView Instant Restore • Restore a SnapView Source LUN contents to different point-in-time version • Any BCV or snapshot session may be selected • Does not impact other BCV or session data • Change in Source LUN appears instantaneous to host • Data copied to Source LUN “behind the scenes” • During restore, Source LUN is accessible for host reads and writes • Other BCVs/sessions available for host I/O • Invoked via Navisphere GUI or Navisphere CLI • User-configurable copy rate

  19. Source Restore with SnapView Replicas • Restore Source LUN with contents of BCV • Overwrites Source with BCV data • Using Fracture Log to determine modified regions • Host access allowed to Source / not to BCV • Source “instantly” appears to contain BCV data production server “instantly”sees 9 AM data SourceLUN9 AM SourceLUN3 PM Replica remains“Golden Copy” “flush and forget” source LUN restoredto 9 AMcopy of data Production Host X X X Other point-in-time replicas preserved 9 AMBCV 10 AMsnapshot 2 PMBCV X . . . Secondary Host1 Secondary HostN

  20. Agenda • SnapView Overview • SnapView BCVs • SnapView Snapshots • SnapView Instant Restore • SnapView Management

  21. Managing SnapView via Navisphere • Management via GUI and/or CLI: • Creation of BCVs and snapshots • Periodic update of BCVs and snapshots • Deletion of BCVs and snapshots

  22. Host Access to SnapView Replicas • Management via GUI and/or CLI: • Assignment of BCVs and snapshots to storage groups • Replicas belong in separate Storage Group for secondary host access • PowerPath 4.0 or Replication Manager family can be used for same-host access

  23. Microsoft VSS – Windows Server 2003 WritersExchange2003 • Microsoft Volume Shadow Copy Services • Mechanism for coordinating point-in-time backups • Shadow Copy volume hidden and read-only • Three different VSS roles (and APIs): • Writers (applications) • Requestors (backup applications) • Providers (software or hardware point-in-time services) • CLARiiON VSS Hardware Provider • Packaged with admsnap (requires NaviCLI) • Automatically creates snapshots, sessions, clones, storage groups vss RequestersNetWorker 7.1 Hardware ProvidersCLARiiON

  24. SnapView – Making Information Available Production Host • SnapView creates multiple point-in-time copies of production information, non-disruptively • SnapView enables increased operational efficiencies, allowing simultaneous • Creating Backups • Report Generation • Decision Support • Data Warehousing • Application Testing • SnapView providesmultiple points ofdata recovery Secondary Hosts Snapshot 1 Production Information Snapshot 2 Snapshot 3 Application Testing Snapshot 4 Snapshot 5 Snapshot 6 Snapshot 7 BCV 1 Snapshot 8 Tape Backup BCV 2 Production Information Report Generation TapeBackup BCV 3 Decision Support Tools

  25. Summary – SnapView Local Replicas • Provides read/writable replicas for concurrent use • Increases productivity, enabling users to do more with less • Provides up to 8 (of each) per Source LUN • Allows both BCVs and snapshots of a Source LUN (and snaps of BCVs) • Provides multiple restore points for Source LUN • Any BCV or session may be used for restore • Data on other replicas is not impacted

  26. CLARiiONwith SnapView allows users to take the snapshot, start the session, stop it, change some file and start a new session—all with the volume still mounted to the server! Create the mounting/snapshot Script and run it ONCE!     Another script refreshes the sessions as required Changes appear on the session Monitor weekly HP's Business Copy snapshots have to be taken, mounted, dismounted, destroyed, and then retaken to update data Create the BC scripts to do the snapshots Mount the drives This has to be repeated each time you want an update  Each time they run there's a possibility for error  Customer example: On the client's backup server, someone created a network connections on using drives F and G; when the script ran, it could not mount the correct volumes since the letters were already in use The backups got the wrong data volumes for a couple of days until someone realized the error Since there weren't any obvious error messages, the ONLY reason it was discovered was when an administrator tried to restore a file for a user and it wasn't there!  In fact, NOTHING was there, since the wrong volumes were connected Scripting SnapView vs. Business Copy

  27. SnapView vs. Business Copy

  28. SnapView Integration Modules simplify CLARiiON-based backup and recovery Application coordinated backup and recovery process Non-disruptive, automated and reliable backups Uses Exchange consistency check and log management to validate copies Faster recovery Leverages SnapView instant recovery Easy to deploy and manage Designed for Exchange Administrator Rapid assessment and implementation Accelerate Exchange migrations Speed process through consolidated procedures Integrated with Windows 2003 VSS (Q1 ‘04) Lower total costs of Exchange Consolidate, automate, and simplify SnapView Integration Modules for Exchange and SQL EVA does not have this level of application integration • More cumbersome and difficult for customers to integrate this functionality • More manually intensive

  29. Pain Points:Navisphere Creating, Growing, and Closing Storage Deals

  30. Sometimes Things Don’t Go As Planned – No. 1

  31. CPU Failure • How reliable are your servers? Any recent failures? • How quickly were you able to get it up and going again? • What is the process to restore the server? • What is your manufacturer’s response time? • Can you get to your information if your servers fail?

  32. CPU Failure A. Problem: • If a server fails, its local data is not available B. Traditional solution: • Call IT Help Desk! • If you’re lucky, they can get data from backup tapes – in a day or two. . . • . . . That is, if they backed up recently. . . • . . . And, the changes you made since the last backup are forever lost.

  33. Traditional CPU Recovery 9

  34. Sometimes, Things Don’t Go As Planned – No. 2

  35. CPU Recovery with Networked Storage 1 SAN NAS

  36. CPU Recovery with Networked Storage 2 SAN NAS

  37. CPU Recovery with Networked Storage 3 SAN NAS

  38. CPU Failure A. Problem: • If a server fails, its local data is not available B. Traditional solution: • Call IT Help Desk! • If you’re lucky, they can get data from backup tapes – in a day or two. . . • . . . That is, if they backed up recently. . . • . . . And, the changes you made since the last backup are forever lost. C. EMC Consolidated Solution: • Simply re-assign the disks that contain the data to another server • As simple as a few mouse clicks D. Business Benefit: • Minimal downtime • Information is accessible, and the business continues to operate

More Related