This content has been marked as final. Show 4 replies
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.
Christopher.... the way you described is exactly what I have done at several locations and it works great. I would recommend using this method as well.
you answered a question I did not ask yet :)
thanks for the answer! happy