|
|
 |
Caution You must back up your data before beginning the upgrade. If you do not back up your data, it will be lost during the upgrade. |
This chapter covers the following topics:
Use the instructions in this section to back up your current software configuration. If you have a simplex host, you back up the data on your server after shutting it down. If you have a high-availability configuration, bring the standby host down and back up the data on the standby host first, so the active host can still process calls while the standby is being upgraded. This minimizes downtime.
This process takes approximately 20 minutes.
|
Caution Do not back up data to an active remote SC host that is processing calls. For example, do not back up your SC host machine to the second host in a high-availability configuration. This can severely impact or shut down call processing. |
 |
Tips Depending on your level of UNIX expertise, you might need to have your UNIX system administrator available for assistance during the upgrade. These instructions might not be sufficient or accurate for large, complex networks. |
If you have a high-availability configuration, first determine which host is running as active. In a high-availability configuration, the active system is the one running the process manager (procM) and the failover daemon (foverd). The standby host is running the file replication daemon (frepld) as well as the failover daemon. To determine which host is running as active, log in to each machine and use the rtrv-ne MML command. The display shows whether the machine is active or standby.
Use these instructions to back up your data to tape. You will restore the data before installing the SC software.
va-blade console login: root Password: Mar 17 10:21:34 va-blade login: ROOT LOGIN /dev/console Last login: Thu Mar 16 10:16:34 on console Sun Microsystems Inc. SunOS 5.6 Generic August 1997
Step 2 Insert a tape into your tape drive.
Step 3 Stop the SC software by entering the following command:
/etc/init.d/transpath stop
 |
Note In a simplex configuration, call processing will stop now. The host will not be able to process calls until you restart the software after the upgrade. See the "Restarting and Verifying the Newly Upgraded Host" section. In a high-availability configuration, perform these steps on the standby host first. Unless the active host goes down, call processing will not stop. |
Step 4 Change to the base directory. For example:
# cd /
Step 5 Backup the entire /opt/TransPath directory, including subdirectories, and the password and group files by entering the following command:
tar cvf /dev/rmt/0h /opt/TransPath /etc/passwd /etc/group
For example:
# tar cvf /dev/rmt/0h /opt/TransPath /etc/passwd /etc/group a /opt/TransPath/ OK a /opt/TransPath/bin/ OK a /opt/TransPath/bin/expect 761K . . .
Step 6 When the backup has finished, remove the tape, engage the write protect tab, label the tape Full SC Backup, and record the machine name, time, and date.
This completes backing up your SC host data to tape. If you need to upgrade hardware on the host, such as hard drives or processors, proceed to "Upgrading Hardware." If you do not need to upgrade hardware, proceed to "Installing and Configuring the Cisco SLT."
Use these instructions to back up your data to a remote machine using your IP network.
|
Caution Do not back up your data to another SC host machine. Only use a spare machine that is not processing calls. |
|
Note This procedure backs ups everything in the SC software base directory to an NFS mountable directory on a remote machine. The remote machine must be set up with an NFS mountable directory that is writable by machine being backed up. The NFS set up of the remote machine is beyond the scope of this document; contact your UNIX system administrator for more information. |
va-blade console login: root Password: Mar 17 10:21:34 va-blade login: ROOT LOGIN /dev/console Last login: Thu Mar 16 10:16:34 on console Sun Microsystems Inc. SunOS 5.6 Generic August 1997
Step 2 Stop the SC software by entering the following command:
/etc/init.d/transpath stop
|
Note In a simplex configuration, call processing will stop now. The host will not be able to process calls until you restart the software after the upgrade. See the "Restarting and Verifying the Newly Upgraded Host" section. In a high-availability configuration, perform these steps on the standby host first. Unless the active host goes down, call processing will not stop. |
Step 3 Verify the machine can connect to the remote machine and host name resolution is enabled. The hosts file in the /etc directory of each machine must contain the IP address and name of the other machine. To verify, enter the ping hostname command. For example:
va-costello:2> ping va-panthers va-panthers.cisco.com is alive
Step 4 Mount the directory from the remote NFS server at /mnt on the local machine by entering the following command:
mount -F nfs -o retry=3 hostname:directory /mnt
For example:
# mount -F nfs -o retry=3 va-panthers:/backup /mnt
where directory is a directory that contains enough free space to store the files.
|
Note You can also use an IP address for the hostname if DNS is not enabled. |
Step 5 Verify that you have enough disk space on the remote machine to back up the files. The SC host can contain very large log files that may be close to 1 gigabyte in size. The procedures here assume that you are backing up to the root directory, which normally holds about 600 megabytes. To verify the size of the files being backed up, change to the /opt/TransPath directory and enter du -sk to see file size (in megabytes). For example:
va-stars:1> cd / va-stars:2> du -sk /opt/TransPath /etc/passwd /etc/group 729070 /opt/TransPath 2 /etc/group 11 /etc/passwd
Step 6 Enter df -k to verify you have enough free space in the backup directory to store the files. For example, the space in the /backup directory in Step 4 should be more than the 729070 megabytes shown in Step 5. You must compress or delete files if you do not have enough space.
Step 7 Backup the system to a file in the /mnt directory. Cisco recommends using a filename containing the hostname of the machine and the date and time with a .tar extension; for example, mgca20000101120000.tar. Use the following command:
tar cvf /mnt/filename.tar .
For example:
# tar cvf /mnt/mgca20000101120000.tar /opt/TransPath /etc/passwd /etc/group a ./ 0 tape blocks a ./var/ 0 tape blocks a ./var/log/ 0 tape blocks
 |
