wow thanks for your time, yes i already master dd, and i have to use it since im cloning two disk that are identical both disk with more that 5 partition / 6 os.
i have no choice I HAVE TO binary copy the disk, and their is a catch since i want to update all my partitions in a fly, since many of them had updates, i normally got track of all of the changes and ftp the small tarballs to the appropriate system, and what i meant by catch is disks are identical i have 16% free on both disk, i cant afford *in the design not monetarly* to dump a tarball that would weight more that a hundred time what i have left for ressources. i am using ip4/ftp/ssh/sftp as of openservices, my question is i need to create a device that could stream the binary flow straight to my disk tru the ip4/sftp/ssh net. more suggestion ? thanks neko --- On Thu, 10/16/08, Mr D R Hughes <[EMAIL PROTECTED]> wrote: > From: Mr D R Hughes <[EMAIL PROTECTED]> > Subject: Re: reliable, dd over simple ip network > To: [EMAIL PROTECTED] > Date: Thursday, October 16, 2008, 5:43 AM > Neko wrote: > > Good day to all of you, > > > > i have found a really dirty way of going around this, > > so im fishing for advices on finding a reliable way > > to dd over simple ip network with the generic bsd. > > > > could this be done in a straight pipe ? > > > > i have an ftp on the generic bsd, containing data, > this > > bsd system is on a multiple os drive. i have no choice > to > > dd, since multiple partition got updated out of hand, > no way > > to single track specific updated folders. *well > actually yes, its > > the dirty way stipulated above* > > > > since my partitions have 16% free on all systems, i > cant tarball the > > drive sent it to target machine and uncompress, > > If you can mount the destination (eg; via NFS or Samba) > then you can > still use tar (it should also be possible to pipe the > tarred stdin > through scp to an sshd enabled destination if you can't > mount it):- > > cd TargetDir && tar cvpf - . | ( cd DestinationDir > && tar xvpf - . ) ; > sync ; sync > > Other choices would include dump (re; $ man dump) and rsync > (re; OpenBSD > packages), but if for some reason you really must use dd > (eg; to clone > a disk/partition), I've not tried it but dd should work > using the > following or similar command over a network mounted > filesystem after > booting to single user with network support mode:- > > dd if=/dev/TargetDisk | ( cd /DestinationDir && dd > of=BackupFile.image ) > ; sync ; sync > > Note that this process is likely to take a very long time > unless you > give dd appropriate ibs and obs or bs value/s to speed it > up (see $ man > dd). > > The destination backup file will also be a raw data (ie; > image) file > which you'll have to mount as a vnode pseudo-device > (see $ man vnconfig) > if you only want to restore a few files and not the whole > disk or > partition at a later date. > > Generally dd isn't a good choice for backing up data > unless you want to > keep clones of hard disks or partitions for replication. > Also when > cloning disks or partitions it is usually more convenient > to remove the > source disk/s and fit it and the destination disk/s to a > spare machine > for cloning. > > Rhys > > > > > anyays, if you have suggestion on opensource pkgs, > services i could open, > > or any bright idea i would like to hear them, > > > > since my solution for now is screwdrivers :C > > > > thanks > > > > neko
