> Amanda, Bacula and Tivoli Storage Manager client assume you have a > working linux system to use for your restorations. I had the bad luck > of a real hardware error during updating my maintenace server making > the DASD un-iplable. DDR makes for a fast restore in that case. I now > have a spare bootable minidisk for disaster maintenance > purposes to add > belt to the suspenders.
Good idea. A repair system is a handy item. Another comment: note that all 3 methods listed above have the actual backup data and metadata in a separate Linux instance, which can easily be shut down and DDRed at will (as opposed to having to shut down production servers and deal with clustering, etc with the "external" to Linux solutions) to get a guaranteed-clean snapshot of the backup server instance without disruption of normal server operations. This makes DDR for that backup server a much more attractive option -- you only have to do one machine that way, and it's a multi-stage approach -- restore VM, restore backup server, restore guests. The Bacula project actually provides scripts for building a minimal IPLable recovery server as part of the project (basically it builds a absolutely minimal Linux system from RPMs for emergencies). I haven't gotten a chance to test them on 390 yet, but they appear to work well on Intel. It might be worth looking at them as a starting point for a method to build this kind of recovery system for other purposes as well. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
