Moving Angelfish to Another Server
Moving Angelfish to a new server is a simple task - here's a brief summary:
- Two Angelfish instances are involved: "Current" and "New"
- Install the same version of Angelfish on New as used on Current
- Copy the Data Directory from Current to New
Complete steps are listed below.
You need to use the same Server ID in the new instance that the current instance uses.
If your New instance is able to reach the Internet, please open a support ticket and ask for your Server ID to be unlocked.
If your New instance is on a secure network, you'll need to open a support ticket from the New instance and request a manual license.
Steps to Move Angelfish to Another Server
- Two Angelfish instances are involved: "Current" and "New"
- Install the same version of Angelfish on New as used on Current
- When installation is complete, Connect to the UI on New
- Enter the same Server ID in New as used on Current
- Click the Request Manual License link to open a support ticket
- Our Support team will respond with a license for New: use it to unlock the instance
- Once you're able to login to New, stop Angelfish on *both* New and Current
- On New, delete all files & subdirectories in the /data/ directory
- On Current, copy all files & subdirectories in the /data/ directory to /data/ on New.
- On New, start Angelfish & login
- On Current, uninstall Angelfish once the migrated data has been verified
NOTES
- The above steps work with both Linux and Windows migrations
- On Windows, use the Start Menu shortcuts to stop & start Angelfish
- On Linux, use agfsctl or the appropriate systemd / systemctl command
- You can also move Angelfish from Linux to Windows, or from Windows to Linux
- Log Tracking info can be invalidated if paths to log files change
- This mostly applies to Local Datasources
- If you have questions, please open a support ticket
Get help for this page
Jitbit HelpDesk