VERITAS NetBackup 6.0 Bare Metal Restore Technical Presentation

1. VERITAS NetBackup 6.0 Bare Metal Restore Technical Presentation Ray Schafer Bare Metal Restore Product Specialist ray_schafer@symantec.com

2. Agenda • Solution Overview • Business Challenges • Traditional System Recovery Challenges • VERITAS NetBackup Bare Metal Restore™ Technology Overview • Installation and Configuration Overview • Daily Operations • Recovery Scenarios • Key Concepts and Features • Questions

3. Acronyms Used In This Presentation • BMR – VERITAS NetBackup Bare Metal Restore™ • NBU – VERITAS NetBackup • BMR Client – BMR protected NBU client • SRT – Shared Resource Tree • DDR – Dissimilar Disk Restore • DSR – Dissimilar System Restore • Config – The BMR Client’s configuration stored in the BMR database

4. NetBackup Bare Metal Restore™ - Solution Overview • NetBackup is the first enterprise backup solution that has an integrated bare metal recovery option capable of making use of ordinary backup data to automatically restore a system. • The system being restored does not need an Operating System installed on the disk drives. • The BMR option will allow NetBackup to restore a system to the exact configuration that existed at any point in time for which a valid backup image exists – either full or incremental, including synthetic backups. • The BMR option allows the recovery of Windows Systems to completely different hardware.

5. The Business Challenges of System Recovery

6. Business Challenges • System recovery takes too long • Traditional methods for system recovery are complex and require highly skilled staff • Recovery of Windows systems to the same or different hardware is very difficult • Recovery procedures and tools vary from platform to platform • System configurations and changes are not often tracked • System recovery is complex and often unsuccessful

7. Business Challenges Return to Service • Recovery Timeline Outage Mins Hrs Days Wks Recovery Time Install/Configure Hardware Install or Recover OS Restore Data

8. Traditional Recovery Methods • Traditional approaches to business recovery: • Reinstall OS and restore data from backup • Recover system from imaging technology • Home grown or exotic solutions

9. Shortcomings of Traditional Approaches • Require additional training and process maintenance • Challenge to train support teams • Maintain the documentation of all processes and procedures required to recover each system type • Home Grown Solutions must be maintained as technology evolves • Generally not considered an enterprise solution • Manually intensive procedural process • Cannot be leveraged across all platforms • Not integrated with existing storage management solution – duplicate data backups • Lack of scalability • Places extra burden on human and machine resources • Questionable data integrity and consistency

10. What Does The BMR Option Bring To Enterprise System Recovery? • A common method for recovery of most major platforms • AIX, HP-UX, Linux, Solaris, Windows 2000, XP, 2003 • A method of recovery that results in consistent and functional systems • Data, OS, and applications are in sync • OS and application patches & configurations are recovered • A Recovery solution that: • Is easy to manage and administer • Uses the data already stored in NetBackup to recover the system from any incremental or full backup • Scales easily when additional systems are added • Provides an unusually high degree of automation for recovery

11. Additional BMR Benefits • Support for multiple technologies • VERITAS Storage Foundation support (Solaris, HP-UX, AIX, Windows) • AIX LVM, HP-UX LVM, Linux LVM, Windows Dynamic Disks • Windows mass-storage support (RAID, SCSI) • SAN support (Windows 2000, 2003), coexistence (UNIX) • Centralized administration • Using the NBU Administration GUI • An extensive command line interface also available • One Button Application Recovery (through BMR External Procedures Feature)

12. Step 9. 8. 7. 6. 5. 4. 3. 2. 1. Reboot Server Recovery Time Load tape(s) and restore Reboot Reload backup software Reboot Step 3. 2. 1. Reload OS Reboot Reboot Click “Prepare to Restore” Collect all media Repair hardware Repair hardware Traditional Recovery Bare Metal Restore BMR Recovery vs. Traditional Recovery

