Database failover within the same Data Center

Last Updated : Oct 31, 2025 |

About this task

Use this procedure for POM to failover the database within the same data center if maintenance is planned only for database. In this case POM services are also required to be restarted along with the database failover. This type of failover must be performed during maintenance hours when POM is non-operational.

Note:

POM supports manual failover of the database within the same Data Center. Automatic failover of the database is not supported.

Before you begin

  • Ensure that the agent-less campaigns such as email, SMS, and notifications are not running.

  • Log off all agents from the system.

  • Stop all campaigns.

    Perform the following procedure on the Data Center in which database failover is planned:

Procedure

  1. Log in as a root user to all the POM servers configured in the Data Center.
  2. Stop the POM services.
  3. From the MSSQL Database AlwaysOn Dashboard, click Start Failover Wizard on the top-right corner of the page.
  4. Select the Secondary database server of the same Data Center as the new Primary.
  5. Refresh the database connections in MSSQL client.
  6. Ensure that after refresh, the AlwaysOn Dashboard displays the selected database node as Primary.
  7. Log in to the Avaya Experience Portal web console.
  8. Navigate to POM > POM Home > Configurations > POM servers > POM Manager.
  9. Select the primary POM server of Active Data center and click Start.

    Wait till all primary POM services have started and are in running status.

  10. Select Aux POM server of Active Data center and click Start.

    POM services start on all POM servers of the Active Data Center.

  11. Verify the status of all the services of the current/active Data Center are as listed in the Service status.
    Note:

    After local database failover, the previous Primary database server synchronization state automatically sets to Not Syncrhonizing (data movement paused).

    You must resume data movement and start the data synchronization only during maintenance hours, when POM processes are stopped. You can start POM processes and resume POM operations when the databases are synchronized.