Some initial questions to consider:
- What operating system is the broker on?
- What type of database does Harvest use?
- Is the database on the same machine as the broker?
- What DR plan is already in place for the database? Or should the database be included in the same DR plan as the Harvest application?
A very simple fail-over scenario would involve installing the SCM Server software on a second backup machine, configuring the database connections so that it can connect to the same Harvest database as the primary, and making use of the "RT_FORCE_NODE_NAME" environment variable to "rename" the broker on this second machine to match the name on the primary. Then if the primary machine goes down you would
1. Set up an alias in the DNS directory pointing the SCM Broker name to the IP address of the backup machine
2. Start the broker on the backup machine.
This is not a complete plan, but a simple example. You should look at this as a starting point from which you could build to devise a plan that will work for your company and environment.
Information about the RT_FORCE_NODE_NAME environment variable can be found in chapter 15 of the Implementation Guide.
Let me know if this is what you needed.