13. Recovery Time Using BMR Return to Service Outage • Recovery time markedly reduced • Recovery is fully automated – allowing simultaneous multiple restores t 1 t 2 Mins Hrs Days Recovery Time BMR Install/Configure Hardware Traditional Methods

14. VERITAS NetBackup Bare Metal Restore™ Technology Overview

15. BMR Primary Functions • Captures system configuration • Physical layout of disks, TCP/IP and NBU configuration • Windows disk and network device drivers • Changes captured with every scheduled backup • Provides restoration environment • Enables diskless boot • Supplies tools and utilities • Creates customized restoration procedure • Builds partitions on drives to be restored • Re-creates original layout of filesystems, volumes • Restores original OS from NetBackup

16. BMR Logical Components • BMR Master Server Option • Installed on the NBU Master Server • BMR database, administration, logging • Creates custom restore procedures • Allocates/de-allocates recovery resources • Holds User-provided External Procedures • BMR Boot Server • Installed on any NBU Server or Client • Houses the Shared Resource Trees (SRTs) that contain the OS utilities/images, NBU software, other software such as VERITAS Volume Manager • Provides the Client boot images • NBU Client • Collects configuration information when directed to do so by the NetBackup policy

17. BMR Shared Resource Tree (SRT) SRT 1 • SRT’s are created on the BMR Boot Server • An SRT Is: • Collection of OS files, NBU software, other programs, such as VERITAS Volume Manager • Created during BMR installation • Used to provide a temporary restoration environment until the OS is restored from NBU • An SRT Is Not: • Backup image copied from BMR clients • A single SRT can be used simultaneously by multiple BMR clients SRT 2

18. BMR Installation and Configuration • No new hardware required • The BMR Master component is installed on NetBackup Master server • The BMR Boot Server component can be installed on the NetBackup Master and/or on a NetBackup client • Small footprint • Minimal processing needed • Well defined storage requirement • Flexible Architecture • Multiple BMR Boot servers • Choice of installation options • Choice of recovery mechanism

19. Integration Points With NetBackup • The NBU Client includes the required BMR client software. There is nothing to install on the NBU client. • The BMR Client agent (BMRSavecfg) is run by the NBU Scheduler and is automatically kicked off at the start of a backup if the BMR policy attribute is selected. • The BMRSavecfg Job will show up as it’s own job in the Activity Monitor • The BMRSavecfg Job will complete before the backup streams start • A failure by BmrSavecfg will not stop the backup

20. Integration Points With NetBackup • The BMR Option is licensed by NBU License Keys • The BMR node of the Admin Console does not show up if BMR is not licensed • The BMR Policy attribute is disabled if BMR is not licensed • BMR uses NBU’s level of Internationalization / Localization • BMR uses VERITAS Unified Logging (VxUL) • Online help is available for the Admin Console, and the standalone Windows wizards.

21. Integration Points With NetBackup • The BMR Database is covered by the NBU Master Server Catalog Backups • All of BMR’s volatile Master Server data is stored in the BMR database; including restore scripts, and external procedures. • Boot Server data (SRTs and packages) are NOT covered by the Catalog Backup. • The BMR Master Server is designed to be cluster-able, and follows the same rules as the rest of the NBU Master Server. • Executables need to be in place • The Database (catalog) needs to be failed over.

22. NBU Master Server Enabling BMR Protection For NBU Clients 1. Install and/or initialize the BMR DB component on the NBU Master Server With BMR Option 2. Enable the BMR option in the NBU Policy 3. Perform an initial full backup NBU Client BMR Protected

23. BMR Boot Server NBU Master Server With BMR Option BMR Recovery Environment Configuration 1. Install BMR Boot Server(s) 2. Create Shared Resource Trees (SRTs) 3. Optionally Create BMR Media Boot CDs NBU Client BMR Protected

24. BMR Boot Server NBU Media Server NBU Client BMR Daily Operations No manual action needed for daily operations! 1. Scheduled backup begins NBU Master Server With BMR Option 2. NBU Client saves it’s configuration 3. NBU Client configuration stored on NBU Master Server 4. Normal backup is performed

