Setting Up the Legacy Orchestrator Secondary Site for Standby Operations

This article contains the procedures required to set up the Legacy Orchestrator secondary site to prepare it for standby operations.

Procedure Requirements

A. Certain procedures in this section 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.

B. Other procedures require SSH access to the Legacy Orchestrator secondary site. To execute these procedures, you must know the skylight account credentials.

Check Legacy Orchestrator Version

1. Open a web browser and use the following information to log in to the Legacy Orchestrator web interface:

   • URL: https://<secondary-site-ip>/businessweb/Login.html
     (you must replace <secondary-site-ip> with the IP address of your secondary site)
   • Username: admin (default)
   • Password: 2admin$admin (default)

   Note: These are default credentials and should be changed in production.

2. Select the logo in the upper left corner of the page and verify the version of Legacy Orchestrator is exactly the same as the version on the primary site.

3. If the Legacy Orchestrator versions do not match, update the secondary site so that its version of Legacy Orchestrator is exactly the same as the version on the primary site.

Stop Services on the Secondary Site

1. Open an SSH terminal session to the Legacy Orchestrator secondary site CLI on port 2200.
2. Log in as the skylight user.
3. Enter: services stop
   Legacy Orchestrator software stops.
4. Enter: exit to close the SSH session.

Set up a Cron Job to Periodically Delete Old Backup Files

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. Enter the following command:

   echo "0 0 * * * find /home/skylight/backups/* -mtime +7 -exec rm {} ;" | crontab
   

4. Enter: exit to close the SSH session.

Verify the Docker Host Has Enough Disk Space for Backup Files

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. Check the size of the backup file in the /home/skylight/backups directory:

   ls -l --block-size=M /home/skylight/backups/
   

   Example output:

   -rw-r--r--. 1 skylight skylight 50M Apr 23 05:15 DB_BAK_2026-04-23_05-00-00.tar.gz
   -rw-r--r--. 1 skylight skylight 50M Apr 23 05:30 DB_BAK_2026-04-23_05-15-00.tar.gz
   

4. Calculate the disk space required for all backup files in 7 days using the following formula:

   Disk space required = <size of backup file> × 672 / 1024 × 1.2
   

   Where:

   • The result is in GiB units
   • 672 = total number of files in 7 days = (60 / 15) × 24 × 7
   • 1.2 = 20% buffer for required disk space

   Example: If the backup file is 50 MiB, then approximately 40 GiB is needed:
   50 × 672 / 1024 × 1.2 = 39.375 ≈ 40 GiB

5. Verify the disk/partition used for the /home/skylight/backups directory has enough space:

   df -BG /home/skylight/backups/
   

   Example output:

   Filesystem     1G-blocks  Used Available Use% Mounted on
   /dev/md126          350G   47G      304G  14% /
   

If the Available space shown by the df -BG command is less than the disk space required (calculated in Step 4), use one of the following options:

Option 1: Add an Additional Disk for Backup Storage

• Add an additional disk to the Docker host of the Legacy Orchestrator secondary site and mount it to the /home/skylight/backups/ directory.
• Update the /etc/fstab file to ensure the disk/partition is mounted after a reboot.
• Use this option if the current disk or partition cannot be expanded, or if you want to store backup files on a dedicated disk.

Option 2: Expand the Existing Disk or Partition

• Increase the capacity of the disk or partition that contains the /home/skylight/backups/ directory.
• Use this option if the current storage can be extended and you want to keep the backup directory on the existing filesystem.

Expected Result

After completing these procedures:

• The secondary site and the primary site have the same version of Legacy Orchestrator software.
• Legacy Orchestrator software (services) is not running on the secondary site.
• A cleanup task at midnight deletes backup files older than 7 days in the /home/skylight/backups/ directory.
• The Docker host of the Legacy Orchestrator secondary site has enough disk space to store the backup files.