backing up Solaris x86 using Linux
By Katsumii-Oracle on Mar 26, 2008
- Image file splitting. Actually, I later learned that splitting doesn't work over ftp. So, this really is NOT an advantage of G4L.
- More file system support. NTFS, ext3. Solaris can do FAT32.
- menu based
I think the 'G4L' name came from 'Ghost for Linux'. G4L uses dd for raw backup.
Here's what I did:
- Booted up Solaris x86 machine with G4L CD.
- Backed up /dev/hda to a bzip2 file called solx86.img on NTFS formatted external disk(/dev/sdb1). It created 42GB file from 120GB HDD. It took about 6 hours.
- Created new VMware Solaris x86 guest. Specified g4l.iso file for CD-ROM.
- Booted new VMware guest.
- Pulled off external HDD USB cable from Solx86 machine and connected it to VMware guest.
- Restore solx86.img. It was humming along to around 2% and suddenly finished. There was some error message but the message was overwritten by GUI. I couldn't jot the error message down.
- Checked on bzip2 file integrity like below. Failed.
$ bzip2 -tvv /mnt/local/solx86.img
- Detached USB disk from VMware guest and attached it back to Solaris physical PC. Checked bzip2 integrity like above. Succeeded.
- Retrying. Put the G4L CD back in old machine.
- Backed up /dev/hda to a lzop file called solx86_2.img on FAT32 formatted external disk(/dev/sdb1). It created 48GB file from 120GB HDD. It took about 3 hours.
- Boot VMware guest. Connected external HDD.
- To catch the error I started g4l in a different way.
$ g4l 2>/tmp/g4l.err
- Restore solx86_2.img. It again finished abruptly at 2%. /tmp/g4l.err file has error logged.
- Integrity check on lzop file. Failed.
$ lzop -t /mnt/local/solx86_2.img
- Connected external HDD to another machine and 'lzop' tested like above. Succeeded.