# scdbackup-0.9.2-x86-rip http://scdbackup.webframe.org scdbackup@gmx.net Thomas Schmitt http://scdbackup.sourceforge.net scdbackup for RIP http://scdbackup.webframe.org/scdbackup-0.9.2-x86-rip.tgz http://scdbackup.sourceforge.net/scdbackup-0.9.2-x86-rip.tgz contains a fully functional installation of http://scdbackup.webframe.org on the rescue system RIP http://www.tux.org/pub/people/kent-robotti/looplinux/rip/ and possibly on other x86-Linux systems. Intended Purpose scdbackup does backups on CD or DVD media in formats ISO-9660 or afio or star. If you are already a user of scdbackup and want to restore your backups, then the first example section in paragraph "Usage" will serve you as reminder about how to restore your backups without the need for installing scdbackup. You will need this tarball for unpacking media which made use of rather exotic scdbackup features like : - redundant multi-copy backups which now turn out to be damaged and need repair - encrypted backups It is also wise to checkread more conventionally formatted backup media by scdbackup_verify before restoring them to disk by RIP's builtin capabilities. You may also use this tarball to produce backups of your sleeping system disk partitions, of shutted database files, or of just overly agile parts of your data filesystem tree. If you did not use scdbackup before, then you might use it now for copying large undamaged data partitions from hard disk to DVD or CD media. If you choose the write commands for ISO-9660 format then these media will be readable on any Linux|Unix|Mac|Windows with an appropriate drive. See paragraph "Usage" below, after the first group of restore examples. For a complete description of scdbackup's features see http://scdbackup.webframe.org/README http://scdbackup.sourceforge.net/README but ignore the installation procedure since it is already applied to the pre-installied tarball described here. The installation also includes sencrypt-0.2 for dealing with encrypted backups. Preparation (just in case no internet access is possible via the RIP system) (best to be done before a disaster occurs) Obtain scdbackup-0.9.2-x86-rip.tgz and put it on suitable media. Possibly within an ISO-9660 filesystem on CD, like : scdbackup scdbackup-0.9.2-x86-rip.tgz or just as a raw byte stream on floppy, like : cat scdbackup-0.9.2-x86-rip.tgz >/dev/fd0 Other filesystem formats and media are possible, too. The only condition is that your hardware and RIP's kernel must be able to read the media and the eventual filesystem format surrounding the tarball. You should try out the rescue system procedure anyway, _before_ a disaster occurs. I burned my RIP bootable CD by this command : dd bs=2048 if=/somewhere/RIP-14.4.grub.iso.bin | scdbackup -pipe_to_media Installation and Configuration - Boot RIP according to its own documentation. Normally you just put in the RIP CD, boot the machine and answer the prompts of GRUB and RIP. Login as user "root" (no password). For documentation on the current version, see the README link on http://www.tux.org/pub/people/kent-robotti/looplinux/rip/ - Unpack scdbackup-0.9.2-x86-rip.tgz. From prepared CD in drive /dev/hdd : mount /dev/hdd /mnt ( cd / ; tar xzf /mnt/scdbackup-0.9.2-x86-rip.tgz ) umount /mnt From prepared floppy in drive /dev/fd0 : ( cd / ; tar xzf /dev/fd0 ) Directly from the internet (if possible) : cd /root wget http://scdbackup.webframe.org/scdbackup-0.9.2-x86-rip.tgz ( cd / ; tar xzf /root/scdbackup-0.9.2-x86-rip.tgz ) rm scdbackup-0.9.2-x86-rip.tgz If you do not want to burn new media but just want to unpack existing backups then no further configuration effort is needed. You should have a look at paragraph "Usage" now. Burning is configured to use burn program cdrskin for CD. This should work well with RIP 2.5 or newer. With older versions of RIP it is better to use cdrecord for CD by switching the default settings: ( cd $(scdbackup -where inst) ; ./SET_DEFAULT_HELPER -cd cdrecord ) - If you want to burn CDs : find out the address of the burner. With program cdrskin you may list the device addresses of your CD drives by: cdrskin --devices With cdrecord or wodim you may list another style of addresses: cdrecord -scanbus cdrecord dev=ATA -scanbus All those address styles are usable in cdrecord, wodim and cdrskin. Set scdbackup's configuration variable to an approriate value like export SCDBACKUP_SCSI_ADR="/dev/hdd" or export SCDBACKUP_SCSI_ADR="/dev/sr1" or export SCDBACKUP_SCSI_ADR="0,2,0" or export SCDBACKUP_SCSI_ADR="ATA:1,0,0" Alternatively you may run scdbackup's configuration script cd /opt/scdbackup-0.9.2/inst ./CONFIGURE_CD which shows you the -scanbus output and asks for the usual configuration parameteres. Answers to questions other than "SCSI-Address of CD recorder ?" should be empty lines, unless you got reason to change these settings. The script does not propose adresses like "/dev/hdd" but it accepts them. - If you want to burn DVDs : find out the device address of the burner. Program cdrskin is able to list device addresses of available CD/DVD drives: cdrskin --devices Elsewise, if it is not obvious by RIP's boot messages or your knowledge about your computer, then close the drive's tray and try commands like eject /dev/hdd eject /dev/sr0 If the tray comes out, then you guessed the right address. Set variable SDVDBACKUP_DEV_ADR accordingly. Like export SDVDBACKUP_DEV_ADR="/dev/hdd" or export SDVDBACKUP_DEV_ADR="/dev/sr0" Set variable SDVDBACKUP_DEV_ADR accordingly or run the configuration script for DVD where you will have to enter the device address : cd /opt/scdbackup-0.9.2/inst ./CONFIGURE_DVD - Other possibly interesting configuration parameters would be SCDBACKUP_SPEED to be set to a value for cdrecord speed= (default "12") SDVDBACKUP_SPEED to be set to 1 in case of poor DVD media (default "any") SCDBACKUP_TMP_DIR to be set to the address of a hard disk directory if the RAM disk does not suffice for temporary files (default "/var/opt/scdbackup-0.9.2") SCDBACKUP_BUFFER to be set to a buffer file address on hard disk. Only needed if an old CD burner is not burnproof enough. SCDBACKUP_Z_CAP estimated capacity of a compressed CD (default "1200m") SDVDBACKUP_Z_CAP same for DVD (default "8000m") SDVDBACKUP_SCSI_ADR DVD drive address to be used if cdrskin , wodim or cdrecord are configured for use with DVD. See /opt/scdbackup-0.9.2/doc/README appendix "CONFIGURATION" for details. The newer releases of program xorriso provide higher backup fidelity and better fault tolerance than mkisofs. They also avoid slow checkreading of BD media and thus write BD 2 or 3 times faster than growisofs normally does. To select xorriso as ISO 9660 formatter: export SCDBACKUP_MKISOFS="xorriso -return_with MISHAP 32 -abort_on FATAL -as mkisofs -graft-points --for_backup" export SDVDBACKUP_MKISOFS="xorriso -return_with MISHAP 32 -abort_on FATAL -as mkisofs -graft-points --for_backup" To select xorriso as DVD/BD writer: export SDVDBACKUP_CDRECORD="xorriso -as cdrecord -v" Usage This paragraph is mainly an extract of scdbackup's README. Refer to /opt/scdbackup-0.9.2/doc/README for a deeper introduction. Especially appendix "RECOVERY" might be of interest for you. The examples assume that you are familiar with mounting disks and unpacking archives. They illustrate mostly the possible peculiarities of scdbackup : - Restore the usual backup formats of scdbackup - Copy data from undamaged disk data partitions to media in ISO-9660 format - Verify media. Either newly burnt ones or old backups before restore. - Merge damaged high-redundancy backups to get an undamaged one. - Unpack a multi-volume star archive (created as advised below) - Unpack a sencrypt-protected backup. - Backups of problematic tree parts with RIP rather than in Single User Mode ------------------------------------------------------------------------------ Restore the usual backup formats of scdbackup ------------------------------------------------------------------------------ For that you do not need any feature of scdbackup. Just execute the appropriate copy command for the particular format. - This example uses the drive at /dev/hdd dev=/dev/hdd - Mount the target disk partition mount /dev/hda5 /mnt Create the target directory mkdir /mnt/my_restored_data_collection - For ISO-9660 filesystems mkdir /mnt_cdrom To be done with each volume mount "$dev" /mnt_cdrom cp -a /mnt_cdrom/* /mnt/my_restored_data_collection umount /mnt_cdrom - For compressed afio archives cd /mnt/my_restored_data_collection To be done with each volume afio -ivZ "$dev" - For compressed star archives cd /mnt/my_restored_data_collection To be done with each volume gunzip <"$dev" | star -x -v - If you restored files of the bootloader (usually in /mnt/boot) you will have to boot the restored system by help of of RIP's bootloader GRUB and then run the installation procedure of the system's own bootloader. For that: reboot, do not choose the start of RIP, but enter GRUB's command line mode by pressing key "c", give the appropriate GRUB commands like : root (hd0,0) kernel /boot/vmlinuz boot GRUB is described in /usr/doc/RIP/grub.txt When the restored system is up, the superuser may reinstall LILO by executing lilo - For incremental backups in ISO-9660 format. mkdir /mnt_cdrom Example derived from: /opt/scdbackup-0.9.2/doc/examples.html#restore_incr TARGET="/mnt/my_restored_data_collection" Level 0 : With each volume do : mount "$dev" /mnt_cdrom cp -a /mnt_cdrom/* "$TARGET" umount /mnt_cdrom find "$TARGET" -type d -exec chmod 0755 '{}' ';' Level 1 : First insert the last volume of the media set and do : level_number=1 mount "$dev" /mnt_cdrom export SCDBACKUP_RESTORE_PREP_LEVEL="$level_number" gunzip /dev/null Watch for the announced name of the block checksum list. Like Note: blocklist file written : /mnt/tmp/scdbackup_1_1_A50912.170124_130537472 where A50912.170124 is the backup timestamp and 130537472 is its size. - Set this name for further processing blocklist="$tmp"/scdbackup_1_1_A50912.170124_130537472 - With each copy of the backup volume perform : $(scdbackup -where bin)/cd_backup_planer \ -process_blocklist mend $blocklist 0 "$dev" "$tmp"/recovering_image eject "$dev" Watch for the final messages. Either "The data still need more recovery work." or "The data are supposed to be in perfect condition now." Hope for that latter message before you are out of copies to be tried. In case of instable errors it may pay off to repeat the procedure with the same media again. - If your image is finally in "perfect condition" then mount it mkdir /mnt_2 mount -t iso9660 -o ro,loop /mnt/tmp/recovering_image /mnt_2 or copy it to fresh media. Remove old backup media and insert new media before you execute : sdvbackup -pipe_to_media /bin rule. Note that this installation is for the superuser only. If there are other users who shall use scdbackup, then they should have their own installations under their own $HOME. For that, such a user may do this : cd $HOME tar xzf ...somewhere.../scdbackup-0.9.2-x86-rip.tgz mv etc/opt/scdbackup-0.9.2 opt/scdbackup-0.9.2/conf mv var/opt/scdbackup-0.9.2/tmp opt/scdbackup-0.9.2/tmp mv var/opt/scdbackup-0.9.2/logs opt/scdbackup-0.9.2/logs rm opt/scdbackup-0.9.2/scdbackup_conf_dir rm opt/scdbackup-0.9.2/conf/scdbackup_tmp_dir_value rm opt/scdbackup-0.9.2/conf/scdbackup_logs_dir_value echo $HOME/opt/scdbackup-0.9.2/scripts/growisofs_wrapper \ > opt/scdbackup-0.9.2/conf/sdvdbackup_cdrecord_value rm usr/bin/scdbackup* usr/bin/sdvdbackup* usr/bin/sencrypt rmdir usr/bin usr etc/opt etc var/opt/scdbackup-0.9.2 var/opt var cd opt/scdbackup-0.9.2/inst ./ADD_USER This makes use of the commands which were already installed in /usr/bin by the superuser's installation.