- AXWAY SECURE TRANSPORT SUPPORTS MLLP INSTALL
- AXWAY SECURE TRANSPORT SUPPORTS MLLP FULL
- AXWAY SECURE TRANSPORT SUPPORTS MLLP PLUS
AXWAY SECURE TRANSPORT SUPPORTS MLLP INSTALL
Mysql/bin/mysqldump -defaults-file=conf/nf -uroot -p st -no-data > /path/to/backup/directory/schema.sqlīack up the MySQL Database without the large Server Log and File Tracking related tablesįor clean install of SecureTransport 5.3.6 and above use: Start the DB service only and dump the SecureTransport DB schema In all commands below replace with the actual database password.
AXWAY SECURE TRANSPORT SUPPORTS MLLP FULL
ST Edges should be following the procedure for a full backup above. This type of backup is suitable for Backends only. The resulting backup file will be smaller, but the drawback is that you will lose all existing and historical log activity. This type of backup will exclude all server and transfer logs, and the historical file logs. Tar -xzvf /path/to/backup/directory/ST_5.X.X.tar.gz -C /Įxcluding the Server Log, File Tracking and historical logs Backup SecureTransport excluding the Server Log and File Tracking-related DB tables, and without the historical logs Rename the current installation directory On the new server, make sure that you meet the installation prerequisites and install the same ST version in the same location. The below steps are valid only if the backup is taken following the steps from Backup SecureTransport with all MySQL tables and historical logs. Restore SecureTransport with all MySQL tables and historical logs Make sure you have sufficient space in /path/to/backup/directory to accommodate the tarball file. Tar -zcvf /path/to/backup/directory/ST_5.X.X.tar.gz /opt/Axway Ĭreate a tarball of SecureTransport's directory If any lefover processes are found, you can kill them manually with kill -9. Make sure you have sufficient space in the destination directory, where the backup file will be stored. Due to this, the size of the backup can be considerable.
AXWAY SECURE TRANSPORT SUPPORTS MLLP PLUS
This type of backup will keep all server and transfer logs, plus any historical file logs. Keeping the Server Log, File Tracking and historical logs Backup SecureTransport with all MySQL tables and historical logs In case of multiple ST nodes in the cluster, it is recommended that application backup and restore is done for each ST node independently. Refer to your virtualization administrator for suggestions. When ST is installed on a VM, another backup mechanism is to take a snapshot of the VM machine, with the ST services stopped. The backup should be taken using the same OS account that ST was installed with (and is running under). The backup consist of archiving the contents of the Secure Transport directories, preserving the subdirectory structure. SecureTransport installed on Linux Prerequisites and considerations IMPORTANT NOTE: The backups created with the below procedures, must be restored on machines with the same IP(s) and hostname and into the original installation folder of your previous SecureTransport installation! Failure to do so will result in a corrupted backup.