User's Guide

Table Of Contents
How Backups Work
All backups, scheduled or on-demand, create a backup file in /usr/local/smx/backups.
Backups include more than the SQL database. Many configuration files (XML files) scattered
throughout ADSP are also included. These files are included in the zip archive along with the
database tables.
If an on-demand backup is done to the desktop, the system performs a regular backup to /usr/
local/smx/backups first and then copies that file to the desktop.
If a scheduled backup is done to a remote device via SCP or FTP, the system performs a backup
to /usr/local/smx/backups first and then copies that file to the remote system.
Only the most current backup is kept. Previous backups are deleted from the /usr/local/smx/
backups folder.
The /usr/local/smx/backups directory is root protected. Users cannot delete the backup file.
However, they can copy it to another location.
The format of a backup file looks like:
Backup_8.1.0-10_ECRT236.am.mot.com_20101018000011.zip.enc. The name always
includes the release, the server name, and the year-month-day-hour-minute-second. The enc at the
end of the name indicates that the file is encrypted. Encrypted files can be emailed securely.
Backup Recommendations
As a minimum, schedule a daily backup internal during non-peak hours.
If there is an external server to backup to, schedule an external backup at least once a week and NOT
at the same time as a local backup.
Legacy Content
Appliance Management
Extreme AirDefense User Guide for version 10.5. 1221