200 likes | 228 Views
Replication for Disaster Recovery. Achieving Datacenter Availability. Recovery objectives. Wks. Days. Hrs. Mins. Secs. Secs. Mins. Hrs. Days. Wks. Data Loss (Recovery Point Objective). Downtime (Recovery Time Objective). Mirroring / Replication. Clustering. Backup.
E N D
Replication for Disaster Recovery Achieving Datacenter Availability
Recovery objectives Wks Days Hrs Mins Secs Secs Mins Hrs Days Wks Data Loss (Recovery Point Objective) Downtime (Recovery Time Objective) Mirroring / Replication Clustering Backup Restore from Disk Vaulting Restore from Tape
DATA APPLICATIONS What is Data Center Availability? Benefits: • Local & remote protection • Planned & unplanned • End-to-end integration • Application focused & …ONLINE
Start with storage virtualization DATA • Creates logical data containers for applications • Data becomes extremely portable • Data containers not tied to physical storage enclosures • Manage data containers, not individual blocks of storage • Backup/recovery • Snapshots • Remote replication
Replication can be as simple as mirroring Recommendation: Mirror the volumes • You may already own it • Hardware independent • Zero data loss • High performance Traditional: • Complex array replication • Expensive • Hardware dependent Replication Throughput
“Volume Replicator transfers 2 TB of data over 2000 km, over a 257 Mbps IP link every day. It does this consistently, without affecting the performance of applications.” IT Director, Bharti Tele-Ventures Asynchronous solutions are not all the same Recommendation: VERITAS asynchronous • Scalable performance • Storage independent • Data consistency • Any distance Traditional: • Performance limitations • Excessive hardware requirements • Incomplete disaster recovery 5000km 500km 50km
Why choose Veritas Storage Foundation for replication? • Scalable asynchronous replication • Volume level I/O over IP (any distance) PERFORMANCE • Persistent log (handles network outages) • Write order fidelity (ordered I/O commits) DATA CONSISTENCY • Minimum storage requirements • Bandwidth throttling RESOURCE UTILIZATION • Tiered storage support • Array independent HETEROGENEOUS STORAGE • 5 platforms, 1 solution • Rolling upgrades PLATFORM INDEPENDENT Network Outage
Add clustering for comprehensive disaster recovery Recommendation: Add clustering not hardware • Optimal server utilization • Any hardware • Simple configuration • 5 Platforms, 1 solution Traditional: • Hardware redundancy • OS restrictions • Poor utilization • Difficult configuration
Global Site Local Datacenter Manual recovery is not enough Recommendation: 1 Click Migration • Completely automated • Planned / Unplanned • Easy fail-back • Integration with replication Traditional: • Custom scripts • Manual restores • Multiple points of failure 1 CLICK
Planning & testing are imperative to recovery Recommendation: Plan thoroughly, test frequently • Cluster Simulator • VRAdvisor • FireDrill Traditional: • Rule of thumb planning • Partial testing • Full DR tests too complex
HA STANDARDIZATION HA/DR ARCHITECTURE APPLICATION/ DATABASE SOLUTIONS Put it together - Datacenter Availability
Optional Slides To be shared with under NDA
COMPATABILITY SOLARIS • SPARC: 8, 9, 10 • x64: 10 AIX • P4, P5: 5.3, 5.2, 5.1 • SAN Virtualization Replication • Centralized management console for Storage Foundation • 4 Node Oracle RAC & CFS replication • Bunker Replication HP-UX • Itanium & RISC: 11iv2 LINUX FEATURES • RedHat: 3, 4 • SuSE: 8, 9, 10 WINDOWS • Server 2000, 2003 • Longhorn Beta 2 Volume Replicator 5.0—Q2 2006 • Synchronous release for all operating systems • Support for latest database offerings (Oracle RAC) • Centralized Management THEMES
Bunker Replication: Any Distance & Zero Data Loss Traditional multi-hop approach • 5X storage requirement • Storage hardware lock in • Cascaded (more dependencies) • Heavy-weight bandwidth reqs • Data is 3 generations old Primary Site Bunker site Secondary Site VERITAS Bunker Replication approach • Reduces storage requirements • Reduced bandwidth requirements • Zero RPO over any distance • Little or no application impact
Bunker Replication How it works: Bunker Replication • Mirror or replicate log to bunker • Use IP or SAN for bunker • Async replication to secondary • Add bunker to existing RVGs • Supports UDP or TCP • RTO depends on size of buffer (and time to drain) • Supported with 3-way GCO • Bunker can be Sync, sync-override, async DR Site Asynchronous over IP Sync over IP or fibre channel Non-dedicated IP (only used to drain bunker SRL) Primary Site SRL Bunker Site
VVR 5.0 with SF RAC and SF CFSHow it works Benefits: Volume Replicator Option • Improved performance • Data consistency • Reduced database licenses costs • Clustered database replication • Clustered file system replication Description • Synchronous / asynchronous • Scales up to 4 nodes • All nodes write to volumes & SRL • Metadata shipping to coordinate SRL All nodes write to SRL & data volumes log-owner log-owner Rlink and IP up on logowner SRL written to by all - accessed only by log-owner Data Volumes
Storage Foundation Centralized Management Benefits: Centralized Management • Reduced management resources • Monitoring & Alerts • Near real-time reporting • Same look / feel as Storage Foundation web GUI Description • Web-based interface • Agent based • Management server architecture • Scalable to hundreds of nodes