Recover BCS- Restoring Primary to Service

This process is used after a Business Continuity Service (BCS) failover where the Secondary Wave IP is now the active operational Wave IP. This process assumes that whatever problem existed with the Primary Wave IP has been resolved and this methodology has been chosen (see Choosing BCS Recovery method).  

Since roles are changing repeatedly in these instructions, the original Primary Wave IP (that is being restored to service) will be called Wave 1. The active Secondary Wave IP, currently in service, will be called Wave 2.

  1. Prepare Wave 1 to return to service. 
    NOTE: All of these initial steps should take place with the Wave not connected to the production network the Wave 2 is active on.
    1. Reset Wave 1 to a default configuration by running an system recovery (IRDD) drive on the system.
    2. Log in to Global Administrator (see Login to Wave IP Global Administrator). Remember the Wave IP will be on the default 192.168.205.1 IP address.
    3. Change the IP addresses to be on a network with internet access (see Set IP Network Settings).
    4. Run Vertical Updates to make sure the box is on the latest software to match the new Primary (see Use Vertical Updates).
    5. Create any Global Administrator accounts. 
    6. If an ODBC connection is set up for Call Classifier use on Wave 1.
    7. Change the IP addresses of Wave 1 to IP addresses on the production network (see Set IP Network Settings). Do not plug it into the production network yet!
      NOTE: The IP address should not be the same as Wave 2. It's not recommended to use the original IP addresses of Wave 1 either. This could cause an accident if devices attempt to connect to them.

       
  2. Clear the BCS settings from Wave 2.
    1. Log in to Global Administrator on the active Wave 2 (see Login to Wave IP Global Administrator).
    2. Click on General Settings.

       
    3. Click on the Business Continuity tab.

       
    4. Click the Clear Secondary Configuration button. This returns the Wave IP to normal operation and it no longer assumes a BCS relationship with another Wave.

       
    5. Click Done to leave the control panel.
       
  3. Power up the Wave 1 and connect it to the production network.
     
  4. Join Wave 1 to domain if domain membership is required. This would include adding Domain security groups for GA access.
     
  5. Set Wave 2 to be the temporary Primary. The goal here is to swap over the dataset with minimal down-time.
     
    1. Login to Global Administrator on Wave 2 (see Login to Wave IP Global Administrator).
    2. In Global Administrator, click on General Settings. 

       
    3. Chose the Business Continuity Tab at the top.

       
    4. Enter the IP address for the Wave 1 in the Secondary Server IP. Click Establish Business Continuity Connection button to connect the two Waves.

       
    5. When using ViewPoint Mobile (VPM), set the secondary Public IP address and port for ViewPoint Mobile to use. 
      Press the Apply button to Apply settings. 
    6. Click Run Backup to Secondary Now to make sure Wave 2 to transfer the database.
       
  6. Login to Wave 1 to cut it over to be the Primary.
    1. Login to Global Administrator on Wave 1 (see Login to Wave IP Global Administrator).
    2. In Global Administrator, click on General Settings. 

       
    3. Click on the Business Continuity tab.

       
    4. Click on the Click the Activate this Secondary Server button. This will disable Wave 2 and cut service over to Wave 1.

       
    5. Wave 1 is now the Primary Wave and should be kept in production at all times. Make sure to test all endpoints and services to make sure they are fully operating on Wave 1.
       
  7. Disconnect Wave 2 from the network. 
     
  8. Clear the configuration of Wave 2.
    NOTE: All of these initial steps should take place with the Wave not connected to the production network that Wave 1 is active on.
    1. Reset Wave 2 to a default configuration by running an system recovery (IRDD) drive on the system.
    2. Log in to Global Administrator (see Login to Wave IP Global Administrator). Remember the Wave IP will be on the default 192.168.205.1 IP address.
    3. Change the IP addresses to be on a network with internet access (see Set IP Network Settings).
    4. Run Vertical Updates to make sure the box is on the latest software to match the new Primary (see Use Vertical Updates).
    5. Create any Global Administrator accounts. 
    6. If an ODBC connection is set up for Call Classifier use on Wave 2.
    7. Change the IP addresses of Wave 2 to IP addresses on the production network (see Set IP Network Settings). Do not plug it into the production network yet!
       
  9. Clear BCS configuration on Wave 1
    1. Log in to Global Administrator on the active Wave 1 (see Login to Wave IP Global Administrator).
    2. Click on General Settings.

       
    3. Click on the Business Continuity tab.

       
    4. Click the Clear Secondary Configuration button. This returns the Wave IP to normal operation and it no longer assumes a BCS relationship with another Wave.

       
    5. Click Done to leave the control panel.
       
  10. Plug Wave 2 into the production network. 
     
  11. Restore BCS setup. 
    1. Login to Global Administrator on Wave 1 (see Login to Wave IP Global Administrator).
    2. In Global Administrator, click on General Settings. 

       
    3. Chose the Business Continuity Tab at the top.

       
    4. Enter the IP address for the Wave 2 in the Secondary Server IP. Click Establish Business Continuity Connection button to connect the two Waves.

       
    5. When using ViewPoint Mobile (VPM), set the secondary Public IP address and port for ViewPoint Mobile to use.
    6. Set the automated backup schedule for BCS. Adjust the time for each additional backup and then press the Add Backup button to add it to the list. See Planning the Business Continuity Service (BCS) backup schedule.

       
  12. Click Run Backup to Secondary Now to make sure the Secondary Wave IP is immediately configured for Failover.