Aspera Faspex Automated Backups
Sections
Introduction
IBM Aspera Faspex is a file exchange application built on IBM Aspera High-Speed Transfer Server as a centralized transfer solution. With a web-based graphical user interface, Faspex offers more advanced management options for FASP high-speed transfer to match your organization’s workflow.
This article describes how to configure automated backups for Aspera Faspex.
Note: Faspex HA (High Availability) is not covered here as backup steps are different for HA. The HA Configuration steps already include automated backup configuration instructions.
Files to Backup After Faspex Installation
The following files may be needed if the Faspex Web Application needs to move to a new server. It is suggested to store these off the server. These only need to be collected one time or again if they are updated/changed:
/opt/aspera/faspex/faspex.rb.yml
/opt/aspera/faspex/config(faspex.yml, secret.yml)
/opt/aspera/faspex/lib/daemons/np/etc/keystore.jks
/opt/aspera/common/apache/conf/(*.key and *.crt)
/opt/aspera/common/mysql/database.rb.yml
Faspex Backing up via Command Line
The following script needs to be called root. It will create a backup folder in the backup path /opt/aspera/faspex/backup:
asctl faspex:backup_database
Faspex Automated Backup
This example will collect a daily backup of Faspex at midnight. Then at 12:01 AM remove backups that are older than 14 days from the target directory.
Schedule a crontab job to run the backup and cleanup by adding the following lines to root crontab. Open crontab in edit mode:
crontab –e
Add the following lines:
# Faspex Auto Daily Backup
0 0 * * * asctl faspex:backup_database >/dev/null 2>&1
# Faspex Delete Backups older then 14 days
1 0 * * * /usr/bin/find /opt/aspera/faspex/backup/ -type d -mtime +14 -exec rm -r {} \;
To learn more about PacGenesis, follow @PacGenesis on Facebook, Twitter, and LinkedIn, or visit us at pacgenesis.com.