25. 1. Prepare to Restore (optionally edit the client configuration for DSR) BMR Boot Server 2. Boot the BMR Client (Network or Media) NBU Client BMR System Recovery BMR Server digests client configuration BMR Server creates custom restore procedures BMR Server allocates SRT on Boot Server NBU Master with BMR Option NBU Media Server Client accesses SRT (Network or Media) Client retrieves custom restore procedures Temporary Win installation (Win only) Client configures disk Client restores data from NBU Client reboots into restored partition Final cleanup is performed upon first login: • BMR Server de-allocates SRT on Boot Server • Temporary Win installation is removed (Win only) • DSR Tasks are completed (Win only)

26. BMR 6.0 Supported Platforms • Clients: • AIX, HP-UX, Solaris (Sparc), Windows (2000, XP, 2003), Red Hat Linux, SUSE Linux • Servers: • AIX, HP-UX, Solaris, Windows (2000 and 2003), Red Hat Linux, SUSE Linux • VERITAS Storage Foundation • AIX, HP-UX, Solaris, Windows Refer to the support matrices at http://support.veritas.com for the latest information

27. Screen Shots of VERITAS NetBackup 6.0 Bare Metal Restore

28. BMR Management Node in the NBU Administration Console

29. Prepare to Restore Operation

30. Prepare to Restore Dialog

31. BMR Tasks – Queued Restore Task

32. Restore Task Properties Dialog

33. Advanced Features of VERITAS NetBackup 6.0 Bare Metal Restore

34. VERITAS NetBackup 6.0 Bare Metal Restore™Dissimilar Disk Restore (DDR) • BMR’s DDR feature allows a UNIX or Windows System to be recovered to a system with completely different disks. • This is used to recover to a system where the disks have changed. • It can be used to change partition types, sizes, and disk location. • Modeled after the VEA GUI. • It can also be invoked to change the disk layouts before the disk partitioning/formatting is done. • The interface is consistent across all platforms

35. Bare Metal Restore Clients Node - Volumes

36. BMR Configuration Editor - Change Volumes Screen – Disk View

37. BMR Configuration Editor - Change Volumes Screen – Table View

38. Windows Dissimilar System Restore • BMR allows Windows systems to be recovered to dissimilar hardware: • CPU speeds and number of CPU’s can differ • HAL (Hardware Abstraction Layer) can be incompatible • Mass Storage Drivers can differ • Network Interface cards can be different • IP Address changes can be made • NBU configuration can be changed

39. The BMR Client “config” – The key to Windows Dissimilar System Restore (DSR) • Windows DSR is made possible by a BMR concept known as the Client Configuration – commonly referred to as the “config”. • The BMR client config can be thought of as an abstraction of the system. It is stored as an entity on the NBU Master Server in the BMR database. • The client’s original configuration is called “current” and is locked for editing to ensure that the original system can always be recovered. • The “current” config can be copied and the copy can be extensively edited: • Disk and Network Drivers, IP addresses, Network Routes, NBU Client configuration, and disk volumes can be changed

40. BMR Configuration Editor • The BMR Configuration editor can be used to edit a configuration in the BMR database • The original system does not need to be available • Editing can be done after the system has suffered an outage • The destination hardware can be decided upon after an outage of the original system • The resulting edited configuration can be used in the “Prepare to Restore” operation to recover to dissimilar hardware • The following screens in the configuration editor are used to change the Disk and Network Drivers in the config

41. Configuration Editor - Summary Screen

42. Change Drivers Screen

43. Additional Configuration Editing • The Configuration Editor allows other changes to be made: • IP and Network changes • Interface IP addresses/netmasks can be added or removed • Additional IP aliases can be defined on a single interface • DNS Servers can be changed or added • Network routes can be changed, added, or removed. • NetBackup Client configuration • Additional Media Servers can be added • IP Addresses of Master and Media Servers can be changed • IP Address of Client can be changed

44. & QUESTIONS ANSWERS