...
Please note that in the case of failure of your primary machine, there is no automatic failover mechanism to forward users to the secondary machine. Users will be manually redirected to the secondary machine using either of the following methods:
Updating the DNS entry of the primary SMACS machine to point to the IP of the secondary machine.
Instructing users to connect to the DNS name or IP address of the secondary machine to continue their work.
| Note |
|---|
Please note that CDR Data and Audit logs will not be synced back from the secondary machine to the primary machine in the case of a failure. |
...
The primary machine must have a High Availability license installed (provided by Stack8).
The secondary machine must be a carbon-copy of the principal machine (i.e. an existing SMACS machine cannot be repurposed to be used as a secondary machine).
Both machines must be able to communicate over port 443.
Both machines must be on the same version of SMACS.
Both machines must be running SMACS version 7.4 or later.
Cloning the SMACS VM
Log into vCenter with your credentials
...
Search for the SMACS machine using the Search tool. You can use the hostname, the FQDN or IP address if they were provided during deployment
...
Shut down the machine with the "Shut down Guest OS" button in the bar next to the server name
...
Once the machine is powered off (you should see the preview switching to “Powered Off”), click on "Actions" > "Clone" > "Clone to Virtual Machine"
...
...
Follow the wizard that appears on-screen to select which name, host and data store to use
...
Wait until the task is completed (Check "Recent Tasks" tab for more details)
Start the newly created machine using the "Power On" button in the bar next to the server name.
Log into the stack8-console with the s8admin account created when the machine was initially deployed.
Select “View/Edit Network Configuration” and change the configuration so that the machine uses a different unused IP address and save the changes.
(Optional) Create a new DNS entry to forward to your secondary machine.
Start the primary SMACS machine.
Test both SMACS instances to validate that they are in working condition.
PROCESS COMPLETED!
Continue to the next section to enable HA in your SMACS environment
Enabling HA in SMACS
Log into the principal SMACS machine as an administrator.
Select the Setting icon on the top-right corner of the window.
In the admin menu, select “Disaster Recovery” and then select “High Availability Management”.
Click on the “Enable High Availability” toggle.
Set the “Sync Interval” to determine the frequency of the syncs between the primary and secondary machines.
Enter the FQDN or IP address of the secondary SMACS machine in the field “FQDN of Secondary Machine”.
Click “Save”.
That’s it! SMACS will then attempt to log into the secondary machine and perform a full sync. If the sync is successful, a green success message will appear in the top-right corner.
If the sync fails, a red failure message will appear in the top-right corner with the failure reason. Please refer to the “Common Failure Causes & Resolution” subsection of the “Troubleshooting HA in SMACS” section of this guide for more information.
Disabling HA in SMACS
Log into the principal SMACS machine as an administrator.
Select the Setting icon on the top-right corner of the window.
In the admin menu, select “Disaster Recovery” and then select “High Availability Management”.
Disable the “Enable High Availability” toggle.
Click “Save” to confirm.
Troubleshooting HA in SMACS
...
Just like other items in the System Health Status page, a warning will not force users to log out of the application but it will appear as an orange badge within the top bar of the application if you are an administrator and will trigger an email if the System Health Status Notifications have been enabled.
Common Failure Causes & Resolution
...
SMACS Upgrade Best Practices When Using HA
Upgrade the stack8-console on the primary and secondary machines if an upgrade is available.
Upgrade the inactive side of the primary and secondary machines to the latest SMACS version.
Route the traffic on the primary machine to the newest version.
Test the primary machine is working as expected.
Route the traffic on the secondary machine.
NOTE: In cases where a sync was being performed during a SMACS upgrade and the sync failed, we recommend waiting for the next sync to occur or saving the High Availability settings again to trigger a fresh sync.
NOTE 2: Steps 1 through 4 do not cause any downtime. Feel free to perform those steps at any time of the day.
...