Scheduled External Log and Support-Info Backup

You can configure the SBC to automatically back up a package of its current log files and the latest support-info command output from the “/opt/archives/logs” folder to an external SFTP server. This feature enhances system reliability by maintaining an off-system copy of your system's state.

You configure this log file and support-info backup using the same procedures as the config-backup function. To accommodate this, the schedule-backup element in the system-config includes the logs-backup sub-element.

Note:

Information from the dump-np-stats command are excluded from this backup.

The majority of the configuration parameters in logs-backup are the same as those in the config-backup sub-element. Differences that apply to logs-backup include:

  • You can configure a support-info-interval parameter to specify the number of hours between each stored support-info output. The default value is 3, and the range is from 1 (minimum) to 48 (maximum) hours.
  • You can configure a all-logs-interval parameter to specify the number of hours after which the system creates a log package. The default value is 12, and the range is from 1 (minimum) to 48 (maximum) hours.
  • You can configure a include-all-logs parameter to specify that the system includes all logs in each log package in addition to the support-info output. When disabled, the system only backs up the support-info output.
  • You can configure a local-backups-count parameter to specify the number of packaged show support-info files to be maintained for rotation. The default value is 5, and the range is from 1 (minimum) to 24 (maximum) times.
  • You can configure a local-logs-backup-count parameter to specify the number of packaged “all logs” files to be maintained for rotation. The default value is 5, and the range is from 1 (minimum) to 12 (maximum).

The majority of operational behaviors for this logs-backup feature are the same as those in the config-backup feature:

  • Target file naming function is basically the same. The target file name has to differ, using the syntax <SBCNODENAME>-logs-YYYYMMDDHHMMSS.
  • If you configure more than one push receiver, the SBC pushes the configuration file to all of them sequentially.
  • The SBC can retry pushing the backup file if it fails.
  • The SBC stops attempting to push the backup file when it reaches your configured value for maximum number of retry attempts.
  • The SBC generates an alarm and an SNMP trap if it fails to push the backup file to a configured push receiver.

Alarm and Associated Trap

The SBC raises an alarm and issues a simultaneous SNMP trap to notify you each time access to a push-receiver fails. You can manually clear the alarm using the clear-alarm command. There is no associated clear-trap.

The alarm is named APP_ALARM_SCHBKP_LOGS_PUSH_FAIL. The alarm uses the standard format and includes:

The name of the trap is apPushReceiverFailureTrap. You can access it from the apSip traps using the OID 1.3.6.1.4.1.9148.3.16.2.2.8.0.1. This trap is reserved for configuration backup push receiver failures only.

In addition, you can review the log.schbkpd file, which is available individually and within the package-logfiles package, for operational analysis and troubleshooting this feature.