# Description

You must move to the same version of Faspex. For example, if you have Faspex 3.9.3 on your old system, your new system must also have Faspex 3.9.3.

# Instructions

### 1. Backup the database from your original Faspex installation.

Run the following command, which will save a backup:

# asctl faspex:backup_database
Note: On Windows, you must run Command Prompt as an Administrator to use asctl

The backup will be saved to the following location:

• Linux: /opt/aspera/faspex/backup/timestamp
• Windows: C:\Program Files (x86)\Aspera\Faspex\Backup\timestamp

### 2. Move files to the new machine

You are now ready to move files from your old machine to the new one. Copy the following files from your old machine:

#### Linux

• Database backup directory
• /opt/aspera/faspex/config/secret.yml
• /opt/aspera/common/apache/conf/*.key (if you have your own SSL certificate(s))
• /opt/aspera/common/apache/conf/*.crt (if you have your own SSL certificate(s))
• /opt/aspera/faspex/config/faspex.yml (if you made advanced Faspex configurations)

#### Windows

• Database backup directory
• C:\Program Files (x86)\Aspera\Faspex\config\secret.yml
• C:\Program Files (x86)\Aspera\Common Files\Aspera\Common\apache\conf\*.key (if you have your own SSL certificate(s))
• C:\Program Files (x86)\Aspera\Common Files\Aspera\Common\apache\conf\*.crt (if you have your own SSL certificate(s))
• C:\Program Files (x86)\Aspera\Faspex\config\faspex.yml (if you made advanced Faspex configurations)

Note: You cannot use the same Faspex license on multiple systems as this is a violation of your license terms.

If your original Faspex installation needs to stay up and running for a short period, you may ask your account manager for a temporary license to use on your new installation.

### 3. Prepare your new system

The rest of the instructions apply to the new machine.

On the new machine, ensure Faspex is installed, as well as Enterprise Server if your transfer server will be on the same system.

Download the installers and run through the Enterprise Server setup, then the Faspex setup as described in the product manuals. Make sure you install the same version of Faspex that you had on your old system.

### 4. Restore the database

Restore the database with the backup directory:

# asctl faspex:restore_database /path/to/your_backup

### 5. Create a Node API user

If your transfer server is located on the same machine as the Faspex server, you will need to create a Node API user to associate to the faspex transfer user.

Linux# /opt/aspera/bin/asnodeadmin -a -u node_user -p node_password -x faspexWindows# asnodeadmin -a -u node_user -p node_password -x faspex

The file that must be replaced is secret.yml, which you can do with the following:

Linux# cp /path/to/secret.yml /opt/aspera/faspex/config/secret.ymlWindows# copy C:\path\to\secret.yml C:\Program Files (x86)\Aspera\Faspex\config\secret.yml

If you copied over faspex.yml, run the following:

Linux# cp /path/to/faspex.yml /opt/aspera/faspex/config/faspex.ymlWindows# copy C:\path\to\faspex.yml C:\Program Files (x86)\Aspera\Faspex\config\faspex.yml

Open up faspex.yml in a text editor and look for the production section. Change Hostname and BaseURL to reflect your new Linux’s hostname or IP address.

### 7. (optional) Install your certificates

If you copied over certificates that you would like to continue using for your new Faspex installation, run the following command:

# asctl apache:install_ssl_cert cert_file key_file [chain_file]

### 8. Restart Faspex services

# asctl all:restart

### 9. Modify node storage

Whether your Faspex storage is on the local system or on a remote system, you will need to configure it in the web UI.

• Go to Server > File Storage. If your storage is local, click the dropdown next to localhost and select Edit. For Username and Password, enter the Node API credentials you created in step 6.
• If your storage is remote, click the dropdown next to localhost and select Add File Storage. Fill in the configuration details.