16.3 Scheduling Backup

Advanced Authentication allows you to automate the backup at a specific time as per your requirement. Also, override the scheduled time and start the backup process at any given time. You can also set the location to store the backup files and delete old backup files while retaining a specific set of files.

You can perform the following tasks:

You can configure the cron schedule to backup the configuration at regular intervals. For example, to schedule a backup at 2.00 A.M. only on Saturdays, set the configuration as * 2 * * sat.

The expression * * * * * is defined in the following table:

Expression

*

First asterisk

*

Second asterisk

*

Third asterisk

*

Fourth asterisk

*

Fifth asterisk

Description

minute

hour

day of month

month

day of week

Value

0-60

0 - 23

1 - 31

1 - 12

0 - 6 (Sunday=0) or sun, mon

The logs are displayed in the celery_long.log file.

NOTE:After upgrading to Advanced Authentication 6.3 SP5, it is required to re-configure the backup as per your requirement.

16.3.1 Scheduling Backup

To schedule backup, perform the following:

  1. Click Backup/Restore > Schedule Backup.

  2. Set the configurations to schedule the backup in the Backup schedule page.

  3. Set the cron expression for the schedule in the first column.

  4. Select Backup database from the drop down.

  5. Click Save.

    NOTE:You can click the > (Run now) button adjacent to the cron expression to run the program (export) immediately.

16.3.2 Scheduling Synchronization of Backups to a FTP Server

To synchronize the backed up log files from a container to an FTP server, remove the backup files while retaining a specific number of files, perform the following:

  1. Click Backup/Restore > Schedule Backup.

  2. Set the cron expression for the scheduled synchronization in the first column.

  3. Select Upload to FTP server from the drop down.

  4. Specify the following details:

    • The host name of the FTP server in Hostname.

    • Path of the folder in the FTP server in Upload Folder.

    • Username and Password to upload the backup files.

    • Number of files to retain after each upload process in Keep last.

      For example, to retain the latest five backup files in the FTP server, set Keep last to 5.

  5. Click Save.

    NOTE:You can click the > (Run now) button adjacent to the cron expression to run the program immediately.

16.3.3 Scheduling Removal of Old Backup Files

To schedule removal of old backup files that are create as a result of the Backup database job while retaining only specific number of files in Advanced Authentication server volume, perform the following:

  1. Click Backup/Restore > Schedule Backup.

  2. Set the configurations to schedule the back up export in Backup schedule.

  3. Set the cron expression for the schedule in the first column.

  4. Select Remove old *.cpt files from the drop down to remove old cpt files from the Advanced Authentication data volume.

  5. Specify the number of old backup files that must be retained in Keep last.

    For example, to remove the old backup files but retain the latest fifteen backup files in your server volume, set Keep last to 15.

  6. Click Save.

16.3.4 Scheduling Synchronization of Backups to a SFTP Server

To synchronize the backed up log files from a container to an SFTP server perform the following:

  1. Run the following command to copy the mirror.sh file from docker to host server:

    docker cp aaf_aucore_1:/opt/AuCore/data/celery_long/mirror.sh /tmp

  2. Add the following parameters in the mirror.sh file to skip verification of SSL certificate:

    set ssl:verify-certificate no

    set ftp:ssl-allow true

    set ftp:ssl-force true

    set ftp:ssl-protect-data true

    set ftp:ssl-protect-list true

    NOTE:When you reboot the appliance, the data available in the mirror.sh file will be lost.

  3. Save the changes.

  4. Run the following command to copy file to docker container:

    docker cp mirror.sh aaf_aucore_1:/opt/AuCore/data/celery_long/

  5. Run the following commands to provide executable rights of the mirror.sh file for users and group:

    docker exec -ti aaf_aucore_1 bash

    chmod u+x data/celery_long/mirror.sh

    chmod g+x data/celery_long/mirror.sh