This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems after moving Sophos DB to other cluster node

Hi,

we had a little bit trouble because our database department had to do some maintenance last night on the SQL-Cluster running the Sophos database.

They switched the database to the other cluster node, so the database was a few minutes offline.

The Management Server lost connection to the database and didn't reconnect automatically.

The endpoints were up to date, but the Enterprise Console showed them "Not updated since..."

After a reboot of the primary Update-Manager and the Management Server I had to do a manual update and then all was fine again.

For future maintenance works of the SQL-Cluster I like to know what I have to do to avoid these trouble.

Here is a short overview of our environment:

- Database is on a dedicated SQL-Cluster

- Server A: management server + secondary Update-Manager

- Server B: primary Update-Manager

Is it enough to disable the management services on Server A before maintenance starts an enable them afterwards?

What about the endpoints that updated from Server B, this is the primary update-manager, during the database is offline?

Is this information cached somewhere and transferred to the database after reconnect?

Thanks in advance.

:48682


This thread was automatically locked due to age.
Parents Reply Children
No Data