I am in the process of setting up a new deployment of the endpoint 5.2 at a client and was wondering the best way to deploy the software so that 2 servers can be running but both using one database (or having the databases synced). I want to be able to recover quickly in the event of a server down issue.
From what I can see in the documentation you can have multiple servers but they each maintain their own database.
Alternatively it looks like I can setup a full backup to a spare server and just run the DB from there in the event of a failure, but how will clients know where to check in ?
If anyone can provide some tips it would be appreciated.
I'm not saying this is your best option, but.... you could configure your clients to connect to two servers, have the production box ("Server A") be the first one, and have the backup ("Server B") be the second one. Make sure they always check in with the last good connection first. Don't run the database service on Server B,null only on Server A - but backup your database to Server B.null Now if Server A goes down, just start-up Server B's database service with the last copy of the database and your clients will failover to B.null When Server A is back online, shutdown the service on Server B and startup on Server A.
Just never have both databases going at the same time!!! When Server A is ready to come back online, make sure to move the database out of the way and bring Server B's database back over to A, since B will have been updated while A was offline.
All that said, it's all only my opinion and may not reflect what the McAfee folks think and may not be perfect for your environment. I would suggest getting professional services involved so that you have a good documented plan in place incase something goes down.