This procedure requires advanced knowledge of the PortaSwitch database and file system structure, as well as a strong understanding of how PortaSwitch components operate and interact. We strongly recommend contacting
PortaOne Support
for assistance.
If your main site is severely damaged (e.g., by fire or flood) and cannot be repaired, you can reconfigure the secondary site to become the main site, ensuring that your PortaSwitch system remains fully operational.
The procedure consists of the following steps:
- Recreate the Configuration server on the secondary site. To do this, select the most suitable server and run the porta-configurator-install.sh script to activate it.
- Restore the Configuration server database from the daily backup stored on the secondary site’s database server. Use the cfgdb.sh script to restore the database from the backup and start all necessary services (such as MySQL, Apache, etc.) for its operation.
- Adjust the restored configuration.
- On the Configuration server web interface, move servers from the failed main site to the secondary site by changing their Site name property.
- Promote the stand-by database to the main database. To do this, create a new main database and replicate all data from the stand-by database to it. After this, delete the old stand-by database.
- Add instances that were not initially configured on the secondary site, such as web servers, CDR importer, etc.
- Apply the configuration.
From this point, the secondary site acts as the main site, providing a fully operational PortaSwitch system, with no restrictions or limitations.
