Link Search Menu Expand Document

Move or Restore Orchestrator

You can:

Move Orchestrator from Virtual Machine to Cloud

IMPORTANT: Before you begin, make sure the on-premise Orchestrator and cloud Orchestrator are the same version. The minimum required version for cloud migration is 8.5.7.

WARNING: The Orchestrator blueprint (obtained through the following procedure) will not restore the IPSec UDP key material. When you import the blueprint, Orchestrator will start a new IPSec UDP key material rotation. To prevent Orchestrator from doing this, make sure that the appliance has a connection to the Orchestrator or the Cloud Portal before you proceed. This will ensure that the appliance obtains the existing key and tunnels will remain up.

To move Orchestrator from virtual machine to cloud:

  1. Place a purchase order with TAC to provision the cloud Orchestrator. For more information on contacting TAC, see Working with Support.

  2. Open a customer case with TAC to enable the Orchestration.

  3. To pause orchestration and export the Orchestrator blueprint, do the following:

    NOTE:
    You must export the Orchestrator blueprint 24-36 hours before the migration is scheduled.

    Do not make any network changes while Orchestrator is exporting the blueprint.

    1. In Orchestrator, navigate to Orchestrator > Orchestrator Server > Tools > Maintenance Mode.

    2. Click Add.

      The Configure Maintenance Mode dialog box opens.

    3. Select the appliance you want to pause orchestration on.

    4. Select Pause Orchestration.

    5. Click OK.

    6. Click Close.

    7. Navigate to Orchestrator > Orchestrator Server > Tools > Orchestrator Blueprint Export.

      The Orchestrator Blueprint Export dialog box opens.

    8. Select the blueprint type: Template or Migration.

    9. Click Export. Orchestrator downloads an SQL file to your local desktop.

  4. Provide the exported file to Support.

  5. Shut down the existing Orchestrator before the migration is scheduled.

    Silver Peak DevOps will notify you when the migration is complete. Estimated duration of migration:

    • Small orchestration: 1 - 2 hours

    • Medium orchestration: 2 - 4 hours

    • Large orchestration: 6 - 8 hours

  6. After the migration is complete, delete your on premises Orchestrator.

  7. Do the following to enable orchestration.

    1. In Orchestrator, navigate to Orchestrator > Orchestrator Server > Tools > Maintenance Mode.

    2. Click Add.

      The Configure Maintenance Mode dialog box opens.

    3. Select the appliance you want to enable orchestration on.

    4. Clear Pause Orchestration.

    5. Click OK.

    6. Click Close.

  8. Do the following to enable IPSec UDP.

    1. Navigate to Configuration > Security > IPSec Key Rotation.

      The Schedule IPSec Key Rotation dialog box opens.

    2. Select Enable Key Rotation, and then click Save.

Move Orchestrator from Cloud to Virtual Machine

