Migration

Purpose

Case 1 : Development → Staging → Production

You have several environments for your development cycle.
When development has been tested on one environment, you want to migrate the content (dashboards, users, etc) towards the Production environment.

Case 2 : Moving to another machine

You need to move your Alpana Server installation to a different machine (e.g. for architecture reasons).

*In this case, it is possible to move the license by de-activating it on the first machine and using it later on the target machine.
Check with your support what is the most appropriate and see License Deactivation.

Migration Procedure

To migrate from MachineX to MachineY, follow the below procedure :

1. Alpana Server must be installed on MachineY. If you are using a separate license, then the MachineY license must be activated too (though this can be done at a later time)
2. Perform a backup on MachineX
3. Perform a restore on MachineY
   

Migrated content

Note : all content from MachineX will be migrated :

• Users and their passwords
• Dashboards, Widgets, Data Sources
• Roles, Permissions, …
• Server Settings, …
• Runtime Connection
  

*If you are transfering your alpana server to a new one for migration, you will have to backup Alpana Runtime Data base also to migrate them at the same time.

Possible Issues

When migrating, some Dashboards may become unable to access their data.
This commonly happens when data is not accessible from the MachineY using the same Connection. Example : database is not accessible on the new network.
The fix is then to open the Dashboard and edit the Connection accordingly.
Error logs should help you find and fix the issue.