DR Database Synchronization Failures

Issue

The Disaster Recovery (DR) database can fall out of sync with the Primary database even when port connectivity succeeds. The embedded DB Analyzer may report an error.

Error: “Slave initialization failed.”

Cause

Occurs after unexpected server reboots or other system-level events.

Resolution

Reset the DR Vault database and restart synchronization to restore sync.

Prerequisites

  • Administrative access to the PAM Console.

  • Direct access to the DR PAM server.

  • An approved maintenance window, as services will be temporarily stopped.


Step 1: Stop the High Availability Sync Service

  • Log in to the PAM Console.

  • Navigate to Platform Configuration -> Systems -> System Status.

  • Open App Services.

  • Locate “SystemHighAvailabilityService”, which manages DR synchronization.

  • Stop the service to prevent automatic synchronization during the reset process.

Step 2: Stop the Vault Database Service on the DR Server

  • Log in directly to the DR PAM Server.

  • Open Run, type “Services.msc”, and press Enter.

  • Locate and stop the Sectona.Vault.Storage.Host service.

  • Open Task Manager and verify that no database-related processes, such as “mysqld.exe” or “mysqldump.exe”, are running.

The service must be stopped before modifying the database files.

Step 3: Reset the Vault Database Files

  • Navigate to the Sectona Vault drive.

  • Open the Sectona Vault Storage Host directory.

  • Open the nested Sectona Vault Storage Host folder.

  • Locate the following folders and files:

    • MySQLbin

    • VaultStorage

  • Open the “MySQLbin” folder and rename “mysqlini” to “mysql.ini.old”.

  • Return to the parent folder and rename “VaultStorage” to “VaultStorage_old”.

Step 4: Restart the Vault Service and Reconfigure

  • Start the “Sectona.Vault.Storage.Host” service.

    • The service automatically creates new “mysql.ini” and “VaultStorage” files and folders.

  • Open the newly created “mysql.ini”file.

  • Copy the required configuration parameters from “mysql.ini_old” to the new file, including:

    • binlog_expire_logs_seconds

    • max_connections

    • innodb_buffer_pool_size

    • innodb_buffer_pool_instances

  • Save changes and restart the “Sectona.Vault.Storage.Host” service to apply the updated configuration.

Step 5: Resume DR Synchronization

  • Log in to the PAM Console.

  • Navigate to Platform Configuration -> Systems -> System Status -> App Services.

  • Start the System High Availability Service.

  • Wait for the DR synchronization to start automatically.