WARNING: The Orchestrator blueprint (obtained through the following procedure) will not restore the IPSec UDP key material. When you import the blueprint, Orchestrator will start a new IPSec UDP key material rotation. To prevent Orchestrator from starting a new IPSec UDP key material rotation, make sure that the appliance has a connection to the Orchestrator or the Cloud Portal before you proceed. This will ensure that the appliance obtains the existing key and tunnels will remain up.

  1. Complete the following steps to pause orchestration on the Cloud Orchestrator and export the Orchestrator blueprint.

    NOTE:
    You must export the Orchestrator blueprint 24-36 hours before the migration is scheduled.

    Do not make any network changes while Orchestrator is exporting the blueprint.

    1. In Orchestrator, navigate to Orchestrator > Orchestrator Server > Tools > Maintenance Mode.

    2. Click Add.

      The Configure Maintenance Mode dialog box opens.

    3. Select the appliance you want to pause orchestration on.

    4. Select Pause Orchestration.

    5. Click OK.

    6. Click Close.

    7. Navigate to Orchestrator > Orchestrator Server > Tools > Orchestrator Blueprint Export.

      The Orchestrator Blueprint Export dialog box opens.

    8. Select the blueprint type: Template or Migration.

    9. Click Export. Orchestrator downloads an SQL file to your local desktop.

  2. Shut down the existing Cloud Orchestrator before the migration is scheduled.

  3. Complete the migration by importing the migration file.

    1. If you are migrating from the cloud to on-prem, you will need to enter the account name and key in the Orchestrator UI in the on-prem (target) Orchestrator.

      NOTE: If you are migrating from on-prem to cloud, you do not need to perform this step because the Cloud Orchestrator will already have the account name and key.

    2. Approve the target Orchestrator from the source Orchestrator, or ask TAC to approve it.

    3. Ensure that the source Orchestrator has at least one valid user. If the source Orchestrator does not have a valid user, you will not be able to log in to the UI.

    4. Download the migration file from the source Orchestrator UI. The migration file name will be similar to SilverPeakOrchBlueprint-2018.06.28.sql

    5. Shut down the source Orchestrator. If the source Orchestrator is in the cloud, you can stop or deactivate it.

    6. Use WinSCP or similar file transfer application to copy the migration file to the target Orchestrator server (for example, ../tmp/SilverPeakOrchBlueprint-2018.06.28.sql).

    7. SSH as admin into the target Orchestrator server.

    8. Go to the gms directory.

      $ cd gms

    9. Stop Orchestrator, but keep the database running.

      1. Change to root user. You will be prompted for the Orchestrator root user password.

        $ su

      2. Stop the GMS Java server and the database.

        $ service gms stop

      3. Exit out of root user.

        $ exit

      4. Start the database again.

        $ dbserver start

      5. If you are migrating to the cloud, then you must set the database connection parameters in the environment. If you do not set the parameters in the environment, Orchestrator will use the built-in values and will connect to the local database.

        export DB_HOST_NAME = ""

        export DB_PORT = ""

        export DB_USER_NAME = ""

        export DB_PASSWORD = ""

        export DB_DATABASE="vistapoint"

        export CONTAINER_MODE = "true"

      6. Run the following script.

        $ ./setup/golden-orch-import.sh ~/tmp/SilverPeakOrchBlueprint-2018.06.28.sql

      7. Restart the Orchestrator server.

        1. Change to root user. You will be prompted for the Orchestrator root user password.

          $ su

        2. Start the GMS service and database.

          $ service gms start

      8. Delete the source Orchestrator.

  4. Do the following to enable orchestration.

    1. In Orchestrator, navigate to Orchestrator > Orchestrator Server > Tools > Maintenance Mode.

    2. Click Add.

      The Configure Maintenance Mode dialog box opens.

    3. Select the appliance you want to enable orchestration on.

    4. Clear Pause Orchestration.

    5. Click OK.

    6. Click Close.

  5. Do the following to enable IPSec UDP.

    1. Navigate to Configuration > Security > IPSec Key Rotation.

      The Schedule IPSec Key Rotation dialog box opens.

    2. Select Enable Key Rotation, and then click Save.

  6. Open a customer case for TAC to shut down and decommission the cloud Orchestrator. For more information on contacting TAC, see Working with Support.

  7. Notify TAC when the migration is complete. TAC will delete the Cloud Orchestrator.

Move or Restore Orchestrator Using a Backup

You may want to restore a new Orchestrator for a variety of reasons, including resizing or moving between virtual machines. Complete the following steps to restore Orchestrator from an existing Orchestrator backup.

NOTE: We recommend you review the release notes specific to the Orchestrator version that you are running in your network before you move or restore Orchestrator using a backup. You can download the release notes from the Silver Peak Technical Support Portal.

WARNING: If you are not moving the IP address of the existing Orchestrator VM to the new Orchestrator VM, you must verify connectivity between the Cloud Portal and all appliances before you begin. When Orchestrator is moved to a new VM, the new VM’s management IP address will be pushed to all appliances via the Cloud Portal. Appliances will only be able to reach Orchestrator via the Cloud Portal until they receive the new management IP.

  1. Deploy a new instance of Orchestrator on a new VM and upgrade Orchestrator to the exact same version as your current Orchestrator.

    NOTE: You do not need to configure anything on the new Orchestrator.

  2. Take a manual backup of your current Orchestrator (Orchestatror > Software & Setup > Backup > Backup Now).

  3. Copy the backup file from your current Orchestrator to the /home/gms folder on the new Orchestrator and rename it to gms.zip.

  4. Shut down your current Orchestrator.

  5. SSH as Admin into the new Orhestrator and do the following:

    1. If you are running release 9.4.x or later, enter the following:

      whoami

      If the response is not gms, enter the following, and then provide the password.

      sudo su - gms

    2. Switch to the root user and stop the Orchestrator service:

      $ su

      # service gms stop

    3. Log out of root and run the restore script:

      # exit

      $ /home/gms/gms/setup/restore.sh 2>&1 | tee /tmp/restorelog

    4. Switch to the root user and start the Orchestrator service:

      $ su

      # service gms start


Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.

Open Source Code:

Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America