|
Backups on CD
Chapter 2 Quick Reference |
Just extract the tarball. Copy the executables /usr/local/sbin and the folder etc/backuponcd to /etc . With the debian package you should have nothing to do.
On a debian system you need to have installed the following packages:
textutils
shellutils
fileutils
sed
awk
findutils
mount
cdrecord
mkisofs >> 1.8a
tar or
afio
gzip
|
As you see everything is done with standard tools.
-
With the settings BackupOnCd comes with, you need 400 Mbyte free disk space under
/tmp/ . If free space doesn't fit you need to edit /etc/backuponcd/global.rc , Section 4.2.
You have several options:
- Change the variable
TMP="..." to a directory where is enough disk space
-
Enlarge the variable
tracks= and decrease tracksize=
Note, that a so-called lead-out is needed for each track, the amount of space on the disk is decreased by the count of tracks. For details have a look at /usr/doc/cdrecord/README.multi , or visit the homepage of cdrecord . You can play with these settings, if one track doesn't fit on the CD it is
stored on the next CD.
-
If free space is very small, you can force BackupOnCd to do the burning not parallel to the backup. If you did that, only one
tracksize space is needed. Edit /sbin/backuponcd_toast.sh , delete the single ampersand at the end of the line:
( nice -n -10 mkisofs -R -J -L $vol $volid \
$multiinfo $toast_dir | cdrecord -v $dev \
$devdepend $blank fs=8m -multi - && rm \
$toast_dir/* ) 2>> $logfile &
|
- A better option: Get an old 850 Mbyte disk and mount it to
/tmp .
- Try out to change the variable
devdepend="speed=2 -eject" to devdepend="speed=x" , while speed is the speed of your cdwriter. Please email me if it works or not. A Philipps CDD 3600 does not read the trackinfo if the CD is not ejected after each track. I think this toaster does a reset if the CD is ejected. You cannot run into trouble by playing this setting, a failed backup is all what can happen.
-
Edit the line
archiver= , choose tar or afio. Note, that find is not used if you choosed tar as archiver. The main disadvantage is, that no filelist is generated. Tar often is used as followed:
find . -not -type d | grep -v -f excludelist | \
tee -a filelist | tar -cvz --file=archive.tar.gz \
--files-from=-
|
With the above line empty directorys and each directory found in excludelist (ususally mountpoints) would not be archived. In my opinion this wouldn't be a backup, so tar is used as below:
tar -cvz -X $excludelist --file=- .
|
It should be easy for you to edit /sbin/backupond if you don't like this quality.
- Edit
rawdevice= and mountpt=
See Usage, Section 1.1 for commandline options. Copy or move the file /usr/doc/backuponcd/samples/excludelist , Section 4.1 to a place where you want and edit it, so that it fits to your system or the system which you want to backup.
The remaining is fun. Everything is done automaticly, the backup will get compared, logliles and scripts are burned on the last CD. It should be easy to do a restore with a system started from a floppy.
Backups on CD
|
|