Restoring your Faspex Database

Aspera strongly recommends backing up your Faspex database as a precaution in case of system failure. You may also want to restore your Faspex configuration folder and database on a new machine.

CAUTION:

The restored version of your Faspex and database must match the version of Faspex on the machine to which you are restoring.

Restore your Faspex database by copying the backup directory to the new location and run the following, where dir is the directory where the backup has been copied:
```
> asctl faspex:restore_database C:\dir
```
Reset the Faspex hostname.
Change the hostname by running the following from a Windows command prompt:
```
> asctl apache:hostname hostname
```
Change the hostname or IP address in your faspex.yml file. The faspex.yml file can be found at the following location: C:\Program Files (x86)\Aspera\Faspex\config\secret.yml. Change Hostname: and BaseUrl: to include the new hostname or IP address.
Update the aspera.conf file with the new hostname using the following asconfigurator command:
```
asconfigurator -x "set_server_data;server_name,hostname"
```

Create a new node admin user. Run the following command:

> asnodeadmin -a -u nodeadmin -p password -x faspex

Restart Aspera services.
After updating aspera.conf, restart the following services:
- Aspera Central
- Aspera NodeD
- Aspera HTTPD
You can restart these services from Control Panel > Administrative Tools > Services.
Copy your SSL certificates and keys.
If you have a custom SSL Certificate, or want to preserve the existing one, copy the SSL certificates and keys to the following locations:
- C:\Program Files[ (x86)]\Common Files\Aspera\Common\apache\conf\server.crt
- C:\Program Files[ (x86)]\Common Files\Aspera\Common\apache\conf\server.key
Keep a backup of those files in that directory.
Copy the secret.yml file from your backup to C:\Program Files (x86)\Aspera\Faspex\config\secret.yml. Keep a backup of the original secret.yml file in the directory.
Restart Faspex.
```
> asctl faspex:restart
```
Migrate the server to the new public IP (or EIP in Amazon if you're using an On-Demand system), or change your DNS to point the hostname to the new server IP.
Modify the localhost configuration.
Launch Faspex from a browser and log in using the Faspex admin account. Go to Server > File Storage and edit the localhost node. (Click the box icon next to localhost and select Edit.) In the Basic Configuration section, enter the username and password you specified when you created the node admin user in the steps above.
Note: Remote storage locations should be accessible without changes.

Note: If you created post-processing scripts, you must copy and restore them manually. For more information on post-processing scripts, see Enabling Post-Processing Scripts.

Each email template notification you have customized must be regenerated from the UI. For more information, see Configuring Email Notifications.