TimeSaver Because installing Sun Solaris 2.6 deletes existing group and password files, you should back up these files so you do not have to add your users again. |
Step 8 Unmount the remote directory using the following command:
# umount /mnt
This completes backing up your SC host data to a remote machine.If you need to upgrade hardware on the host, such as hard drives or processors, proceed to "Upgrading Hardware." If you do not need to upgrade hardware, proceed to "Installing and Configuring the Cisco SLT."
|
Caution Do not restore your data until after you install the new version of the Solaris operating system. Instructions for installing the new version of Solaris are presented in "Installing the Sun Solaris 2.6 Operating System." |
Use the procedures in these sections to restore the SC data you previously backed up. If you backed up your data to tape, see the "Restoring Your Data from a Local Tape Drive" section. If you backed up your data to a remote machine using the IP network, see the "Restoring Your Data from a Remote Machine" section.
This procedure restores everything on a tape installed in the local tape drive to the SC software base directory. This procedure assumes the operating system has just been installed and no SC software has been loaded. This procedure returns the etc and dialPlan subdirectories from a tape in the local tape drive to the /opt/TransPath directory. When the new SC software is later installed, it detects these files and uses them to migrate to the new configuration.
va-blade console login: root Password: Mar 17 10:21:34 va-blade login: ROOT LOGIN /dev/console Last login: Thu Mar 16 10:16:34 on console Sun Microsystems Inc. SunOS 5.6 Generic August 1997 # mkdir -p /opt/TransPath
Step 2 Change to the / directory. For example:
# cd /
Step 3 Restore the files from tape using the command shown in this example:
# tar xvf /dev/rmt/0h x ., 0 bytes, 0 tape blocks x ./etc, 0 bytes, 0 tape blocks x /opt/TransPath 0 tape blocks x /opt/TransPath/bin 0 tape blocks x /opt/TransPath/bin/expect 1522 tape blocks . . .
Step 4 When the restore has finished, remove the tape from the tape drive.
This procedure restore files from the etc and dialPlan subdirectories to the /opt/TransPath directory from a file on an NFS mountable directory on remote machine. The remote machine must be set up with an NFS mountable directory that is writable by machine being backed up. The NFS set up of the remote machine is beyond the scope of this procedure. When the new SC software is later installed, it detects these files and uses them to migrate to the new configuration.
va-blade console login: root Password: Mar 17 10:21:34 va-blade login: ROOT LOGIN /dev/console Last login: Thu Mar 16 10:16:34 on console Sun Microsystems Inc. SunOS 5.6 Generic August 1997 # mkdir -p /opt/TransPath
Step 2 Change to the / directory. For example:
# cd /
Mount the directory from the remote NFS server at /mnt on the local machine using the following command:
# mount -F nfs -o retry=3 hostname:directory /mnt
|
Tips For the hostname and directory variables, use the names you provided in the "Backing Up Your Data to a Remote Machine" section. |
For example:
# mount -F nfs -o retry=3 va-panthers:/backup /mnt
Step 3 Obtain a directory listing of the files in the directory using the following command:
ls -1 /mnt/*.tar
Step 4 Restore from the selected file using the following command:
tar xvf /mnt/filename.tar
For example:
# tar xvf /mnt/mgca20000101120000.tar x ., 0 bytes, 0 tape blocks x ./etc, 0 bytes, 0 tape blocks x /opt/TransPath 0 tape blocks x /opt/TransPath/bin 0 tape blocks x /opt/TransPath/bin/expect 1522 tape blocks . . .
Step 5 Unmount the remote directory using the following command:
umount /mnt
This completes restoring your data. Proceed to "Installing and Configuring the SC Software."
Posted: Tue Aug 8 05:27:19 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.