150 likes | 400 Views
Disaster Recovery using Veritas NetBackup. Presented By Steve White CNF Transportation Inc. white.steve@cnf.com. What We’ll Cover Today. Introduction Types of D/R Concerns Preparation for catastrophic loss Protection of NetBackup Server Preparation for relocation
E N D
Disaster Recovery using Veritas NetBackup Presented By Steve White CNF Transportation Inc. white.steve@cnf.com
What We’ll Cover Today • Introduction • Types of D/R Concerns • Preparation for catastrophic loss • Protection of NetBackup Server • Preparation for relocation • Sample hot-site configuration • Examples from hot-site tests • Conclusion
Types of D/R /Concerns • Loss of data • Catastrophic system loss • Catastrophic loss of NetBackup server • Localized disaster requiring relocation
Catastrophic System Loss • O/S Disk is lost • May include loss of data disks • May involve complete replacement of hardware • Can not restore basic O/S files over the network • NetBackup master may loose image catalog
Localized Disaster/Relocation • Datacenter fire or flood • Local or regional disaster • Requires plan for both operation and recovery
Prepare for Catastrophic Loss • Sun-only solution can be external disk • Watch for new PCI servers with no SCSI • Have also seen Jumpstart as a choice • Maintain current configuration data • Disk and volume layout • prtvtoc, df -k, df • Standard vxprint • vxprint -vpshm • daily/weekly crontabs • Perhaps maintain hard-copy • Document the recovery process • PRACTICE
Protecting the NetBackup Master • Frequent backups of image and media databases • BPVault helps with off-site copy of database • Scripts posted to mailing list • Majordomo@eng.auburn.edu • subscribe veritas-users • Establish a maximum life for database tape • Consider local dump tapes for O/S • PRACTICE
Prepare for Relocation • Pre-plan your hotsite environment • More tape drives is better • Be careful about the network • Remote vs. onsite recovery options • How will you recover OS • What media is required at hotsite • What to do about license keys • How to keep hotsite info up-to-date • Don’t forget about coming back home • DOCUMENTATION
Sample Hotsite Configuration • Home site has Sun E450 master with STK 9710, 6(8) DLT7000 Drives. 4 CPUs, 728MB, Gbit Ethernet • Hotsite Config: • STK 9710 with 10 DLT7000 • E6000 with 6 CPUs and 1 GB • Fast Ethernet • Company provided switch for backup network
Hotsite Recovery Experiences • We have performed four hotsite tests using NetBackup • Largest server recovered is 350GB. • First two tests we performed at the hotsite. • Last two tests were remote from Portland • Remote network connectivity is a primary issue • The first remote test NBU database not there • Importing images…the second list shows only those images not imported • Watch out for BPVault and rsh
Hotsite Cont’d • First two tests we used stand-alone DLT drives. • Last two tests have used STK 9710 • Configuration of robot is essential • Remember what the drive index should be • Must know what device corresponds to each drive. • Current media and O/S patches important • ISDN is reasonable for X-windows • Be careful to document client/master/media server names.
More Test Results • Provide transportation for people performing tests • Plan on the worst…you’ll need it • Network configuration can be a challenge • Not being in full-duplex can triple restore times. • Some providers don’t allow access to machine room
Conclusions • Planning is critical to recovery • Ensure plans are documented • Ensure plans are current • PRACTICE frequently • Process is needed to update media and documentation off-site • D/R must accompany business resumption plans…if no one can talk to the server, what good is it?