Previous Topic

Next Topic

Book Contents

Book Index

Step-by-Step Instructions

You should not proceed unless the previous assumptions are in fact true.

  1. Nodes 1 and 2: Using the "Permissions" dialog in MOVEit Central Admin, create a Windows user (either a local or domain user) named "centralfailover" into the "MOVEit Admin" Windows group on both nodes. Use the same password on both nodes.

    The "centralfailover" user will be used by the other node for replication. You may use an alternate username, but make sure it is the same username on both machines.

  2. Nodes 1 and 2: Stop the MOVEit Central service on both nodes. Use MOVEit Central Admin's "Shut Down Service" command on Node 1 if tasks could be running. You may issue the command "net stop moveitcentral" or use the Windows control panel to stop the service on Node 2.
  3. Nodes 1 and 2: If the MOVEit Central Config program is not already running, start it via the shortcut located in "Start | Programs | MOVEit Central" on both nodes.
  4. Nodes 1 and 2: Enter the same failover-capable license key in the License tab on both nodes.
  5. Nodes 1 and 2: Configure the email addresses of an administrator in the Errors tab on both nodes. If you do not enter these values, you will not be emailed when serious errors or failover events are encountered.
  6. Node 1 ONLY: Go to the Failover tab and configure the following information:
  7. Node 2 ONLY: Go to the Failover tab and configure the following information:
  8. Nodes 1 and 2: If you are using MySQL as your database, click the "Clear SQL Rep..." button on the Failover tab on both nodes.

    Note: The first time that you click "Clear SQL Rep...", you may see error messages that state that there is nothing to replicate. You can ignore these errors.

  9. Node 2 ONLY: If you are using MySQL as your database: On node 2 only, click the "Copy Database" button on the Failover tab to do a one-time replication of the database from the primary node to the secondary node. This may take several minutes if your existing database is large.

    You may also need to change the "Copy from" value on the "Copy statistics database" dialog which will appear. If you encounter "'From' directory does not exist or cannot be accessed" errors, use the following command-line sequence to confirm this MOVEit Central can connect to the other MOVEit Central via Windows File Sharing, that the "centralfailover" user may be authenticated to the other MOVEit Central, and that "centralfailover" enjoys read access to the file share listed in the "Copy from" field.

    C:\>net use H: \\192.168.3.172\micstats /user:centralfailover
    The password or user name is invalid for \\192.168.3.172\micstats.

    Enter the password for 'centralfailover' to connect to '192.168.3.172': *******
    The command completed successfully.

    C:\>H:

    H:\>dir stats.myi
    09/22/2005 02:28 AM 53,248 stats.MYI

    H:\>copy stats.myi c:\
    1 file(s) copied.

  10. Node 1 and 2: If you are using Microsoft SQL Server as your database: On both nodes, make sure that you set the registry entry DWORD named SuppressDBRep to a value of 1. This registry entry is found in one of these locations (you may need to add the registry entry):

    You do not want the SQL Server database to be replicated because Node 1 and Node 2 share the same SQL Server database.

  11. Node 1 ONLY: Start the MOVEit Central service. (From a command line, you may issue the command "net start moveitcentral".)
  12. Node 2 ONLY: Start the MOVEit Central service. (From a command line, you may issue the command "net start moveitcentral".)
  13. Node 1 ONLY: Open MOVEit Central Admin and connect to "localhost". Within about three minutes, MOVEit Central Admin's Failover tab should show that Node 1 is the primary MOVEit Central node and Node 2 is the secondary MOVEit Central node.
  14. Node 1 ONLY: Use MOVEit Central Admin's Command | Reset Tamper Detection menu item to reset tamper detection for the failover system.