We currently have about 8 computers for my business, and I'm hoping to create a handy consolidated backup, containing clones of all OS-containing partitions from all computers, onto one 2TB external hard drive. Would this work, or create issues? What would you advise?
In case of a HD failure, I want to be able to replace the broken HD, and easily redeploy the respective cloned partition(s) onto the repaired computer, and have everything operating as it was before.
I use BootIt NG as a boot manager on 5-6 of the computers, and have multiple-OS setups on those (generally WinXP and Win7, setup to not see each other at all, plus a shared data partition if I need to transfer files between them).
With BootIt NG, it creates an Extended MBR, and I can essentially set up as many primary partitions as I want on a given drive on that computer. I have also used the program to individually clone, resize, move, etc., the partitions within a single computer - and I have made clone backup partitions within the same HD of each OS partition, in case the working OS gets hopelessly messed up. But if the HD itself dies, that won't help me much.
Of course, when working within a single computer, BootIt NG makes sure the EMBR keeps track of all the partitions. But if I try throwing maybe 15 cloned partitions on a single external HD, as separate partitions, originating on different computers, I'm guessing that any computer I plugged the ext HD into would not read it correctly, or it wouldn't see all the partitions (nor >4, if they're all made primary).
Or, perhaps, would I have to dedicate one desktop computer for holding a 2TB internal drive for all these backups, and use the boot manager/EMBR on that desktop to keep track of them all -- and then to redeploy a backup if needed, put the new/replacement HD into a USB enclosure and copy the cloned backup(s) onto it? But then might the MBRs not match up between the source computer and the new computer, rendering the new HD not bootable once I install it?
Or, is it better to scrap the whole "partition" premise, and make "images" of each partition instead? But then could I recreate a fully working, multiple-OS, multi-partition HD that would work like before?
This is confusing! Sorry for the lengthy post, but thanks for your input!
In case of a HD failure, I want to be able to replace the broken HD, and easily redeploy the respective cloned partition(s) onto the repaired computer, and have everything operating as it was before.
I use BootIt NG as a boot manager on 5-6 of the computers, and have multiple-OS setups on those (generally WinXP and Win7, setup to not see each other at all, plus a shared data partition if I need to transfer files between them).
With BootIt NG, it creates an Extended MBR, and I can essentially set up as many primary partitions as I want on a given drive on that computer. I have also used the program to individually clone, resize, move, etc., the partitions within a single computer - and I have made clone backup partitions within the same HD of each OS partition, in case the working OS gets hopelessly messed up. But if the HD itself dies, that won't help me much.
Of course, when working within a single computer, BootIt NG makes sure the EMBR keeps track of all the partitions. But if I try throwing maybe 15 cloned partitions on a single external HD, as separate partitions, originating on different computers, I'm guessing that any computer I plugged the ext HD into would not read it correctly, or it wouldn't see all the partitions (nor >4, if they're all made primary).
Or, perhaps, would I have to dedicate one desktop computer for holding a 2TB internal drive for all these backups, and use the boot manager/EMBR on that desktop to keep track of them all -- and then to redeploy a backup if needed, put the new/replacement HD into a USB enclosure and copy the cloned backup(s) onto it? But then might the MBRs not match up between the source computer and the new computer, rendering the new HD not bootable once I install it?
Or, is it better to scrap the whole "partition" premise, and make "images" of each partition instead? But then could I recreate a fully working, multiple-OS, multi-partition HD that would work like before?
This is confusing! Sorry for the lengthy post, but thanks for your input!