On Thursday 10 May 2007 10:08 am, Chad Osmond wrote: > Are they one the same network? > dd and nc should work for you. > Maybe add the drive via USB and then dd the entire drive.
There's absolutely no reason to use dd for something like this. Your biggest problems with doing any kind of live backup is data that hasn't been flushed to disk yet, and that's not necessarily a big problem. Hell, here's how to do it live (assuming / is your running asterisk system, and /mnt/backup is your backup drive or network mount or whatever): rsync -avx / /mnt/backup Now either stop asterisk, mysql, whatever you've got running that may be 'live' or signal the processes to flush to disk, and execute the above command again. If you're really cautious, you may want to drop to single user mode. Whatever's left running typically doesn't care if its data isn't "clean" when it starts back up. Now you've got what I'd consider a "mostly working" image. You may have to create the /tmp, /proc, /sys etc filesystem mount points and install a bootloader on the target drive, but this is trivial to do. Unmount the drive and test it out. DD is a waste of time, and generally speaking I find ghosting linux to be an equally useless exercise. One of the greatest things I love about Linux is that I can make a copy like this, even "mostly" live, and get it running elsewhere, or pick up the drive out of a failed system and put it into another, with next to no screwing around to get the backup running. -A.
