Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

BrainShare 2010 SLC - ELS306 Linux Disaster Recovery Made Easy


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

BrainShare 2010 SLC - ELS306 Linux Disaster Recovery Made Easy

  1. 1. Linux Disaster RecoveryMade EasySchlomo Schapiro Jeff LindholmSystems Architect / Open Source Evangelist Technology Sales Specialist – LinuxImmobilien Scout GmbH Novell, License:
  2. 2. Agenda Linux and disaster recovery Solutions: relax and recover Secure disaster recovery for enterprise environments SLES 11 SP1 HA – ReaR availability and support Live demo and use cases Questions and answers2 © Novell, Inc. All rights reserved.
  3. 3. Backup != Restore/Recovery3 © Novell, Inc. All rights reserved.
  4. 4. Linux and Disaster Recovery
  5. 5. Disaster Recovery Strategies Copy Files and Store Disk Disk Imaging Layout and Boot Info + Online -> no problem + Offline -> no open + Backup independent of disk file issues layout and sizes + Simple to restore – More effort required to – Online -> very restore (can be scripted) problematic – Maybe consistency – No “perfect” open problems, but should be source tool for solved by backup solution Linux available5 © Novell, Inc. All rights reserved.
  6. 6. Advantages of a Linux System All information is stored in files; all files always readable Operation system and applications can be “slim” - 600MB enough for complete standard server Open system – open methods and procedures All steps of an installation can be scripts: partitioning, file systems, boot loader etc.6 © Novell, Inc. All rights reserved.
  7. 7. Disaster Recovery – Media • Most important: external storage! • Bootable media: CD/DVD, USB key, LAN, tape ... • Media usually combination boot and backup media: – Bootable CD/DVD, USB key with backup data on it – LAN boot (PXE) with backup data via CIFS, NFS ... – Bootable tapes - HP OBDR (CD emulation) • Separation between boot media and backup data – Boot the system from a (small) USB key, CD/DVD or LAN – Recover the system with backup software, tar, rsync ...7 © Novell, Inc. All rights reserved.
  8. 8. Disaster Recovery – How It Works • Store the disk layout – Partitioning, LVM and RAID configuration – File systems, file system labels ... – Boot loader (GRUB, LILO, ELILO) • Store the files (tgz, rsync, through backup software ...) • Create bootable rescue media with system configuration (and backup data) • Can be done online – No business interruption – 100% compatible with original systems hard- and software8 © Novell, Inc. All rights reserved.
  9. 9. Disaster Recovery – Rescue Media • Create “rescue linux” from running system • Optimally compatible “tool box” • Clone the system environment – Linux kernel and modules – Device driver configuration – Network configuration – Basic system software and tools • Operate entirely in RAM (initrd)9 © Novell, Inc. All rights reserved.
  10. 10. Disaster Recovery – In Action • Boot system from rescue media • Restore disk layout – Create partitions, RAID configuration and LVM – Create file systems (mkfs, mkswap) – Configure file systems (labels, mount points) • Restore the backup data • Restore the boot loader • Reboot • Done!10 © Novell, Inc. All rights reserved.
  11. 11. Solutions: Relax and Recover
  12. 12. Proprietary Solutions • Usually part of backup software • Extra licenses and can be costly (up to 1000€ / server) • Some are free, but are the any good? • Level of integration into backup software varies • Not all backup software actually supports disaster recovery • Cover only simple setups • Often static boot media, inflexible with regard to drivers • Certification on server hardware missing or lagging behind procurement cycles12 © Novell, Inc. All rights reserved.
  13. 13. Open Source Solutions • Several software projects on the internet: – Relax and recover – mkCDrec – Mondo Rescue – CRU – BACULA – Your-Favorite-Selfmade-Script – <something you know but I never heard about> • In 2006, all of them where lacking something...13 © Novell, Inc. All rights reserved.
  14. 14. Relax and Recover – ReaR • GPL Software – Developers in Germany and Belgium • 100% Bash script – no GUI and no dependencies • Utilize kernel, modules, binaries of host (kernel ≥ 2.6) • Support any combination of SW/HW RAID, LVM • Internal backup on CIFS, NFS ... • Boot media on CD/DVD, USB key and LAN (PXE) • Successor of mkCDrec14 © Novell, Inc. All rights reserved.
  15. 15. ReaR – Features • Focus on disaster recovery and not backup • Tight integration with common backup software – delegate file backup to backup infrastructure • Simple full backup integrated • Complements backup software: – Backup software: Data storage and retrieval – ReaR: Recover system layout and make it work again – ReaR utilizes the backup software to restore the backup data • Use the best tool for the job15 © Novell, Inc. All rights reserved.
  16. 16. ReaR – Backup Software • Supported solutions include: – CommVault Galaxy – IBM Tivoli Storage Manager – Veritas NetBackup – HP Data Protector – Rsync and other “external” methods – tar.gz archive on NAS share – CIFS, NFS, NCP ... • Very transparent integration • Quick implementation: 2-3 PT programming • Can be easily extended to support other vendors16 © Novell, Inc. All rights reserved.
  17. 17. ReaR – Network Integration • Disaster recovery as part of network infrastructure – Backup software – file-level backup storage – ReaR – system environment – Boot rescue media via PXE – no physical media required – Very scalable – automated installation of entire disaster recovery data center ReaR Boot Files Software Backup PXE Boot Backup Network Storage infrastructure17 © Novell, Inc. All rights reserved.
  18. 18. ReaR – Status • Stable software – i386 and x86_64 well tested – ia64 and ppc experimental • Regular releases (RPM, DEB, TGZ) • Major Linux distributions ship ReaR: – SUSE Linux Enterprise High Availability Extension 11 SP1 ® – openSUSE 11.2 and Fedora 11 ® • Community and commercial support available • Regular patch submissions from ReaR users18 © Novell, Inc. All rights reserved.
  19. 19. ReaR - Development • Open Source development model: – Submit patches and feedback – “field testing” – Sponsoring • Modular design: – ReaR is a framework to plug together many small bash scripts – Maximize code reusability – Simple development model (vi works fine) – Little to no “interferences” between different areas of code • Documentation on project homepage – Hierarchical structure – References to source code19 © Novell, Inc. All rights reserved.
  20. 20. ReaR – Configuration • Shell-script style configuration file • Usually: Set backup software and boot media System definition: ARCH = Linux-x86_64 OS = GNU/Linux OS_VENDOR = SUSE_LINUX OS_VERSION = 11 OS_VENDOR_ARCH = SUSE_LINUX/x86_64 OS_VENDOR_VERSION = SUSE_LINUX/11 OS_VENDOR_VERSION_ARCH = SUSE_LINUX/11/x86_64 Configuration tree: Linux-x86_64.conf : OK GNU/Linux.conf : OK SUSE_LINUX.conf : missing/empty SUSE_LINUX/x86_64.conf : missing/empty SUSE_LINUX/11.conf : missing/empty SUSE_LINUX/11/x86_64.conf : missing/empty site.conf : OK local.conf : OK20 © Novell, Inc. All rights reserved.
  21. 21. ReaR – Operation rear [Options] <command> [command options ...] Relax & Recover Version / 2010-03-19 Build: b80d32a97e41a6ec8a5b19cd6399e444 Copyright (C) 2006-2009 Schlomo Schapiro Gratien Dhaese, IT3 Consultants Relax & Recover comes with ABSOLUTELY NO WARRANTY; for details see the GNU General Public License at Available Options: -V version information -d debug mode -D debugscript mode -S Step-by-step mode -s Simulation mode (shows the scripts included) -q Quiet mode -r a.b.c-xx-yy kernel version to use (current: © Novell, Inc. All rights reserved.
  22. 22. ReaR – Operation (continued) List of commands: dump Dump configuration and system information help print out usage mkbackup Create rescue media and backup system. mkbackuponly Backup system without creating a (new) rescue media. mkdeb Create DEB packages with this rear version mkdist Create distribution tar archive with this rear version mkrescue Create rescue media only mkrpm Create RPM packages with this rear version mktar Create tar archive with this rear installation mkvendorrpm Create vendor RPM with this rear version recover Recover the system validate Submit validation information22 © Novell, Inc. All rights reserved.
  23. 23. ReaR – Example Configuration # cat /etc/rear/local.conf OUTPUT=ISO #BACKUP=TSM|NBU|DP|GALAXY|EXTERNAL|... BACKUP=NETFS NETFS_URL=nfs://server.domain/backup-path MODULES_LOAD=( vmxnet )23 © Novell, Inc. All rights reserved.
  24. 24. ReaR – Example Execution # rear mkbackup Relax & Recover Version / 2010-03-19 The preparation phase OK Physical devices that will be recovered: /dev/sda /dev/sdb Creating root FS layout OK Copy files and directories OK Copy program files & libraries OK Copy kernel modules OK Create initramfs OK Creating archive nfs://server.domain/backup-path/rear/backup.tar.gz Transferred 297 MB in 254 seconds [1197 KB/sec] Making ISO image OK Wrote ISO Image /tmp/ReaR.iso (19M) Copying resulting files to network location OK The cleanup phase OK Finished in 258 seconds.24 © Novell, Inc. All rights reserved.
  25. 25. ReaR – Disk Layout # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/system-root 2,5G 927M 1,4G 40% / devtmpfs 244M 128K 244M 1% /dev tmpfs 247M 0 247M 0% /dev/shm /dev/sda1 84M 19M 61M 24% /boot /dev/mapper/system-home 524M 17M 481M 4% /home /dev/md0 680M 55M 591M 9% /var25 © Novell, Inc. All rights reserved.
  26. 26. ReaR – Disk Layout # pvs PV VG Fmt Attr PSize PFree /dev/sda3 system lvm2 a- 3,21G 0 /dev/sdb2 system lvm2 a- 312,00M 0 # lvs LV VG Attr LSize Origin Snap% home system -wi-ao 532,00M root system -wi-ao 2,44G swap system -wi-ao 572,00M # cat /proc/mdstat Personalities : [linear] [raid1] md0 : active raid1 sda2[0] sdb1[1] 706816 blocks super 1.0 [2/2] [UU]26 © Novell, Inc. All rights reserved.
  27. 27. ReaR – Recovery Example# rear recoverRelax & Recover Version / 2010-03-19Backup archive size is 298MInitializing physical devices OKCreating Software RAID devices OKCreating the LVM2 devices OKCreating file systems OKRecreated this filesystem layout:Filesystem Size Used Avail Use% Mounted on/dev/mapper/system-root 2.5G 68M 2.3G 3% /mnt/local/dev/sda1 84M 5.6M 74M 7% /mnt/local/boot/dev/mapper/system-home 524M 17M 481M 4% /mnt/local/home/dev/md0 680M 17M 629M 3% /mnt/local/varRestoring from nfs://laptop/dev/shm/nfs/rear/backup.tar.gz OK 27 © Novell, Inc. All rights reserved.
  28. 28. ReaR – Recovery Example (continued) Restoring the bootloader (SuSE style) Creating swap files and partitions OK Finished recovering your system You can explore it under /mnt/local Thank you for using Relax & Recover Version Finished in 150 seconds.28 © Novell, Inc. All rights reserved.
  29. 29. ReaR – Vision • Do more than just disaster recovery – System cloning and provisioning – System migration (P2V, V2P, V2V, P2P) – Generic system tool-kit for offline tasks and rescue media • Centralized information and management: – rear-server – 1.0: Gather and aggregate information about ReaR > System protection status > Rescue media boot files – 2.0: Centrally manage configuration and control ReaR > Site-wide and system-local configuration store > Trigger and control disaster recovery tasks – 3.0: Integrate into 3rd party solutions29 © Novell, Inc. All rights reserved.
  30. 30. Secure Disaster Recovery Enterprise Environments
  31. 31. Enterprise DR – Requirements Standardization Scalability Automation Integration in existing system environment Security Coverage over all systems in use Support and maintenance Education and certification Affordable licensing – site license31 © Novell, Inc. All rights reserved.
  32. 32. Enterprise DR – Relax and Recover • Standardization through global configuration: – /etc/rear/site.conf • Scalability and automation: – rear mkrescue can be run as a cron job – Automated processing of rescue boot media fairly simple – Rescue boot media also stored with backup software – LAN boot – extreme scalability and automated DR possible • Integration in existing system environment – Support internal and external backup solutions – E-mail reports32 © Novell, Inc. All rights reserved.
  33. 33. Enterprise DR – Relax and Recover • Security considerations – No “secret” data in rescue media – Secure export of rescue media through backup software and E-mail – Remote access to rescue system only with SSH keys • Coverage – i386 and x86_64 stable – Enterprise Linux (Novell , Red Hat, Ubuntu) stable ® – Community distributions also work, less tested • Maintenance and support, education – Please contact Novell and the authors • Site license: Included with GPL33 © Novell, Inc. All rights reserved.
  34. 34. Security Aspects – Disaster Recovery Backup server DR boot server DR client Transfer of Backup Data Transfer of Boot Riles • How secure is the • Insecure (anonymous): backup software? – NFS • Insecure: NFS2, NFS3 – CIFS • Secure (with – SSH (keys) authentication): – RCP – NFS4, CIFS • Manipulation proof: – SSH (rsync) – SMTP34 © Novell, Inc. All rights reserved.
  35. 35. Enterprise Linux Disaster Recovery • Linux – Simple Disaster Recovery • Integration: Disaster recovery – backup software • Automated creation of disaster recovery information • Network boot into rescue system • Disaster recovery becomes part of infrastructure • Scales well even for very large data centers • Disaster recovery becomes a valid option for clients, not only for servers35 © Novell, Inc. All rights reserved.
  36. 36. SUSE Linux Enterprise High Availability ® Extension 11 Service Pack 11 – ReaR Availability and Support
  37. 37. SUSE Linux Enterprise ® Modular Portfolio SUSE Linux Enterprise Common Code Level 3 Support Runs on x86, Base foundation x86_64, Itanium, Power, and s390x SUSE Linux SLES for SAP, Enterprise SLED JeOS SLE SDK SLE POS Expanded Server Support Server Desktop Custom Developer Bundles Support OS OS OS Tools SKUs High Availability Real Time Extension Mono Extension Optional extensions for high availability clustering, Pay only for deterministic computing, and running .NET applications what you need37 © Novell, Inc. All rights reserved.
  38. 38. SUSE Linux Enterprise High Availability Extension 11 ® Key Features • Flexible, policy driven • Continuous data clustering solution replication – OpenAIS messaging and – Distributed Replicated Block membership layer Device (DRBD8) – Pacemaker cluster resource manager • GUI and CLI tools – Graphical user interface • Cluster-aware file system – Unified command line interface and volume manager – Oracle Cluster File • IP load balancing System (OCFS2) – Clustered Logical Volume • Resource agents Manager (cLVM2) • Bare Metal Recovery (ReaR) • Virtualization aware38 © Novell, Inc. All rights reserved.
  39. 39. SUSE Linux Enterprise High Availability Extension 11 ® Differentiators • Affordable Costs less than other Linux clustering solutions, with tools and resource agents included at no extra charge • Virtualization-aware Supports hybrid virtual and physical clusters • Open Source No proprietary modules or user space applications means your Linux clustering solution is secure and easily kept up to date • Integrated Streamlined support and an optimized solution from a single vendor that delivers both the OS and clustering software39 © Novell, Inc. All rights reserved.
  40. 40. SUSE Linux Enterprise High Availability Extension 11 ® New Features/Enhancements SP1 ReaR – Relax and Recover • ReaR will be included with SUSE Linux Entreprise Server 11 SP1 HA Add-on • ReaR is considered to be an extensible framework, allowing for custom scripting and extension of the recovery toolset • ReaR RPM packages will be supported on x86 and x86_64 • SLE11 High Availability Add-on inherits service level agreement from the SLES Subscription – Priority (24x7) – Standard (12x5) • Customization is not covered by Novell Technical Support ® – Integration Partners are available (contact Novell Sales)40 © Novell, Inc. All rights reserved. •
  41. 41. SUSE Linux Enterprise High Availability Extension 11 ® More Information - SP1 For more information on what is new with SLE11 HA SP1: ELS307 Building High Availability Clusters with SUSE Linux Enterprise High Availability Extension ELS302 SUSE Linux Enterprise High Availability Extension 11: Support and Troubleshooting ATT307 Quickly Configure a High Availability Cluster with SUSE Linux Enterprise 11 High Availability Extension41 © Novell, Inc. All rights reserved.
  42. 42. Live Demo/Use Cases
  43. 43. Relax and Recover – Live Demo Demo (~10 min): • SUSE Linux ® Enterprise High Availability Extension 11 SP1 • ReaR creates backup and boot CD • “PEBKAC” at work • Boot system from CD • Recover system • Happy End43 © Novell, Inc. All rights reserved.
  44. 44. Questions and Answers
  45. 45. Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc.Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scopeof their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified,translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc.Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market aproduct. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon inmaking purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contentsof this document, and specifically disclaims any express or implied warranties of merchantability or fitness for anyparticular purpose. The development, release, and timing of features or functionality described for Novell productsremains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and tomake changes to its content, at any time, without obligation to notify any person or entity of such revisions orchanges. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, the United States and other countries. All third-party trademarks are the property of their respective owners.