2. Data Protection, Availability and Replication Andreas Tsangaris CTO, Performance Technologies

3. Overview of DR Technology Backup & Vaulting Mirroring &Replication Global Clustering SecsMinsHrsDays WksSecsMinsHrsDays Wks Recovery Point Recovery Time Backup & Vaulting

4. Backup for DR: Why? Normal steps in Disaster Recovery 1.Manual procedures - plan 2.Automated backup – restore 3.Data Replication / mirroring 4.Clustering

5. Backup for DR: Why?  Backup is the first approach to data continuity  Redundant systems replicate user errors, viruses and data corruption  System or component redundancy (RAID, mirroring) cannot replace backup  Backup tapes may represent the last valid copy of data  Backups are your last line of defense against total data loss  It is the chipset to deploy  It is the fastest to deploy  It is always the roll back for a complete DR

6. Backup for DR: How far (fast) you can go? Recovery Point with Backup (RPO): כAssume daily backups כData lost is at least a day כVery often it will be two days Recovery Time with Backup (RPO): כDR site preparation for restore כSystem restore (administrator oriented) כData restore

7. Site Recovery from Backup  Tape Backup with Offsite Vaulting כRPO = Time of last good backup stored offsite כRTO = Time required to recover from tape ∞ Transport tapes to recovery site ∞ Setup systems to receive data / Restore OS ∞ Restore from tape כTypically 1-3 days between RPO and RTO SecsMinsHrsDays WksSecsMinsHrsDays Wks Days Wks Retrieve from Vault Set Up Systems Restore from Tape Wks Days Tape Backup Offsite Vaulting RPORTO

8. Backup for DR: The tools  VERITAS NetBackup  Storage Hardware  Design  Procedures

9. NetBackup Architecture Master Server MediaServer MediaServer Clients Storage Domain

10. NetBackup: Multi-hosted Drives (SAN) NetBackupServer NetBackup Server & Robotic Controller NetBackupServer Data Path Robot Control Path Robot Requests 

11. NetBackup: Tape Multiplexing - Multistreaming Client or filesystem A Client or filesystem B Client or filesystem C Client or filesystem D t 32 streams per tape drive e.g. t Benchmarked at over 10Tb/hour

12. NetBackup: Multiple steams, multiple systems Run multiple client backup sessions simultaneously and stream the data to the same device remotely attached disks high-speed tape devices NetBackup server clients backup streams

13. NetBackup: Flat File Database John/doe/filetom fish/head/usr carol usr/foo/barmary one/fine/daypaul John/doe/filetom fish/head/usr carol usr/foo/barmary one/fine/daypaul John/doe/filetom fish/head/usr carol usr/foo/barmary one/fine/daypaul  Flat ASCII files כsimple כcompressible כbrowsable כvery tolerant כeasy to repair כeasy to sort, filter and report  Proprietary DB כcomplex כprone to corrupt כdifficult to rebuild כneeds defragmenting

14. NetBackup: Server Independent Restores NBU client  NetBackup Server 1 NetBackup Server 4 

15. NetBackup: True Image Recovery Ensures only your current files are restored Full Backup Sat 100 files Restore 141 files Ignoring 52 deleted Latest versions of 90 modified NetBackup: Without True Image Recovery we would get 193 files restored Restore valid files only Incremental Backup Tue 60 files modified 32 deleted 48 new Incremental Backup Mon 30 files modified 20 deleted 15 new Wed Disk Damaged

16. NetBackup: Network Bandwidth Throttling Other network-based applications Keeps backup workload from saturating your network NetBackup Clients  restrict by user  restrict by group  dynamically balanced NetBackup Servers Database applications

17. NetBackup Vaulting Process #1 – Duplicate / in line copy backups #2 – Eject duplicate tapes from tape library and prepare for transport #3 – Transport tapes to the offsite vault #4 – Record where each tape is located within the vault and when each tape will expire #5 – When tapes expire, notify the offsite facility #6 – Transport expired tapes back onsite #7 – Load tapes back into the tape library

