On Tue, Jun 15, 2010 at 10:07 AM, Shiv Deepak <[email protected]> wrote: > dd if=/dev/hda3 of=/home/sam/backup_set_1.img bs=1M count=4430 > dd if=/dev/hda3 skip=4430 of=/home/sam/backup_set_2.img bs=1M count=4430 > dd if=/dev/hda3 skip=8860 of=/home/sam/backup_set_3.img bs=1M count=4430
It's critical that /dev/hda3 is unmounted before you run dd. Or at the very least it should be mounted read-only. Problem with a backup which is not file system aware is that you may end up using too much backup space/media. Eg. if a 100GB file system is only 5GB filled, your backup will take all 100GB. A file system aware backup will only consume 5GB of backup media. Further, restoring through dd means that the target partition must be exactly the same as the source partition. Eg. if you backup a 100GB partition using dd, you cannot restore into a 60GB partition or a 160GB partition. As others have suggested file system aware backup tools like dump/restore, CloneZilla, etc are better in these aspects. - Raja _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
