Hi Marcel,

Basically I’m recommending my customers not to backup the OS disk of phsyical (!) Windows repos since this might cause conflicts and inconsistency.

From my past experience I ran into Windows update issues that leave the system faulty not very often and in case it happens it might be quicker to just re-install the OS on the separated OS disk from scratch since a Windows installation doesn’t take long and if you e.g. work with scripts you are ready to go very quickly (1-2 hours). The longest would be installation HW drivers from a huge ISO file (e.g. HPE SPP or Dell SUU) but compared to the frequency of that issue occuring I’d stay with that.

There is basically no data stored on the OS disk and in case you have to reinstall it you just need to run the Veeam wizard again or perform a rescan (in case you use the same credentials, hostname and IP of course).

Maybe not the answer you’d like to hear but I’m comparing the amount of time in finding a solution and the amount of time and frequency of a reinstall.

Hope that helps in any way.

Lukas

I have to agree with Lukas on this one as long as the repo drive is not compromised then reinstall of the OS is the faster solution then trying to restore, etc.

Interesting Marcel. I actually never really considered backing up Repos. For me, not really a necessity. I use Linux and so it’s pretty basic. I haven’t done so yet, but will create a bash script to get a newly built phys Host configured like I want it. Other than that...no real issues I need to address for this. But, interested in what others have to share.

Best.

Thank you very much for hints, but as you mentioned, there is no other backup way of disk.

I have already automated backup of linux root disk via cobbler, but has to be provided continuously  maintenance of scripts. Due certificate of transport service it cannot be provided backup via VAL.