Chapter 5: Backups/Profiles - Tavve zoneranger User Manual

Chapter 5: Backups/Profiles

ZoneRanger provides two mechanisms for managing sets of configuration information: backups and
profiles. Backups and profiles are similar in that in each case, a set of configuration information for a
ZoneRanger is gathered and saved in a file that can be restored to the same ZoneRanger, or applied to a
different ZoneRanger. The primary difference between backups and profiles is that backups contain the
content of the ZoneRanger's database of discovered devices, as well as any polling/management
configuration associated with those devices that is also stored in the database, while profiles do not.
ZoneRanger Profiles
Profiles are intended to be used as a form of configuration template, so that a ZoneRanger configuration
can be developed, captured, and easily replicated across a set of ZoneRangers that may be installed in
different network regions, and be managing different sets of devices. Backups, on the other hand, can be
used to roll back a given ZoneRanger's configuration to a previous state, to auto-configure a new
ZoneRanger that is being added to an existing pool, or to replace an existing ZoneRanger that may have
failed or is being redeployed to another location.
Profiles are created (a.k.a. saved) using the ZoneRanger web interface, from the Administration >
Profiles page. The user has two options with regards to the location(s) where the profile file will be
stored:
•
The profile can be saved on the ZoneRanger only.
•
The profile can be saved on the ZoneRanger, and also copied to a joined Ranger Gateway.
When loading (i.e. applying) a profile, the user can choose to load any profile stored on that
ZoneRanger, or stored on any joined Ranger Gateway. Note that a profile can only be loaded on a
ZoneRanger that is at the same software version as the ZoneRanger that created the profile. The
ZoneRanger web interface can also be used to delete profiles from the ZoneRanger or any joined Ranger
Gateway.
ZoneRanger Backups
Backups can be created using the ZoneRanger web interface, from the Administration >
Backup/Restore page, or by executing the Ranger Gateway backup command. When creating a
backup from the web interface, the user has two options with regards to the location(s) where the backup
file will be stored:
•
The backup can be saved on the ZoneRanger only.
•
The backup can be saved on the ZoneRanger, and also copied to a joined Ranger Gateway.
When creating a backup using the Ranger Gateway backup command, the backup will always be saved
on the ZoneRanger, and copied to the Ranger Gateway where the command was executed. Note that the
command is primarily intended to allow users to perform automated periodic backups. For
backup
example, if the Ranger Gateway is installed on a Solaris or Linux operating system, a cron job can be
configured to run this command at scheduled times. In a similar manner, the Scheduled Tasks
mechanism can be used to automate backups on a Windows operating systems. Backups are stored in
the Ranger Gateway store/zr/backup directory.
Backups can only be restored from the ZoneRanger web interface. When restoring from a backup, the
user can choose any backup file stored on that ZoneRanger, or stored on any joined Ranger Gateway.
Note that a backup file can only be loaded on a ZoneRanger that is at the same software version, model
number (e.g. ZR-50, ZR-200, ZR-500, ZR-SPX, or ZR-MSP) and hardware version as the ZoneRanger
that created the backup file. The ZoneRanger web interface can also be used to delete backup files from
the ZoneRanger or any joined Ranger Gateway.
ZoneRanger 5.5 User's Guide 20