-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oren Beck wrote:
First bite being a method of scripting the backups and archiving them. That means defining WHAT gets grabbed from where when etc rules and namespace conventions to make admin less painful. Since many windows users are schiziod in their file naming we have to be mindful of that.
I'm partial to partimage for system backups, which I use (combined with the fairly minimal system rescue CD linux environment) to implement windows imaging from bare metal (via PXE boot & NFS), from a 'rescue partition' on the 'doze HDD, and from DVD. I don't think the image files created by partimage can be directly mounted, but making a read-only loop-back block driver doesn't seem like it should be that difficult (he says naively, not having looked at the image format).
Second Bite being creating the restore method/s. Ranging from a web menu to ?
What exactly do you want to do? I have scripts that run under Sysrescd that image a windows system from bare-metal across the network (including PXE boot) in fairly short order (less than 1 Min/GigB IIRC, total time depends on the file-system size), but you don't get to resize parititons or extract just the user data for some customized linux win2lin migration thingy. - -- Charles Steinkuehler charles@steinkuehler.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG7uK3LywbqEHdNFwRArRwAJwOCe5or1+sCxv5syU7uOfU91LadACgnnus HLw5/8pyFyFnH8iWLcGgC80= =nAON -----END PGP SIGNATURE-----