Table of Contents
Advertisement
Release 7.0.0 3DB 19286 ACAA Issue 01
WebEML User Manual
25 MIB database management (backup and
25.1 Purpose
This chapter provides procedures to perform MIB Database Management (backup
and restore) on the 9500 MPR. A MIB database restore should be performed for
catastrophic recovery ONLY.
25.2 Overview
Caution: All traffic will be interrupted during the activate database phase.
The backup operation provides the ability to save a copy of NE configurations
parameters stored on the flash memory on the NE Core cards.
Database backup file name supports a user, free-form string name, up to twenty-five
characters. Only alphanumeric characters, the hyphen "-" character, and the
underscore "_" character are supported. The file name is prefixed with the software
version number as follows: "V<release number 01-99><intermediate revision 00-
99><maintenance revision 00-99> for example, "V020200". The file name also
includes the ".bar" extension. The maximum total backup file name length is thirty-six
characters: Version (7 characters) User free-form string name (25 characters) .bar
extension (4 characters), for example,"V020200_Chicago-Pearl_2010-04-30.bar" is
an example of the longest backup file name supported.
To aid in tracking database backup files, it is recommended to use the NE Name and
Date in the backup file name (for example, V020200_Chicago-Pearl_2010-04-
30.bar) or follow local practices and procedures to construct backup file names.
The restore operation provides the ability to restore a previously saved copy of NE
configurations parameters to the flash memory on the NE Core cards.
On NE configured with Core protection, the spare Core card must be either disabled
or physically unseated from the shelf, prior to Database Restore.
restore)
MIB database management (backup and
restore)
201
Advertisement
Table of Contents
