Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!purdue!mentor.cc.purdue.edu!nova.cc.purdue.edu!gerrit From: gerrit@nova.cc.purdue.edu (Gerrit) Newsgroups: comp.sys.next Subject: Re: dump onto OD Keywords: silly keywords, dump, optical disk Message-ID: <5729@mentor.cc.purdue.edu> Date: 8 Dec 89 07:26:25 GMT References: Sender: news@mentor.cc.purdue.edu Reply-To: gerrit@nova.cc.purdue.edu (Gerrit) Distribution: comp Organization: Purdue University Lines: 25 In article wombat@claris.com (Scott Lindsey) writes: >Has anyone had success with using dump to backup onto optical disk? If I I typically use something like: dump 0fsd - 100000 6250 | compress > /OpticalDisk/full_backup.Z and then: zcat /OpticalDisk/full_backup.Z | restore rf - (or "restore xf -", depending on mood and purpose) One of the problem is that my "tape length" and "density" parameters are not at all tuned, and probably can't be well tuned if I'm running the dump through compress. If you know the approximate length (maybe by trial and error) you could probably even back up a 660 meg drive onto multiple OD's. The advantage of what I'm doing above though is that it is easy to save multiple partial backups on a single OD and have them all quickly accessible. The disadvantage is that if you are unlucky, you'll run out of space on the disk and dump will tell you that the entire dump is aborted. Then you have to guess again about the length and density and try again. gerrit