| Backup procedure with mkcdrec (through NFS) |
|
|
|
| Manuales |
| Escrito por Gusvenom |
| Jueves, 03 de Abril de 2008 18:37 |
1.1 mkcdrec installation
1. Connect through SSH on the Linux machine to upgrade 2. Login with root privilege 3. En SSH copy mkCDrec_v0.8.2.tar.gz file to its own home directory (ex : /home/ie84948 with my account) 4. #cd /opt 5. #tar zxvf /home/mkCDrec_0.8.2.tar.gz (create a mkcdrec directory into /opt and untar mkcdrec files) 6. #mkdir /opt/mkcdrec/ISOFS_DIR 7. #mkdir /opt/mkcdrec/CDREC_ISO_DIR 8. Type the following command to verify packages requirements : #make test 9. If all packages are there, you must have something like this (all tests passed) : make test output of mkCDrec v0.8.2 Test 1: Are we root? Passed Test 2: missing executables needed by mkCDrec Passed Test 3: Filesystem for Initial ramdisk allowed? Passed Test 4: loopback device works? Passed Test 5: ram device available Passed Test 6: romfs supported by the kernel? N/A Test 7: cramfs supported by the kernel? N/A Test 8: strip (from binutils) available? Passed Test 9: BOOT_FLOPPY_DENSITY=ED ok? Passed Test 10: cdrecord -scanbus N/A Test 11: Header files present? Passed Test 12: DEVFS supported by kernel? N/A Test 13: filesystem tools present? ext2: Passed ext3: Passed Test 14: initrd must be compiled in kernel! Passed Test 15: Amount of memory available 513 Mb Test 16: scripts/Config.sh a link? Passed Test 17: serial console N/A Test 18: supported architecture? Passed Test 19: is RAMDISK_SIZE=64 big enough? Passed make[1]: Leaving directory `/opt/mkcdrec' 10. Otherwise, if packages are required, we could read something like this : gcc Not found mkisofs Not found cdrecord Not found In this case, install the missing packages in this sequence to respect dependencies: #rpm -ivh cdrecord-xxx.rpm #rpm -ivh mkisofs-xxx.rpm #rpm -ivh cpp-xxx.rpm #rpm -ivh glibc-kernheaders-xxx.rpm #rpm -ivh glibc-headers-xxx.rpm #rpm -ivh glibc-devel-xxx.rpm #rpm -ivh gcc-xxx.rpm 11. If all tests are passed, configure /opt/mkcdrec/Config.sh file by modifying the following lines : ISOFS_DIR=/opt/mkcdrec/ISOFS_DIR CDREC_ISO_DIR=/opt/mkcdrec/CDREC_ISO_DIR EXCLUDE_LIST="/opt/mkcdrec/ISOFS_DIR/* /opt/mkcdrec/CDREC_ISO_DIR/* /proc/* /mnt/*" 12. Verify that permission mask on /opt/mkcdrec/Config.sh are well 755
1.2 Backup the system
To launch the backup (creation of disaster recovery ISO files) ,type : #cd /opt/mkcdrec #make CD-ROM
Remarks : · MkCDrec supports ext2, ext3, minix, xfs , jfs, reiserfs file systems, LVM, hardware and software RAID (multiple devices) · The backup procedure via NFS session may last a long time (several hours according the total size to backup and the bandwith of network). So we recommend to start the backup procedure long time before the upgrade procedure · Let’s assume, there is enough free space on the NFS target drive (in our example : /mnt/nfs/server-name directory) · Do a "tail -f /opt/mkcdrec/tmp/xxxx_.log" to see backup progress
1.3 Verification
When mkCDrec has finished making the disaster recovey CD-ROM, it implants a checksum into the ISO9660 image. To check the integrity of the ISO9660 image or CD-ROM use the following command (build in mediacheck/ directory): # checkisomd5 CDrec.iso Read 0 MB 8852a5d88200444987f429bc527a8010 8852a5d88200444987f429bc527a8010 Md5sums match
1.4 Restore procedure
1. Create the recovery CD-ROM by burning the ISO files (see next section for instructions) 2. Boot from the CD #1 (so, eventually change your boot sequence in Bios to boot from CD-ROM first) 3. Start the recovery: 4. when the restoration is finished, reboot your system on disk
1.5 Instruction to burn a CD from Linux
The ISO files created by mkCDRec can be burned on any CD recorder using any software, but since our repository server is running on Linux and there is a CD burner right there, the best thing is to use it to burn recovery CDs, here's the instruction. 1. Find out the device address of the CD recorder: 2. Then, run this command to burn a CD: |
| Actualizado ( Martes, 08 de Abril de 2008 18:48 ) |













