I have a an Instance of SDE that uses a SQL Server back end. The SQL Server instance resides on its own machine, separate from the SDE machine. I have ArcGIS Server on the SDE machine as well with a number of mission specific published maps and locator services. (This is all v10 sp5; SQL Server 2008 R2.)
Recently I have been tasked with setting up a fail over machine that will primarily function as a redundant map and locator server; if the primary ArcGIS Server goes south, we roll to the secondary and everyone is happy. We use SDE to maintain an enterprise geodatabase, so the thought is to load SDE on the fail over machine and point it to the same SQL Server instance; that way while the primary machine is down, the editing process can continue.
Has anyone had this experience? Given the gray hairs I've accumulated over the years since ArcSDE 8.3, I have to think there are some gotchas I need to be aware of.
Your thoughts and advice are appreciated.
Recently I have been tasked with setting up a fail over machine that will primarily function as a redundant map and locator server; if the primary ArcGIS Server goes south, we roll to the secondary and everyone is happy. We use SDE to maintain an enterprise geodatabase, so the thought is to load SDE on the fail over machine and point it to the same SQL Server instance; that way while the primary machine is down, the editing process can continue.
Has anyone had this experience? Given the gray hairs I've accumulated over the years since ArcSDE 8.3, I have to think there are some gotchas I need to be aware of.
Your thoughts and advice are appreciated.