I have a question about a hole in the ground scenario. I have two BES servers ServerA and ServerB both this their own SRP with BES running. They use the same SQL databse (on ServerC) What happens in the case of serverA crashing and the need to move 400+ users to serverB occurs. Since the server is not available I can not move the state databses. I currently have replicas of these on serverB but I am unsure if a move would recognize this. Also is there a way to automate the move if the 400+ users if serverA is not available?

I may be off here, but if you are using a shared config DB on a remote SQL server, I belive you should be able to install the ServerA instance on ServerB and manage from there. Just make sure that you have the BB services stopped and disabled on ServerA so you don't get the SRP conflict.

Hey abakcuh,

You can perform a sourceless move as a disaster recovery program. A sourceless move involves moving users from an unavailable BlackBerry Enterprise Server to an available one. Check out the steps listed in the PDF document - "BlackBerry Enterprise Server for IBM Lotus Domino Version: Maintenance Guide".

One note though, your BlackBerry Enterprise Servers need to be 4.0 Service Pack 3 or later.

THanks for the reply I will read the document. I have 4.0.3.11 (Service Pack 3 HF1) installed. Currently both servers are pointed to a third server running SQL Server 2006 Express Edition (Basically a MSDE with no governor). I plan to install a second SQL Express Server as a backup (Running blackberrydbbackup on the main pointing to seondary with blackberrydbrestore on it)

One more question on sourceless moves. If the server they are moving from is unavailable and I don't have a replica already on the other server of their state db what happens. Is a new one created? Will the user be bombarded by a lot of repeat messages?

Thanks

as far as i know. the move will not finish until you have the database on the dr server.

Yeah. I have basically moved half of my users to one of the server leaving the rest on the other. Once the moves complete I will create a replica of the state databases to each so that both servers have all states.

I'm not sure what exactly you are looking for but in our environment, we have 4 BES servers that point to a remote SQL database. Two BES are at our primary site and two are at a failover site. The two failovers share the same SRP as the two primary (PrimA = FailA, PrimB=FailB). The services on the failover services stay disabled so that the SRP's dont get locked. When we need to fail, we have a simple batch script that stops the services on the primary nodes, disables them, enables the services on the failover and starts them. We can be up and running in literally 2 minutes. Dont know if that helps.