Direkt zum Inhalt

vmProtect VirtApp fails completely after OS Patches

Thread needs solution

Periodically, I need to run patches on my various servers to update the OS, which often requires a reboot of various servers. I tend to run updates in batch -- all at the same time, so various machines are patching and rebooting at the same time. Every time I do this process, vmProtect simply refuses to do backups from that point forward. Every backup fails with an error that it could not contact the host.

The vmProtect console is working just fine. I can see my vCenter server in my list of hosts, but it sees no VM's on it. Any existing tasks show a "No source" error. I can disconnect from the vCenter server and reconnect with no problem. I can "test connection" with no problem. Everything seems to work in the UI, except for backups.

Now, I usually get frustrated and attempt to reboot the vmProtect from its own console. Every time, the console displays the "reboot" dialog box, but as soon as I click "Yes", it stops responding, and the UI also fails. The ONLY solution is a hard power-off of the vmProtect virtual appliance. After this reboot, things seem to start working again, but I've lost several backups in the meantime.

My current version is v8.0.8135. I noticed that build 8184 is current, but should this issue be fixed in the newer build? One other thing that complicates matters -- I have a special "bright colors" version so that I can see the red/green colors. If I patch to the base 8184 build, will I get the old color scheme again?

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi Bill,

From your description it seems like there are some vSphere infrastructural changes which make vmProtect unable to recognize these changes and therefore it looses connection to the vSphere (vCenter). We haven't seen such behavior before and in order to check it, can you please let us know how this issue can be reproduced? I.e. which servers you are applying patches to (are these particular ESX(i) hosts or there are some patches applied to the vCenter itself)?

There are also chances that 8184 build would automatically fix the issue since there were several fixes made in the code to improve work with the vSphere infrastructure (vSphere instances enumeration has been changed slightly), so it does make sense to install 8184 build and see whether the problem still persists. If it does then we'll need to reproduce the issue by getting additional details (mentioned below).

What concerns your question about the custom build with "bright colors" - I've submitted a request to create this build (I've found a case where the same task has been done for you) basing on 8184 one and will send you a link via PM once it is ready (should take around 1-2 weeks to get done). Though for now it definitely makes sense to ensure that 8184 (without "bright colors") fixes the issue first.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi Bill, I'm just curios here if the 8184 build did the trick for you?