Open topic with navigation
1. Returning to full redundancy after an outage
When the problem with the primary Wave has been diagnosed and repaired, it is time to return your BCS configuration to full redundancy. There are two methods to do this:
|
•
|
Leave the secondary Wave in place. This is the preferred—and simpler—method. The secondary Wave will be converted to the primary Wave and will provide continuous service throughout the procedure. |
|
•
|
Switch back to the primary Wave. This option should only be used if the physical location of both Waves causes a problem with the secondary Wave becoming the primary Wave. This method requires a brief service outage, because both Waves will be offline at one point, but switching back to the primary Wave can be done with minimal loss of service as described below. |
Leaving the secondary Wave in place
To leave the secondary Wave in place
|
1
|
Clear the secondary Wave configuration:
|
|
•
|
On the secondary Wave, start the General Settings applet. |
|
•
|
On the Business Continuity tab, click Clear secondary configuration. This removes the BCS settings and makes it a normal Wave again. |
|
2
|
Activate the Wave licenses on the secondary Wave:
|
This step is required because the secondary Wave does not have activated licenses, which were only installed on the primary Wave. Before the secondary Wave can become the primary Wave, you must activate its licenses.
Important! This may require contacting Vertical Customer Support to raise the activation count. Plan time for this step into your restoration plan.
Activate licenses in the License Control Panel. The previous secondary Wave is now your new primary Wave.
|
3
|
Return the previous primary Wave to service as the new secondary Wave: |
|
•
|
On the Business Continuity tab in General Settings, click Disable Business Continuity Connection. |
|
•
|
Connect the new secondary Wave to the network. |
|
4
|
Re-enable failover on the new primary Wave:
|
Perform the steps in Configuring the primary Wave again, specifying the secondary Wave's IP addresses and reconnecting to it.
Switching back to the primary Wave
To switch back to the primary Wave
Note: In the following steps, the original primary Wave is called "Wave1". The currently active secondaryWave (after failover) is called "Wave2".
|
1
|
Recover Wave1 to a blank system: |
|
•
|
Use the USB Recovery Image to restore the Wave1 (or a replacement system) to factory defaults—after restoring, it will be a new, blank Wave system with no Wave database installed. |
|
•
|
Install any Hotfixes or other upgrades so that the software on the new system is identical to the software installed on Wave2. |
|
•
|
If you do not already have a base Wavedatabase backup, make one of the system now. |
Important! Make this backup now, if necessary—do not do it at any later step.
|
2
|
Set Wave1’s IP addresses to be on the same network as Wave2:
|
|
•
|
Best practice is to not use any of the same IP addresses as the original primaryWave if possible, to minimize any potential problems. |
|
•
|
Join Wave1 to the domain if necessary. |
|
•
|
Set a unique fully-qualified domain name (FQDN) setting for Wave1 in the Global Administrator Management Consol. This must be different from Wave2's FQDN. |
|
3
|
Clear the Secondary Configuration on Wave2:
|
|
•
|
On Wave2, in General Settings, click the Business Continuity tab. |
|
•
|
Click Clear Secondary Configuration. This removes the Business Continuity settings and make Wave2 a normal Wave again. |
|
4
|
Set up Wave2 as a new primary Wave temporarily:
|
|
•
|
On Wave2, on the Business Continuity tab, enter the IP address of the old primary Wave as Secondary Server IP. |
|
5
|
Transfer the Wave database to Wave1:
|
|
•
|
On Wave2, click Backup Now to perform an immediate backup, and transfer the database to Wave1. |
|
6
|
Disconnect Wave2 from the network and failover to Wave1:
|
|
•
|
When the backup on Wave2 is complete, disconnect the network connection on Wave2. |
|
•
|
On Wave1, click Activate Failover to Secondary. |
|
7
|
Validate that Wave1 is fully functional and all devices are connecting to it:
|
When Wave1 becomes active, all services should come up and Wave1 should be recognized by clients. Validate that all devices are connecting to Wave1 as expected.
|
8
|
Activate the Wave1 licenses:
|
The restored database on Wave1 does not have activated licenses at this point. Before it can be the primary Wave, you must activate its licenses. This may require contacting VerticalCustomer Service to raise the activation count. Please plan time for this step into your restoration plan.
|
9
|
Clear Wave2 and put it back on the network:
|
Do not reconnect Wave2 to the network yet.
|
•
|
Using the base Wave database backup you created in step 1, restore it to Wave2. Wave2’s database will now look like a freshly recovered Wave. |
|
•
|
Reconnect Wave2 to the network and assign IP addresses on the same network as Wave1. |
|
•
|
Join Wave2 to the domain if necessary. |
|
•
|
Set a unique FQDN setting for Wave2 in the Global Administrator Management Console. This must be different from Wave1's FQDN. |
|
10
|
Re-enable Business Continuity on Wave1:
|
Perform the steps in Configuring the primary Wave again, specifying Wave2's IP addresses and reconnecting to it.