User guide

File Administration Backup and Restore

AlliedView NMS Administration Guide

3.4.3 Configuring Backup Parameters for AlliedView NMS

A backup of the NMS configuration can be performed on demand or on a schedule. When the files are being backed up on

demand, the console window shows the path where the files are being copied. When the files are being backed up on a

schedule, the Backup Destination field (seen in Figure 3-21) shows this path.

The path used is controlled by the file:

<NMS_Home>/conf/AT_NmsBackupFiles.conf

This file includes the following parameters:

• ATINMS_BACKUP_DEST

This where the NMS backups are stored. The default is <NMS_Home>/backup

• ATIDEVICE_BACKUP_DEST

This is where device backups are stored. The default is <NMS_Home>/backup

• ATIDEVICE_BACKUP_LIMIT

Refer to 3.4.5.

Note: In most cases, the user should change the directory path to one where you normally send backup files. The server should have

sufficient space and be reliable for backup purposes.

Note: Changes made to

AT_NmsBackupFiles.conf are enabled as soon as the file is changed, so a server restart is not needed.

3.4.4 Restore the AlliedView NMS (GUI Screens)

There is a set of GUI screens to perform a restore.

Caution: A restore requires the server to be shut down and then restarted. If this feature is used while the AlliedView NMS is running,

there is an error message. Moreover, any data changed since the last backup will be lost.

Caution: A restore should only be done on the same software version in which the backup was performed. If the software versions do

not match, the following appears when starting the restore.

FIGURE 3-22 Warning for Software Version Mismatch for a Restore

1. Shut down the server (using the Start -> Programs menu path).

2. Start the tool:

For Windows, from the bin/backup directory, select

AT_NMSRestore.bat.

On Solaris, from the bin/backup directory, execute

./AT_NMSRestore.sh

Refer to the following figure for the Windows folder.