When errors occur within the database and replicas, you must re-create the Global Master database (GMS).
You must re-install all the other servers in the cluster. You can do this by performing a fresh install of all the servers in the cluster.
It is recommended to rebuild the cluster by performing the following steps:
In the primary site:
Rejoin the database servers
Rejoin the Webserver servers
In other sites:
Rejoin the Master server
Rejoin the database servers
Rejoin the Webserver servers
To enable the First Install wizard, perform the following steps.
Log in as root to the server.
Perform the following:
Stop the Advanced Authentication server:
systemctl stop aauth risk-service
Remove the containers, network, and volumes which Advanced Authentication has created on the server:
docker-compose -p aaf -f /opt/aauth/docker-compose.yml -f /opt/aauth/docker-compose.sles.yml down -v
docker-compose -p risk -f /opt/risk/docker-compose.risk.yml down -v
Start the Advanced Authentication server:
systemctl start aauth risk-service
Browse the URL: https://<servername> in a web browser and rejoin the server.
You can rejoin the cluster in any of the following scenarios:
Ensure to enable the SSH daemon on the appliance. To do this, browse https://<aafwebservername>:9443 and log in as a vaadmin. Click the System Services tab and start the SSH service.
NOTE:If you want to recover the database server because of a failure, you must delete the server from the Cluster tab of the Administration portal, before re-joining the web server. To delete the server in the Cluster tab, see Configuring a Cluster
.
Perform the following steps to restore the database server:
Log in as root to the server.
Run the following commands:
Stop the Advanced Authentication server:
systemctl stop aauth risk-service
Remove the containers, network, and volumes that the Advanced Authentication has created on the server:
docker-compose -p aaf -f /opt/aauth/docker-compose.yml -f /opt/aauth/docker-compose.sles.yml down -v
docker-compose -p risk -f /opt/risk/docker-compose.risk.yml down -v
Start the Advanced Authentication server:
systemctl start aauth risk-service
Browse the URL https://<servername> in a web browser and rejoin the server.
After joining the database server to the existing cluster, the database replication takes place. If issues occur while joining the cluster configuration, ensure that the ports are accessible by the Global Master and the database server. For more information, see Configuring the Firewall
.
You can perform the following steps to restore a web server.
Log in as root to the server.
Run the following commands:
Stop the Advanced Authentication server:
systemctl stop aauth risk-service
Remove the containers, network, and volumes which Advanced Authentication has created on the server:
docker-compose -p aaf -f /opt/aauth/docker-compose.yml -f /opt/aauth/docker-compose.sles.yml down -v
docker-compose -p risk -f /opt/risk/docker-compose.risk.yml down -v
Start the Advanced Authentication server:
systemctl start aauth risk-service
Browse the URL https://<servername> in a web browser and rejoin the server.
After joining the database server to the existing cluster, the database replication takes place. If issues occur while joining the cluster configuration, ensure that the ports are accessible towards the Global Master and the database server. For more information, see Configuring the Firewall.
NOTE:
If you can access the Web server through the console, ensure to enable the SSH daemon on the appliance. To do this, browse https://<aafwebservername>:9443 and log in as a vaadmin. Click the System Services tab and start the SSH service.
If you want to recover the database server because of a failure, you must delete the server from the Cluster tab of the Administration portal, before re-joining the web server. To delete the server in the Cluster tab, see Configuring a Cluster
.
A database master server exists for a multi-site implementation.
NOTE:Ensure to enable the SSH daemon on the appliance. To do this, browse https://<aafwebservername>:9443 and log in as a vaadmin. Click the System Services tab and start the SSH service.
You can perform the following steps to restore the database master:
NOTE:If you want to recover the Database Master server because of a failure, you must delete the server from the Cluster tab of the Administration portal, before re-joining the web server. To delete the server in the Cluster tab, see Configuring a Cluster
. Delete the web server before re-joining.
Log in as root to the server.
Perform the following commands:
Stop the Advanced Authentication server:
systemctl stop aauth risk-service
Remove the containers, network, and volumes which Advanced Authentication has created on the server:
docker-compose -p aaf -f /opt/aauth/docker-compose.yml -f /opt/aauth/docker-compose.sles.yml down -v
docker-compose -p risk -f /opt/risk/docker-compose.risk.yml down -v
Start the Advanced Authentication server:
systemctl start aauth risk-service
Browse the URL https://<servername> in a web browser and rejoin the server.
After joining the database server to the existing cluster, the database replication happens. If issues occur while joining the cluster configuration, ensure that the ports are accessible towards the Global Master and the database server. For more information, see Configuring the Firewall
.
When a site goes down due to a configuration problem or a database issue, all the site infrastructure needs to be rebuild again.
Perform the following to restore the site:
Open the Administration portal.
Click Cluster > Register new site.
Specify the details.
A database master server exists for a multi-site implementation.
For the procedure to restore the database master, see Database Master is Down
.