Chapter 2 Pre-upgrade activities 13

Perform a backup of your BCM 3.6/3.7 system: Current settings will be lost if there is a system failure during the upgrade procedure. Use the Unified Manager backup and restore utility (BRU) to back up all the data on the BCM and store it on a remote host before proceeding with the upgrade procedure.

Note: If you are using Network Configuration Manager (NCM) to manage your BCM networks, you can use NCM to automatically obtain and store the backup images of BCM 3.6/3.7 systems before performing the upgrade to BCM 4.0. You can invoke the BCM 3.6/3.7 backup in accordance with a centralized schedule. You can also import the BCM 3.6/3.7 configurations into NCM, and use the NCM excel report capability through Export to TFTP to create an excel programming record of all the BCM Unified Manager information that NCM is able to manage.

Ensure that you have a complete current backup file stored in a location other than on the BCM system or the computer you are using to run the backup. This provides you with a backup of your most recent settings in the event of a system failure during the upgrade.

Warning: After the upgrade is complete, do not restore your BCM 4.0 system using the BCM 3.6/3.7 backup. The systems are not compatible and the restore will not function properly. Use the BCM 3.6/3.7 backup only if the upgrade fails and your system is no longer functional. A backup can only be restored to a system running the same software version from which the backup was created.

Note the BCM IP address: Note the IP address of the BCM system that you want to upgrade. You are required to enter this information in the Upgrade Wizard when prompted to connect to the BCM system.

Ensure your BCM 3.6/3.7 system hard disk is correctly partitioned: Your BCM system hard disk must be partitioned as shown in Table 2. If the hard disk is not correctly partitioned, the upgrade does not proceed and your system returns to the pre-upgrade state.

Use BIT to correct any hard disk partition issues (see “Upgrading to BCM 4.0 after a failed pre-check or upgrade” on page 40).

Table 2 BCM200/400 and BCM1000 system hard disk partition information

Drive

Label

Type

Size (bytes)

 

 

 

 

C:

WINNT

NTFS

exactly 2623863808

 

 

 

 

D:

DATA

NTFS

exactly 9911427072

 

 

 

 

E:

LOGS

NTFS

exactly 2105638912

 

 

 

 

F:

NNACTIVE (or NNINACTIVE

NTFS

exactly 2105638912

 

 

 

 

G:

NNINACTIVE (or NNACTIVE)

NTFS

exactly 2105638912

 

 

 

 

I:

MAINTOS

NTFS

exactly 1052835328

 

 

 

 

Note 1: Drives F and G cannot have the same label. One must be NNACTIVE and the other NNINACTIVE.

Note 2: For BCM1000 systems, the MAINTOS partition can be on drive I or H.

Note 3: For BCM1000 systems, the size of drives C and D must be greater than or equal to the values provided and drive I (or H) must be greater than or equal to 1052834816 bytes.

Upgrade Guide

Page 13
Image 13
Nortel Networks n0060597 manual Drive Label Type Size bytes