After completing several successful backups over a couple of weeks, two servers stopped backing up a day apart from each other. When trying to startup the Azure Recovery application on each server to view job status and any errors, the application fails to initialize and times out during step 1. If I try to restart the service, it hangs on the startup and times out, never fully starting. I even tried to re-register one of the servers, but it fails by not saying the vault credentials file isn't valid, even though it had just been downloaded and I had allowed re-registration for that server in Azure. I rebooted both servers as well, no change.
One server is running 2012R2 and the other is 2008R2 sp2, and as I mentioned having been completing successfully daily backups for weeks then just stopped. Other servers on this same subnet have still been completing their backups successfully, and there has been no firewall changes or anything else changed in the environment. The servers still have internet access.
On the 2008R2 server I even installed an upgrade of the agent since the running version was a few weeks older than the currently available one, the upgrade was successful, but the app itself still won't initialize and the service can't be started still, so nothing was helped.
I feel like I may need to completely uninstall the app and reinstall , but I'd prefer to not lose my existing recovery points. Also, we're trying to make Azure Backup our main backup utility but it's hard to trust if it just stops working randomly and can't be restarted even though nothing has changed on a server.
Any ideas of what else I can check or try?