Appliance migration allows easy migration from a source gateway to a target gateway while following best practices using gateway secure backup and restore.

Prerequisites & Assumptions

• The source and target gateways should be up and running to perform backup and restore.

• The source gateway must be registered to the system before the process begins.

• The target gateway must have XML Management Interface enabled. The XML Management Interface must be accessible via the MGMT network interface with the supplied user and password.

• The target gateway must have a different system identifier (device name) than the source gateway.

• The private and public keys must be available before the secure backup or restore start. The public key must be uploaded to the source gateway while the private key might be uploaded to the target gateway, or just be accessible from the local file system.

• If the source gateway is part of an API-Connect environment, please pay attention to the following notes:

  • When connecting a gateway to an API Connect environment for the first time, the Application Optimization feature is automatically enabled on that gateway.

  • To complete the restore phase of this migration process, the target gateway must also have the Application Optimization feature enabled.

  • If the Application Optimization feature is not enabled on the target gateway, you may contact the gateway support team for assistance.

Limitations

• This process will NOT handle the following:

  • B2B persistence store data, HSM data and RAID data

  • Gateways configured with Application Optimization

  • Gateways configured with Link Aggregation/Standby-Control

  • Custom system health metrics, device groups and DNS translations configured for the source gateway in the system

Next: Input basic details