UNSOLVED
How to deal with MS Windows Patching
Hi Experts,
I'd like to reach out for some real life experience with the use of the following parameters:
- Client retries
- Client retry delay
We have around 800 Windows-Clients which are all being patched every month. We are unable to avoid conflicts between backups and patch initiated reboots. We are seeking optimal settings for the above Parameters in order to restart backups within a certain amount of time.
Are there any known issues related with the use of these parameters?
Many thanks for sharing your experience!
Regards
Christian
Correct - the worst thing that can happen are failed backups which you can easily restart or you simply wait until the group is started the next day.
Be careful if you have clients which will only be backed up rarely (only a full once a week/a month) - you might miss that full. In this case you can override the schedule manually with a command like
savegrp -l full -c -c .... -G
ble1
6 Operator
•
14354 Posts
•
56186 Points
358
0
Posted March 3rd, 2016 05:00
I rarely hit this as time when patching is done and backups do not overlap that much. Plus some critical servers are always excluded from patching as too many things can go wrong. When failing, due to patch, we just restart failed group next morning and all is fine. We use restart window of 18 hours.