Recovering if the Legacy Orchestrator Primary Site Fails

If the Legacy Orchestrator primary site is unavailable, service can be recovered by switching to the Legacy Orchestrator secondary site as explained in this article.

Procedure Requirements

A. Certain procedures in this section require SSH access to the Legacy Orchestrator secondary site. To execute these procedures, you must know the skylight account credentials.

B. Other procedures require access to the Legacy Orchestrator secondary site through its web user interface. To execute these procedures, you must know the account credentials with an admin role to log in to the web interface.

Restoring the Data Store on the Legacy Orchestrator Secondary Site

The first step is to restore the most recent backup of the data store (from the primary site) on the secondary site. Then you start the Legacy Orchestrator software on the secondary site.

1. Open an SSH terminal session to the Docker host of the Legacy Orchestrator secondary site on port 22.

2. Log in as the skylight user.

3. Search for the latest backup database that was transferred from the primary site to the secondary site:

   ls -l /home/skylight/backups/
   

4. Take note of the name of the latest backup file.
   For example, if the latest backup file is named: DB_BAK_2026-04-20_04-00-00.tar.gz

5. Copy the backup file to the /tmp directory:

   cp /home/skylight/backups/<latest-backup-file-name> /tmp
   

   Example:

   cp /home/skylight/backups/DB_BAK_2026-04-20_04-00-00.tar.gz /tmp
   

6. Open an SSH terminal session to the Legacy Orchestrator secondary site CLI on port 2200.

7. Log in as the skylight user.

8. Restore the latest backup database:

   database restore <latest-backup-file-name>
   

   Example:

   database restore DB_BAK_2026-04-20_04-00-00.tar.gz
   

9. Start the Legacy Orchestrator web interface on the secondary site:

   services start
   

Expected result: Legacy Orchestrator software is now running on the secondary site.

Verifying the Switch to the Secondary Site

The final step is to verify the network inventory and ensure that the Legacy Orchestrator web interface is operational on the secondary site.

1. Use a supported web browser to log in to the Legacy Orchestrator web interface on the secondary site.
2. Click the logo (upper left corner of the page) to display the About Legacy Orchestrator dialog and verify the Legacy Orchestrator version.
3. Navigate to Devices > Managed Elements page and verify that the total count of Skylight devices (bottom left corner of page) is accurate.
4. Click the alarm icon (in bottom left corner) and verify that the current alarm count is accurate.
5. Navigate to Commission > Jobs page and verify that pre-existing configuration jobs are present.
6. Navigate to Collection > Reporting Status page and verify that:
   • The complete list of managed devices is displayed.
   • CSV time and Transfer time are both updated for all devices with performance data streaming enabled.