This technical note outlines solutions you can use if your Reflection for the Web or Reflection Security Gateway master server goes down in your replication environment.
If the master server goes down, there are two possible courses of action:
See Technical Note 2174 for detailed information about configuring master and slave servers.
If it is possible to restore your master server within a short period of time, this is the easiest course of action. Be sure to restore the masterís ReflectionData directory to the state you want to have replicated to all the slave servers. For example, you may need to restore the masterís ReflectionData to the most recent backup, and then make additional configuration changes to the master before you enable the slaves, so that the slaves will replicate the correct master server configuration.
Note: When you create a new master server, all servers in your replicated environment take on the new master serverís configuration, so be sure that your new master server is configured the way you want all your servers configured before you convert any server to a slave server. You may want to use the most recent masterís ReflectionData directory backup as a starting point.
To change the role of a server to master in a replicated environment, follow these steps: