Velkommen Backup & Snapshot v. Jørgen Weinreich / Arrow ECS Technical Specialist 1
Agenda Fra backup til restore produkt Politikstyret Backup Live Demo 2
IBM XIV Snapshots - Næsten uden begrænsninger Snapshot oprettelse/sletning sker øjeblikkelig Volume High performance med snapshots Uendeligt antal snapshots Differential snapshots spare plads Distributed snapshots on each server. Extremely fast memory operations Accessing snaps is as fast as accessing production volumes Nextra Physical View Snap Vol snap As Each Restore Host Server Volume Writes has from data, pointers shapshot it is placed in memory copy On a snapshot, each server simply to randomly the disks that across hold system the data in 1MB locally chunks points to original volume. memory only operation Data Module Data Module Data Module Data Module 3
Crash consistent backup A crash consistent backup may result in: Application data loss during recovery A backup that can not be recovered from Longer recoveries because of application and server consistency checks Has no additional impact to the application beyond moving the data Simple to do because you just copy the data with no concern for its state A consistent backup will Have no data loss during recovery Will always allow recovery Enables very quick recoveries because there is no consistency checking Enables finer grained recoveries. While the backup is in process, application performance may be impacted. Complex to do because you need to perform some co-ordination between the server, the application and the backup process. 4
IBM Tivoli Storage FlashCopy Manager 5
Solution Overview FlashCopy Manager Application Data Snapshot Backup Local Snapshot Versions For IBM Storage SVC XIV DS8000 DS 3/4/5* Storage Manager 6 With Optional TSM Backup Integration Online, near instant snapshot backups with minimal performance impact High performance, near instant restore capability Integrated with IBM Storage Hardware Simplified deployment *VSS Integration 6
Key functionality Snapshot (FlashCopy) Backup Volume level Full Database or Storage Group backups Exploit Storage Copy Services features Block level Incremental FlashCopy Space Efficient FlashCopy Auto provisioning of targets Enables Frequent Snapshot backups for near CDP operation Reduce the amount of data at risk from 24-hours to a few minutes worth Policy Managed Maintain a number of backup versions Adaptive to changing requirements 77
Key Functionality - Restore Microsoft Exchange Snapshot Restore* of Exchange storage groups File copy restore of a storage group or database from a mounted snapshot image Restore into a Recovery Storage Group, alternate storage group, or relocated storage group Individual mailbox or mail item restore from a snapshot backup Microsoft SQL Snapshot Restore* of a full database backup File copy restore of a full database from a mounted snapshot image To an alternate database name To an alternate location IBM DB2 UDB Snapshot Restore of a Full database Snapshot restore of one or more database partitions in the case of a multipartition database Oracle Snapshot restore of a Full database SAP Snapshot Restore of a Full database * As supported by Volume Shadow Copy Services (VSS) provider 8
Hvornår har vi brug for backup? ALDIG Men vi har brug for restore. Destruktive brugere slettede filer menneskelige fejl fyrede medarbejdere. Server nedbrud (OS hardware) Historik (revision/bevisførelse) Serveren er væk (tyveri / brand) 9
10 Serverrum på første sal
Hvorfor tager vi backup Vi ved godt at vi skal SLA Lovgivning. Revisoren siger vi skal. Regnskab 5 år, FDA 30 år, skole karaktere.. Person følsomme data må IKKE gemmes. Bevisførelse. 11
Hvordan tager vi backup? Backup Politik Vi tager backup hver nat. Vi kan restore alt en uge tilbage. Vi gemmer en årsbackup Backup typer... Backup (hver nat) Spejle mine data (raid/mirrow) Snapshot Dumpe 12
Hvorfor kunne vi ikke restore Det er helt usansynligt at dette kunne ske Serveren var ikke lige kommet med i backuppen endnu. 20 % af serverne er ikke i backup eller konfigureret forkert Vi regnede med at backuppen virkede Revisoren har sagt ok Forkert configurering af backup (inconsistens) Dobbelt backup Backuppen destureret ved restore Vigtige data placeret uden for datapolitik Fx data installeret i c:\temp 13
Hurtig konklusion Hvis datane kommer tilbage er alle glade Jo længre tid det tager, jo mere sur bliver chefen Hvis datane IKKE kommer tilbage er det pludselig min skyld. Jo flere kopier af data, jo bedre. 14
Backup politik - Historik Database politik. (Oracle, SQL, MySql...) Guld Sølv Bronce DB 1825 dage 180 dage 14 dage Log 365 dage 30 dage 14 dage DB del 1825 dage 180 dage 14 dage Historiske data ligger altid på anden lokation Historiske data ligger normalt elektroniks offsite. 15
Backup politik Recovery time Timer <500 GB 500-1000 GB Lav > 24 TDP for SQL TDP for SQL TDP for SQL+ LAN free 4 < medium < 24 TDP for SQL TDP for SQL+ LAN free Høj < 4 TDP for SQL+ LAN free TDP for SQL + Snapshot TDP for SQL + Snapshot TDP for SQL + Snap + mirrow 16
17 Backup politik Recovery time