User's Guide

Table Of Contents
NEVER direct a backup from the primary server to /usr/local/smx/backups on a standby
server. This will prevent synchronization from working properly.
NEVER back up to the desktop from the standby server, because that process overwrites the
existing file in /usr/local/smx/backups.
As the second part of synchronization, the standby server runs a restore to itself using the file found
in its own /usr/local/smx/backups directory. This should be the only file ever copied over
from the primary server.
Synchronization Rules
You should only back up the primary server. NEVER schedule or perform a backup on the standby
server.
Synchronization should only be done from the standby server. NEVER schedule or perform a
synchronization on the primary server.
Always schedule or perform a backup on the primary server one hour before scheduling a
synchronization or performing an on-demand synchronization on the standby server. Backups
require more time as the primary server continues collecting configuration data.
NEVER schedule backups at the same time as a synchronization. This will NEVER work.
Scheduled jobs should be included when backing up an appliance before synchronization. This will
save you valuable time when restoring the backup on a new appliance. Unless you have backed up
your scheduled jobs, you will have to recreate them on the new appliance.
Automatic Synchronization
As with manual synchronization, use the Redundant Appliance Synchronization screen to synchronize
the configurations from your primary server to the secondary server.
Figure 120: Redundant Appliance Synchronization Screen
Use the left pane of this screen to provide the details for the primary Extreme AirDefense appliance.
The right pane of this screen enables you to automatically synchronize configurations from the primary
server on a pre defined schedule.
Synchronization Rules
Configuration
294 Extreme AirDefense User Guide for version 10.5.