Re: Imaging computers for bare metal backups. I don't want to miss a bet regarding best practices.
So, I'm asking for comments on my beliefs and practices.
I'm trying to be as pedantic as possible in order to generate comments. So some assertions are really, to me, DUH! (You don't have to say "well, SURE!" :-)
I'm currently targeting VEEAM Windows Free Agent as the tool.
There are no virtual machines.
There are no "families" of identical target hardware.
1) If it's going to be bare metal then that implies the OS drive could be empty and one has to provide a boot mechanism.
2) One has to have a boot mechanism, an image, and the image source has to be reachable by the booted recovery environment.
3) Remote access is out of the question.
4) If the computer is headless then this can complicate matters to provide HID access for the recovery environment.
5) The VEEAM backup process can keep up with changes. So, if the objective is to back out from an OS upgrade, some selection in the recovery will be necessary. (Assumes that using a Restore Point from within Windows isn't feasible).
6) Using VEEAM, it's necessary to have a unique boot drive. How to avoid the uniqueness?
7) The unique boot drives have to be available or easily burned from backups. (Which?)
8) If the unique boot drive isn't tested (including that the image file reachable) then you don't know what you have.
Some thoughts and questions:
The more computers handled by imaging, the more images, the more boot drive images and the more administration.
It would be nice to not have unique boot drives. Is there a reasonable way to do this?
How do you handle the process?