This is a major setback for us.Īlso, to be clear, the release notes did not mention any impact to physical servers with Veeam Agent for Windows the CBT driver installed. They did not lose restore points and did not require reboot after updating. I verified this by the simple fact servers which I did not have the CBT driver installed were unaffected. I have a case open with support, but it is most likely an unexpected result of update 3a on physical agents with no recovery of previous restore points. This was extremely painful when considering this impacted more than 50 servers with the loss of data protection and additional bandwidth costs to recreate fulls across the WAN. All servers having the CBT driver installed deleted existing restore points and created new backup chains after reboot. There is no longer any record of the restore points in the B&R console under Backups/Disk or in the repositories themselves. Secondly, and most destructive, all restore points for each server were deleted without a trace. First, they immediately quit processing backups pending an unexpected reboot. To change settings in Postman, select the settings icon in the header and then select Settings. Make changes to settings at any time based on your use case or to customize your Postman experience. Postman Enterprise Postman Enterprise is designed for organizations who need to deploy Postman at scale. Postman automatically chooses default values for some settings so you can get right to work. Even put a note (not recommended) and remove it from default setup for a protection group.Īfter applying update 3a, all of my VAW physical servers were negatively affected. Not your OS Download for Windows ( 圆4) or Linux ( 圆4, arm64) Postman on the web Access the Postman API Platform through your web browser. Hey I can't upgrade this automatically because it will break backups until a reboot is done. There needs to be some sort of logic to state. Now we are scrambling and doing an emergency change (which directors have to approve and are asking why) and will be rebooting production servers into the night tonight in order resolve. Now we are not getting any backups at all. The worst part is we have one physical file server that is the main file share for 4 hospitals and is backed up every 2 hours. This is a very very very bad situation to be in. The protection groups did the once daily scan last night and saw hey I have an upgrade and upgraded but it requires a reboot in order to go thru and will no longer take backups until that is done. Well that is fine if its not going to break my backups but it did. I started going thru it and apparently the default for the protection groups is to check box " install agent automatically" and to "upgrade the agent automatically". I come in this morning and half of my physical servers didn't backup last night and each of them state "Host Reboot required". I upgraded our main VBR server and proxies to the latest version yesterday morning. Either way they need to put wordage in the setup at the least when having the check mark for auto update client in a protection group. The backup agent upgrade process has a nasty issue and not sure if it is a bug or if it is as designed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |