Академический Документы
Профессиональный Документы
Культура Документы
Defining Terms: Remote Mirroring and Data Replication Remote Mirroring generates a mirrored image of
Checklist
data on two or more disks Data Replication scans data periodically for changes and copies new data to the other disk or file system on another system Factors to consider
Value of data (and lost data) being backed up Costs for network bandwidth and software Your existing infrastructure Product features (OS, File System, Disk or Application)
More
Synchronous
Data Protection
Asynchronous
Point In Time
Less
More
What are you protecting? (applications, transactions, files, disks) What level of protection do you need? (Well come back to this!) What are your network requirements? What is your expected budget for this project? Is the ROI greater than acquisition costs? What will best fit your larger business continuity strategy?
Best Practice
Fundamentals
Makes comparisons and only copies changes (at disk or file level)
Key Advantages
Can be less expensive Can be flexible to replicate all enterprise data regardless of disk system Copies only the most important files/data Many-to-one replication architectures available Limits amount of data transferred, reducing network load and cost
Key Disadvantages
Warning
Less expensive, host-based (or array-based) file and block replication Specific to storage vendor, OS or file system
Database Replication
Typically done by replicating or mirroring log files A number of variations:
Continuous Mirroring: updates DBMS as changes(adds, updates, deletes) occur Change Data Capture: captures DBMS changes and stores them until a predetermined replication time Full Copy Refresh: replicates entire DBMS copy to target systems (done to resynchronize DBMS after outage)
Trigger-based native DBMS is not usually appropriate for DR because of high system and
Is dependent on OS, host and array support Advantage: it takes up less network bandwidth than mirroring Disadvantage: resynchronization of data is an art
If you do not resynchronize, you must build snapshot mirror totally from scratch
New Kid on the Block: Virtualization and Disaster Recovery Virtualization software offers a new alternative
Data replication (over both IP and Fibre Channel) Snapshot High Availability Fail-over A cost-effective approach to disaster recovery
Key Challenges
Recreating the virtualization system can be difficult Specifying file level information for replication can be difficult Warning Still a relatively new technology, so test well Research virtualization players thoroughly
Ask hard questions about number of customers doing this
Hot Site Remote Disk Mirroring Data Replication Snapshot Campus Disk Mirroring
More
Importance Of Data
Electronic Vaulting
Tape Onsite Tape-Backup Offsite More Less Less
Myriad of network transport choices boil down to two fundamentals (from the POP out)
Fibre IP
Specific Network Challenges for Remote Mirroring and Replication Enterprise network performance is many times
What tools do the remote mirroring/replication vendor provide for performance on a Metro SAN?
Network throttling adjusting data amounts sent over wire Compression compressing data to take up less network bandwidth Time-stamping marking data at time saved or accessed
Tip
Remote Site
ATM, T3/E3, OC3+ or Fibre Optic (DWDM) Service Provider Connectivity Services Mirroring/Replication Software Edge of Network Equipment (Director, Router or DWDM)
Key Features
Performance
Full performance (200-M bits/sec. unidirectional) Bi-directional channel protocol, runs over at 1.063 G bit/sec. Dedicated Fibre (depends on transport)
Length of Distance
8 km for full performance, 50% performance @ 20 km 100 km distance limitation
Still in proof-of-concept Depends on applications, stage, but promise of 1 TB service, connection points per hour over IP FCIP - primary for Metro SANs
IP Network Options
Private Router Backbones
Leased, dedicated lines Optimized for performance (racing the sun)
xSP VPNs
Customer purchases edge routers and ISP provides shared backbone Leverages Multiprotocol Layer Switching (MPLS) for better Quality of Service
Internet . . .
Not a disaster recovery tactic I would trust
Checklist
Tips To Consider When Speaking With Your Service Provider Ask your xSP to provide you what their expertise
is in storage services
Consider how you could leverage your existing connectivity services to establish a cost-effective service contract for your backup services Ask for a latency/network performance SLA Your primary xSP should have partners to assist with storage services if they dont
Consider leveraging storage vendor relationships to find service providers that can do integration Do or have done a network analysis to determine requirements for your backup services
Determine if outsourcing disaster recovery services for Data Mirroring and Replication services
Do I have the skills, personnel and infrastructure?
Best Practice
Come up with a ROI calculation for your data protection strategy Guidelines to remember
Calculated over three-year term The higher the ROI, the more favorable the project TCO vs. ROI ROI wins out
Best Practice
Conclusions
Dont forget the fundamental goal: Disaster Recovery Consider your options for mirroring/replication and make a metric to measure them by
ROI analysis is one way of measuring options
Theres not one solution strategize on ways to prioritize your data protection
Questions?
Jamie Gruener
jgruener@yankeegroup.com