Every year one out of 500 data centres will experience a severe disaster
43% of companies experiencing disasters never re-open, and 29% close within two years
93% of business that lost their data centre for 10 days went bankrupt within one year
81% of CEOs indicated their company plans would not be able to cope with a catastrophic event
Components of Effective DR DR Recovery Facility Primary Infrastructure Designed for Resilience and Recoverability Processes And Procedures Operational Disaster Recovery And Business Continuity Plan
Copy from a template library a virtual machine with the appropriate Windows OS service packs and the Backup Agent pre-installed
Register and start VM, edit IP addresses
Restore from tape into VM using backup server
Compare Recovery Steps Find hardware Configure hardware / partition drives etc. Install Operating System Adjust Registry entries, permissions, accounts Install backup agent Find hardware Install VMware with Templates “ Single-step automatic recovery” from backup server “ single-step automatic recovery” from backup server Physical to Physical Do Once Repeat for each box Physical to Virtual Repeat for each box
Synchronous – data is written simultaneously to both SANs. The write operation is not completed until both individual writes are completed. This will require a communications link between both sites operating at least 1 Gbps.
Asynchronous – data is not written real-time to the backup unit. Data is buffered and written in blocks. This will require a communications link between both sites operating at least 2 Mbps.
CommVault QiNetix ContinuousDataReplicator
Virtualisation Resource Allocation and Configuration Analysis
How much resources to leave free to cater for server failure?
VM1 VM2 VM3 VM4 Limit Threshold Reservation Threshold Actual Usage VM5 VM6 VM7 VM8 Server 1 Server 2 HA Cluster
Virtualisation Resource Allocation and Configuration Analysis
Critical (or all virtual servers) will be restarted on other physical server(s)
VM1 VM2 VM3 VM4 VM5 VM6 VM7 VM8 Server 1 Server 2 VM1 VM2 VM3 VM4 X HA Cluster
SCOM monitors agentless servers. This is aimed at IT environments where agents could not be installed on a few exception nodes. Agentless monitoring is limited to status monitoring only.
Agents are installed on servers. SCOM lets you manage applications running on servers.
Server Discovery Wizard
Allows for server lists to be imported from Active Directory, from a file, or from a typed list. It also allows the list to be filtered using LDAP queries, as well as name– and domain name–based wildcards.
State View - Provides you with a real-time, consolidated look at the health of the computers within the managed environment by server role, such as Active Directory domain controllers, highlighting the systems that require attention.
Diagram View - Gives you a variety of topological views where the existence of servers and relationships are defined by management packs. The Diagram View allows you to see the status of the servers, access other views, and launch context-sensitive actions, helping you navigate quickly to the root of the problem.
Alerts View - Provides a list of issues requiring action and the current state and severity of each alert. It indicates whether the alerts have been acknowledged, escalated, or resolved, and whether a Service Level Agreement has been breached.
Performance View - Allows you to select and display one or more performance metrics from multiple systems over a period of time.
Events View - Provides a list of events that have occurred on managed servers, a description of each event, and the source of the problem.
Computers and Groups View - Allows you to see the groups to which a computer belongs, the processing rule groups with which it is associated, as well as the attributes of the computer.
Virtualisation Improve Utilisation Spare Logical Drive 1 = 2 Disks Logical Drive 2 = 8 Disks Logical Drive 3 = 3 Disks 1 Hot spare 550 GB of wasted space 14 x 72 GB disks = 1 TB capacity Vol 0 Data Parity Database Data Data Data Data Data Data Data Parity Home Directories Data Data Parity 140 GB 370 GB 40 GB
Flexible Volumes Improve Utilisation Logical Drive 1 = 144GB Logical Drive 2 = 576GB Logical Drive 3 = 216GB 1 Hot spare Spare Database Home Dirs Vol0 400 GB used 600 GB of Free Space! 14 x 72 GB disks = 1 TB capacity Data Data Data Data Data Data Data Data Data Data Data Parity Parity Aggregate
Storage management and administration is very vendor specific
Most vendors require different skills for different storage systems
Hardware is not cross compatible
The Unified Storage Architecture Advantage Incompatible silos Compatible family Platforms HP, EMC, DELL, IBM Storage Virtualisation Software & Processes Incompatible software; different processes Unified software; Same processes Experts & Integration Services Lots of experts and integration services Reduced training & service requirements
Virtual Storage Environment / EMC – Comparison Virtualisation: Architectural Simplicity Multiple Concurrent Protocols Integrated Mgmnt, DR, BC, ILM, D2D, … Celerra Symmetrix / DMX and CX ONLY Virtual Gateways HP, IBM, HDS, SUN The EMC Effect? - Complexity
8 Dissimilar Operating Systems
8 Dissimilar Mgmnt GUI’s
Dissimilar DR, BC, …
CentraStar - 6 1 - FLARE OE 5 - Enginuity 2 - FLARE 8 - MS Win 3 - Dart 4 - RHEL 2 - FLARE 8 - MS Win External server w/MS Win and CLARalert required to support CX dial/email home support (compare to AutoSupport). Virtual Gateway Limited iSCSI Support DMX Series CX3-20 CX3-40 AX150/S EMC FC CX3-80 CX3-10 NS40G NSX NS80G Centera CX300i AX150i iSCSI Only EMC IP NS80 NS40 NS350
Managing Disk Based Backup Through Storage Virtualisation Single Instance Storage (Deduplication)
Backup Integration Snapshot and Snapshot Restore Backup and Recovery Software Disk Based Target Secondary Storage Short-Term Local Snapshot Copies Mid- to Long-Term Disk to Disk Block-Level Backups Client Drag-and-Drop Restores Changed Blocks Primary Data 9AM 12PM 3PM Snapshot Snapshot Snapshot Primary Storage Instant Recovery
Advanced Single Instance Storage User1 presentation.ppt 20 x 4K blocks User2 presentation.ppt Identical file 20 x 4K blocks User 3presentation.ppt Edited, 10 x 4K User4 job-cv.doc Different file 8 new 4K blocks = Identical blocks Data Written to Disk: With ASIS: 38 blocks Without ASIS: 75 blocks
Enabling greater Data Management Through Storage System SnapShots
System writes modified data block to new location on disk (C’) C’ Snapshot File: FILE.DAT A B C Active File System File: FILE.DAT Disk blocks
Snapshot Internals Active file system version of FILE.DAT is now composed of disk blocks A, B & C’. Snapshot file system version of FILE.DAT is still composed of blocks A, B & C C’ Snapshot File: FILE.DAT A B C Active File System File: FILE.DAT Disk blocks
Snapshot-Based Data Recovery User is offered this most recent previous version (and up to 255 older versions) User may drag any of these read-only files back into active service
Snapshots are State-of-the-Art Data Protection
Snapshots should be near instantaneous!
To create a point-in-time Snapshot copy requires copying a simple data structure, not copying the entire data volume
Additional storage is expended incrementally
only for changed blocks
only as data changes, not at Snapshot creation time
Avoids the significant costs associated with the I/O bandwidth, downtime, CPU cycles dedicated to copying and managing entire volumes
Replicates a filesystem on one storage system to a read-only copy on another storage system (or within the same storage system)
Based on Snapshot technology, only changed blocks are copied once initial mirror is established
Asynchronous or synchronous operation
Runs over IP or FC
Data is accessible read-only at remote site
Replication is volume based
SnapMirror Function SAN or NAS Attached hosts Source Source Step 1: Baseline Step 2: Updates Target LAN/WAN Target LAN/WAN SAN or NAS Attached hosts OR Immediate Write Acknowledgement Immediate Write Acknowledgement … ... of source volume(s) Baseline copy … ... of changed blocks Periodic updates
Storage Mirroring Internals Source Volume Target Volume Snap A Baseline Transfer
Storage Mirroring Internals Source Volume Target Volume Completed Target file system is now consistent, and a mirror of the Snapshot A file system Source file system continues to change during transfer Snap A Baseline Transfer Common snapshot
Storage Mirroring Internals Source Volume Target Volume Snap B Target volume is now consistent, and a mirror of the Snapshot B file system Completed Incremental Transfer Snap A
Storage Mirroring Internals Source Volume Target Volume Snap C Completed Target volume is now consistent, and a mirror of the Snap C file system Incremental Transfer
Volume 2 Result: Easily create new permanent volume for forking project data
The Pain of Development Prod Volume (200gb) Pre-Prod Volume (200gb) QA Volume (200gb) Dev Volume (200gb) Test Volume (200gb) Sand Box Volume (200gb) 1.4 TB Storage Solution 200 GB Free Create copies of the volume Requires processor time and Physical storage
Clones Remove the Pain Prod Volume (200gb) Pre-Prod Volume QA Volume Dev Volume Test Volume Sand Box Volume 1.4 TB Storage Solution Create Clones of the Volume – no additional space required Start working on Prod Volume and Cloned Volume Only changed blocks get written to disk! 1 Tb Free
Ideally… Primary Production Array Secondary Array Mirror Create Clones from the Read Only mirrored volume Removes development workload from Production Storage!
Rapid Microsoft Exchange Recovery through Storage Systems Technologies
Why use Storage Systems Series for Exchange Data?
Just a few off the top…
Snapshot copies “snapshots”
Data and snapshot management, replication
Flexible and easy, dynamic provisioning
iSCSI, cost effective and gaining on Fibre Channel
Excellent high-end FCP, clustering and MPIO options
Tight Windows OS (incl. MSCS) and Exchange 5.5., 2000, 2003 and 2007 Server integration (SME, VSS on Windows 2003, etc.)
Ability to backup DB faster with fewer resources and without any storage knowledge
Reduces Mean Time to Recovery on failure
More frequent backups Less logs to replay Faster Recovery
Ability to backup and restore DB without any DB knowledge
Space, time & infrastructure efficient backups, restores and clones
Increased productivity and storage utilization
Technical Details – Consolidated SQL Server Storage Primary Data Center SQL Server iSCSI or FCP 1 Benefits:
Simplified, centralized management
Shared storage for improved utilization
Better system availability
Consolidate SQL Server storage on storage system 1 2 2 Add disks and expand volumes on the fly without downtime 3 3 Cluster for higher availability
Technical Details – Simplified Backup » More Frequent Backups Primary Data Center iSCSI or FCP SQL Server
Eliminate backup windows
Automation reduces manual errors
More frequent backups reduce data loss
No performance degradations
Benefits: SnapManager automates data management for SQL Server 1 1 Time to backup: seconds Snapshots 2 2 Snapshots for near-instantaneous backups 3 3 Backup multiple databases simultaneously
Technical Details – Rapid Restores » Less Downtime Primary Data Center Time to restore: minutes iSCSI or FCP SQL Server Standby Server
Fast and accurate restoration of SQL Server
Reduce downtime from outages
Automation saves administrative time
Benefits: Near-instant restore from online snapshot Snapshot 1 1 Roll transaction logs 2 2 Automated log replay for current image 3 3 Restore single or multiple databases 4 4 Rapid failover to standby server
Technical Details – Simple & Robust Disaster Recovery Primary Data Center DR Site iSCSI or FCP iSCSI or FCP Failover DB Server IP network
Ensures business continuance
Minimizes length of outages
Cost effective – efficient use of existing IP network
Benefits: System Mirroring 1 Storage Mirroring replicates SQL Server data to remote location 1 Replicate over existing IP networks 2 2 Failover to DR site After Failure 3 Rebuild primary site from DR site 3
Technical Details – Volume Mount Point (VMP) Support
Drive letter limitations in SMSQL
Only 26 available drive letters in a system.
Minimum for 2 LUNs required for database migration.
Limitation for customers who have hundreds of databases.
The customer might not want to have multiple databases on one/two LUN.
Again one database might span multiple LUNs.
LUN restore is performed on whole disk.
To support individual database restore, each database will require its own LUN and drive letter.
Verification will fail on Local server if free drive letter exhausts.
SMSQL migrates Resource database along with master database
Resource database will not be listed in the Configuration Wizard
Internally SMSQL migrates it while it migrates master database
It will be migrated to the same location as master database
This is supported only for SQL Server 2005
SnapShot Management with SQL Server – Summary
SnapShot Management with SQL Server:
Helps consolidate SQL Server on highly scalable and reliable storage
Efficient , Predictable , Reliable Backup, Restore and Recovery for SQL Server databases
Allows dynamic provisioning of storage for databases
Allows DBAs to efficiently perform database backup, restore, recovery, clone operations with minimum storage knowledge
Facilitates Disaster Recovery and Archiving
Rapid Recovery of Oracle DB Through Storage Systems Technologies
Oracle Enterprise Manager Grid Control Monitor Trends and Threshold Alerts Monitor Key Statistics Monitor Utilization
Ships with Oracle Enterprise Manager
Developed, maintained and licensed separately by Oracle
Manage Storage System from Oracle Enterprise Manager 10 g Grid Control
Oracle ASM Automatic Storage Management Disks Logical Vol File System Files Tablespace Tables Disk Group Logical Vol File System File Names Tablespace Tables Before ASM ASM Networked Storage (SAN, NAS, DAS) 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010
Compatible Storage Adds Value to Oracle ASM Yes Yes Yes Yes Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Compatible Storage Yes No Thin provisioning of ASM Disks Yes No Space efficient Cloning Yes No Free space management across physical disks Yes No I/O prioritization Yes No Balance I/O across Physical Disks Yes No Stripe data across Physical Disks Yes Yes Balance I/O across ASM Disks Yes Yes Stripe data across ASM Disks Yes Yes Active Block corruption detection Yes Yes Passive Block corruption detection Yes No Lost disk write detection Yes Yes Protect against Single Disk Failure Yes No Storage Snapshot based Restores Yes No Storage Snapshot based Backups Data Protection Storage Utilization Performance Yes No Protect against Double Disk failure Data Resilience Oracle ASM + Compatible Storage Oracle ASM
Integrated Data Management Approach Go from this… Centralized Management X High cost of management X Long process lead times X Rigid structures X Low productivity + Administrator productivity + Storage flexibility + Efficiency + Response time … to THIS Server-Based Management Application-Based Management Storage Management Integration and Automation Data Sets and Policies
Create Snapshot copie s of replicas for instant SnapShot Restore of working databases
PROD Test/Dev/DR Clones Develop ● Test ● Deploy
Traditional Approach: Application Development and Testing
Production database 100GB
Mirror copy 100GB
Development copies 300GB
Testing copies 300GB
8x actual storage requirement
Production Test 1 Test 2 Test 3 Mirrored Copy Dev 1 Dev 3 Dev 2
SAN Approach: Application Development and Testing
Production database 100GB
Mirror copy 100GB
Development copies 30GB
Testing copies 30GB
Over 67% reduction in storage required
Near instantaneous copies
Ability to have many more test and dev copies
Test 1 Test 2 Test 3 Production Mirrored Copy Dev 1 Dev 3 Dev 2 Assumption: up to 10% change in data in the test and dev environments more clones = higher productivity
Oracle Applications Lifecycle Need reliable backup and recovery solution Install Implement Re-organize Upgrade Patch Deploy Pain Points Plan Tune & Maintain Solutions Configure systems, forecast storage accurately Provision and maximize utilisation with FlexVol Testing requires duplicate data, lengthy and expensive process Flexible Clone: Fast & space-efficient data duplication Backup and Recovery solution with Snapshots, SnapShot Restore Mirror prod. data to test and dev system, lengthy process Mirror data with Storage Mirroring, ReplicatorX Create several clones, lengthy process, expensive Create clones with FlexClone, automate with SMO Need reliable backup and recovery solution Use Snapshots, SnapShot Restore, Need reliable backup restore, and DR solution Automate backups, restore with SMO, SnapMirror, ReplicatorX for DR