Restoring Logs And Configuration Data; Managing Device Schemas Through The Juniper Update Mechanism - Juniper NETWORK AND SECURITY MANAGER 2010.2 - ADMINISTRATION GUIDE REV1 Administration Manual

Network and Security Manager Administration Guide

Restoring Logs and Configuration Data

Managing Device Schemas Through the Juniper Update Mechanism

312
For a large amount of log data, using tar may not be appropriate. We recommend
using Secure Copy (scp) or File Transfer Protocol (FTP) to backup the Device Server
data.
Example using scp:
scp -r <local directory> usr@host:<remote-directory>
Example using FTP:
ftp <host name>
bi
hash
lcd <local directory>
prompt
mput
Start GUI Server and Device Server processes.
5.
These instructions apply only to systems where the var directory links point to a true
location outside the prescribed locations (
). We recommend that you do not set these links to point to
/usr/netscreen/DevSvr
locations that are inside
/usr/netscreen/GuiSvr
complicate upgrades to NSM and requires special precautions during backup and restore
procedures.
To restore log and configuration data:
Stop Device Server and GUI Server processes.
1.
Use the mv command to transfer data from the var directories to a safe location.
2.
This precaution clears the var directory for restoration of the backups.
Untar your backups into both of the locations described above.
3.
Start GUI Server and the Device Server processes.
4.
You can download and activate XML-based device schemas without upgrading NSM.
This feature applies only to devices whose schemas are defined using XML:
Secure Access devices
Infranet Controller devices
JUNOS devices
This mechanism does not apply to ScreenOS or IDP devices.
The latest device schema is placed by Juniper Networks on the Juniper Update Server,
which is a publicly available server. From there, schema upgrade is a two-stage process:
/usr/netscreen/GuiSvr or
or
/usr/netscreen/DevSvr
Copyright © 2010, Juniper Networks, Inc.
; doing so can