> Since you have a network with storage, perhaps setting up Samba and > using Windows built in backup facilities to store the image that is > created on the network? Maybe that would be a viable solution given my > understanding of your network. If you can provide additional details > about exactly how things are laid out specifically in relation to this > particular task then we might be able to offer better tips and > suggestions. > > Drew-
Sorry, I didn't know what the acronym meant. I tried googling, but the information I'm getting appears to be very old. I'm trying to build a backup system via network that allows me to do bare metal recovery. I.E., Windows 7 gets trashed and as soon as a new hard drive that works is put in, it is time to restore the last known good copy. Notice I'm not saying reinstall, but restore. In order to restore, potentially to a new hard drive of equal or greater size, there is a need to replace the boot sector and all the data. The backup system isn't just being set up for Windows, my personal system runs Fedora. I'd like to support backing up my brother's Sunflower G3 Mac as well running Mac OSX 10.3 I believe. Right now, I'm trying to get my level 0 raid to persist across reboots. I have a terabyte decimal of storage using two WD PATA 500G hard drives, which is about 900 gigs binary. Last time I rebooted, the hard drives in the raid volume came up as having no superblock. I probably will have to google for this, but off hand, does anyone know if a terabyte exceeds what ext3 can handle for a single filesystem? I'm running CentOS 5.5 on the server. Using dd to create an image is probably not the way to go even for Windows, but I'm not sure if I can trust Linux's NTFS support. I am open to better ways to do a backup, but right now I'm in the can I keep the data storage volume stable across reboots and can I support all of the different systems stage. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