18. Backup for DR: The tools  VERITAS NetBackup  Storage Hardware  Design  Procedures

19. NetBackup: Second-host Backup Disk Array Subsystem Tape Library LAN Ethernet FDDI ATM Offload backup processing to the backup server, freeing up cycles on the application server. Application Server Backup Server

20. NetBackup: Third Party Copy LAN Ethernet FDDI ATM Fibre Switch/Hub NetBackup Server Application Server Disk Array Subsystem Tape Library Catalog Third Party copy totally offloads the application server and the backup server from the actual data transfer

21. Backup for DR: The tools  VERITAS NetBackup  Storage Hardware  Design  Procedures

22. Automated Vaulting & Pre - restores SUNServer SUNServer X DR X Primary Standby Server

23. Design #1: Single Large Site  Multiple servers (more than 40)  Large data (more than 2 TB)  Central Enterprise storage box  Some servers boot from the SAN  DR site has equivalent servers

24. Design #1: Single Large Site The tools:  VERITAS NetBackup  VERITAS NetBackup Vault  SAN attached Tape library  Enterprise central storage  Procedures

25. Design #1: Single Large Site Disk Array Subsystem Tape Library Application Servers Backup Servers SAN LAN Backup Stage: SAN attached Servers: Snapshot Full backup (daily) LAN attached Servers: LAN Backup (Weekly Full & Daily incremental) Multiple Media Servers Multiplexing & Multistreaming VAULT: Dual in line copy Off site set of tapes

26. Design #1: Single Large Site Tape Library Backup Server Tape Vault stage: Export NetBackup catalog: Write to to a tape Transfer Tapes to DR: Directions for operators Insert tapes to DR’s library Initiate Site recovery: Import catalog Start automatic site restore Tape Library Backup Server PRIMARY SITE DR SITE

27. Example #1: Single Site Disk Array Subsystem Tape Library Application Server Backup Server SAN LAN Site Restore Stage: SAN attached Servers: Restore to locally mounted boot & data volumes LAN attached Servers: Use a small pre-installed OS & restore over the LAN

28. Example #1: Single Site Recovery Point: Average: 12 hours Worst case: 1 Day Recovery Time: Normally minimal (Site is pre-restored) Worst case: 8 hours (Backup time) plus 4 hours for tape transfer Disk Array Subsystem Tape Library Application Server Backup Server SAN LAN

29. Design #2: Multiple Sites  Multiple geographic sites (more than 6)  Small data footprint (less than 100 GB per site)  Large available bandwidth  Multiple database applications  Need for cross site recovery

30. Design #2: Multiple Sites The tools:  VERITAS NetBackup  VERITAS NetBackup Vault  Direct attached Tape library  Multiple direct attached storage boxes  DR site has spare servers and available attached storage

31. Design #2: Multiple Sites Application Servers Backup Server Direct Attached Disk Repository Application Servers Backup Server Application Servers Backup Server Tape Library Direct Attached Disk Repository Master Backup Server

32. Backup Stage: Full backups (daily): 1.Backup to disk (free up application faster) 2.Duplicate over WAN to central backup server Database log & incremental backup (hourly): 1.Backup to local disk AND 2.to central backup server (INLINE Copy) over the WAN Design #2: Multiple Sites Restore Stage:  Auto restore all (remote) full backups to local spare server  Use different disk volumes on the spare server  Auto restore all incremental & database logs Spare server is ready to recover! RPO: maximum 2 hours RTO: less than 1 hour (plus log replay)

33. Backup for DR: How far (fast) you can go? Recovery Point with Backup (RPO): כNormally 1 day כMay go up to 1 hour (WAN is essential) Recovery Time with Backup (RPO): כPre restored images כMay go up to 1 hour

34. Thank you!