1 / 30

Rapid Backup and Recovery Strategies for NT/Linux

Rapid Backup and Recovery Strategies for NT/Linux. Matthew F. Reagan Centocor, Inc. mreagan@fast.net. Purpose. The purpose of this presentation is to identify a problem with traditional backup and recovery strategies and propose alternative or supplemental solutions. Presentation Goals.

jenna-jennings
Download Presentation

Rapid Backup and Recovery Strategies for NT/Linux

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Rapid Backup andRecovery Strategiesfor NT/Linux Matthew F. Reagan Centocor, Inc. mreagan@fast.net

  2. Purpose • The purpose of this presentation is to identify a problem with traditional backup and recovery strategies and propose alternative or supplemental solutions

  3. Presentation Goals • Discuss the problems encountered • Identify alternative or supplemental solutions • Propose a supplemental solution • Present a snapshot of research into rapid backup and recovery solutions • Emphasis on non-production environments

  4. Presentation Non-Goals • Present the only solution • Present the best solution • Present the cheapest solution • Present the fastest solution • Ignore the subjective side of the issue • Replace backups

  5. Production Environments • Standard hardware configurations • OS installed using SOPs • Documented software installation • Usually static configurations • Centralized, regular backup

  6. Non-production Environments • Development • Validation • Evaluation • Sandbox

  7. Non-production Environments (cont) • Not always standard hardware • Baseline OS/software configuration • Myriad extensions to the baseline • Loose documentation requirements • Usually not backed up (regularly)

  8. Description of Problem • How do you recover from media failure • How do you recover from accidents • How do you recover from bad installs • … with YOUR deadlines?

  9. Checklist for System Recovery • Repair the hardware • Reinstall NT Server • Reinstall the Service Pack(s) as Needed • Reinstall the required drivers • Reinstall the appropriate applications • Recover the OS from backup tape

  10. Problems with Recovery • Requires installation and configuration knowledge of • NT Server • Service Packs • OS baseline • Application Software • Drivers (you know where they are, right?)

  11. Rapid Recovery Options • Implement robust backups • RAID • Drive “snapshots”

  12. Implement robust backups • Requires additional hardware (tape drives) • Requires additional software (backup) • Requires (more) operations staff • Train personnel in NT, service pack, driver and software installation and configuration

  13. Implement robust backups (cont) • Recovery requires extensive configuration and installation knowledge • Recovery is complex • Recovery is time consuming

  14. Implement local backups • Requires additional hardware (tape drives) on each server • Requires additional software (backup) • Train personnel in backup procedures • Needs tape storage/retention policies • (not much better than previous option)

  15. RAID • Requires additional hardware (drives) • Requires additional software (backup) • Train personnel in RAID installation, configuration and operation

  16. RAID (cont) • Recovery requires extensive configuration and installation knowledge • Recovery is complex • Recovery is time consuming • Implementation nightmare

  17. Drive “Snapshots” • Wouldn’t it be nice if we could just take a snapshot of the hard drive?

  18. Imagine, if you will,taking a snapshot... • Prior to installing a service pack • Prior to installing a new software version • Prior to modifying an existing configuration • Just after finishing an install

  19. Recovery would be… • Simply putting back the snapshot

  20. Functional Requirements • OS independent • Floppy based • Avoids open files • Avoids configuration differences • Simple to use • Cheap

  21. PowerQuest Drive Image • Provides a drive snapshot capability • Supports DOS, Windows 3.x, Windows 95, Windows NT, Linux • Reads IDE and SCSI hard drives • Writes to IDE and SCSI hard drives, ZIP, Jaz drives, network drives, etc. • Creates an optionally compressed image file (~40%)

  22. Possible Configurations • Local hard drive • Internal/External ZIP drive • Internal/External JAZ drive • Network drive

  23. Local Hard Drive • Destination drive must be mountable under boot floppy (native IDE, ASPI driver for SCSI) • Destination drive must have a FAT partition • Boot using supplied floppy • Point and click snapshot done!

  24. Internal/External ZIP Drive • Internal uses IDE or SCSI • External uses PP or SCSI • Destination cartridge must have a FAT partition • Boot using supplied floppy • Point and click snapshot done!

  25. Internal/External JAZ Drive • Internal uses SCSI • External uses PP (traveler) or SCSI • Destination cartridge must have a FAT partition • Boot using supplied floppy • Point and click snapshot done!

  26. Network Drive • Create a network boot floppy (see NT client administrator) • Must have write privs on share • Boot using network boot floppy • Point and click snapshot done! • (took 5 minutes for 2 gb partition with 50% of disk in use

  27. Recovery • Boot using supplied (or network) floppy • Gain access to the image • Run PQDI • Point and click snapshot recovered! • Network recovery took 5 minutes for a 2 gb partition with 50% of space in use

  28. Caveats • Only supports non-RAID configurations • Only supports Intel (or clone) CPUs • Have not tested larger than 6.4 gb HDs • There are other options (Symantec’s Ghost)

  29. Conclusions • Several untraditional options available • Each is a balance between cost, convenience, and efficacy • Drive Image is a strong contender • Additional research is necessary

  30. Questions?

More Related