Lucent Technologies CentreVu Call Management System Release 3 Version 8 Guide

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring35
Step 8: Install the 
CMS software
2
Now you will complete the installation of the usual software by installing 
CMS. In general, the steps are as listed below. Detailed installation 
instructions can be found in 
CentreVu CMS R3V8 Software Installation 
and Setup 
(585-210-941).
The steps to be completed are these:
lInstall CMS software
lInstall CMS patches (if needed)
lInstall CMS Supplemental Services software
lSet up CMS
lInstall Open Database Connectivity (ODBC) software (optional)
lSet up the remote console
lAdminister the NTS (if using NTS ports)
Step 9: Create an 
alternate boot 
device
2
1. Enter the following command:
where 
newbootdev is the device name of the disk chosen as boot 
disk 2 (as c0t1d0s0, for example). You partitioned that disk earlier in 
the installation procedure.
The system responds (for example):
2. Record the device definition (the part after /devices
 and 
before:a,raw). 
For the example above, you would record the part 
beginning /sbus@3,0 
and ending sd@1,0
.
3. Reboot the system by entering the following command:
The system displays the ok 
prompt.
4. Create a device alias for the new boot device by entering the 
following command (for example):
Replace 
 with what you recorded in item 2. For the 
example shown, you would replace 
 with the following:
/sbus@3,0/SUNW,fas@3,8800000/sd@2,0 # ls -l /dev/rdsk/
newbootdev
lrwxrwxrwx   1 root     root          83 Jun 18 15:23 
/dev/rdsk/c0t1d0s0 -> ../../devices/sbus@3,0/SUNW,
fas@3,8800000/sd@1,0:a,raw
# /usr/sbin/shutdown -y -i0 -g0
ok nvalias bootdevice2
 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring36
5. Enter the following command:
6. Check the output for a line like this:
bootdevice2 <
device definition>
where, again,  is the string recorded in item 2.
7. Verify that the system boots normally off the alternate boot device, 
and log in as the root user:
8. Reboot with a shutdown
 command and again log in as 
root:
9. Verify that everything is normal.
10. Enter the following command:
The system starts the editor and loads the cron
 file. 
11. Add the following line to the end of the file:
15 0 * * * /olds/chkDisks > /dev/null 2>&1
12. Save the file and exit the editor.ok devalias
ok boot bootdevice2
.
.
.
 console login: root
Password:

.
.
.
#
# /usr/sbin/shutdown -y -g0 -i6
.
.
.
 console login: root
Password:

.
.
.
#
# crontab -e 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring37
13. Enter the following command:
14. Do a CMSADM backup. For instructions, see the 
CentreVu 
CentreVu CMS R3V8 Administration 
(585-210-910) document or the 
maintenance and troubleshooting document for your hardware 
platform.
When the CMSADM backup is finished, the factory installation 
procedure for disk mirroring is complete.# chmod +x /olds/chkDisks 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring38 
						

							  Maintaining Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Using the alternate boot device39
3
Maintaining Mirrored Systems3
This chapter contains procedures you are likely to need to 
maintain a disk-mirrored system, including replacing disk 
drives, recovering from disk failures, and using the olds scripts.
Using the alternate boot device3
When you set up your mirrored system, you created an alternate boot 
device named 
bootdevice2. 
The alternate boot device is a fail-safe device. If for some reason you are 
unable to boot from the primary boot disk—a corrupted boot disk, for 
example—you can tell the system to boot from the alternate device until 
further notice.
You do that by entering one of the following commands, depending upon 
whether you are at the boot prompt or in root:
_________________________________________________________________
ok setenv boot-device bootdevice2
# eeprom boot-device=bootdevice2
_________________________________________________________________
To reset the boot device to the primary disk, enter one of the following 
commands, again depending upon whether you are at the boot prompt or 
in root:
_________________________________________________________________
ok setenv boot-device disk
# eeprom boot-device=disk
_________________________________________________________________ 
						

							  Maintaining Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Maintaining the chkDisks crontab40
Maintaining the chkDisks crontab3
The chkDisks crontab runs each night and checks to see whether any 
potential or actual drive problems have been logged. The results of the 
search are logged to 
/olds/elog and mailed to the root user. This section 
shows how to start and stop chkDisks, and how to verify that it will run.
Activating 
chkDisks
3
Activate chkDisks by doing the following steps:
1. Enter the command:# crontab -e
The system starts the editor and loads the cron
 file. 
2. Find the line for 
/olds/chkDisks. If it is commented out, uncomment it 
by deleting the pound sign at the beginning of the line. If there is no 
line for 
/olds/chkDisks, add the following line to the end of the file:
15 0 * * * /olds/chkDisks > /dev/null 2>&1
Verifying chkDisks3To verify that cron
 is running, enter the following command:
Check the listing to see that there is an entry for chkDisks.
Changing the 
scheduled run time
3
The /olds/chkDisks line in the cron file is generally in the following format:
15 0 * * * /olds/chkDisks > /dev/null 2>&1
This line tells the system to run chkDisks every day at 15 minutes past 
hour zero, or 12:15 AM. You can change that schedule by changing the 
first five fields as necessary. The fields, in order of appearance, are: 
minute, hour, day of the month, month of the year, and day of the week. 
An asterisk means “all legal values.” For more information, see the 
manual (man) page for the crontab command.
Canceling 
chkDisks
3
To stop cron from running, enter the following command:
With the file loaded in the editor, comment out the entry for chkDisks and 
write and quit the file.# crontab -l
# crontab -e 
						

							  Maintaining Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Doing a CMSADM backup on a mirrored system41
Doing a CMSADM backup on a mirrored system3
This section describes how to perform a traditional CMSADM backup on 
a mirrored system. 
Mirroring is intended as a way to minimize data loss should a system crash 
occur, not as a way to avoid backing up data. Mirrored systems must be backed 
up just as often as unmirrored systems.
Step 1: Print the 
vfstab file3
Print out the contents of the vfstab file before beginning the backup. You 
will need the information in that file to restore files from the backup tape.
To print the 
vfstab file, do the following:
1. Enter the following command:
2. Retrieve the printout and save it. You will need it again when the 
backup finishes.
Step 2: Run the 
backup
3
1. At the system console, log in as root. 
2. Verify that the computer is in a 
Solaris multi-user state (a run level of 
2
 or 3
) by entering a who -r
 command. The system responds by 
listing the run level and date. For example:
If the system is in some other run level, reboot and log in again as 
the root user: 
NOTE:
# lp /etc/vfstab
# who -r
. run-level 3 Feb 2 16:52 3 O S
#
# /usr/sbin/shutdown -y -g0 -i6
...
 login: root
password:

...
# 
						

							  Maintaining Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Doing a CMSADM backup on a mirrored system42
3. Display the CentreVu CMS Administration menu by entering a 
cmsadm 
command. For example:
4. Enter the number of the backup 
option. The system prompts for 
the tape drive.
5. Enter the appropriate option number. The system begins calculating 
the approximate number of tapes required and informs you of its 
calculation. For example:
6. Insert the tape, wait for it to rewind and reposition, and press Enter.
The backup begins.
During the backup, you may receive a prompt about CMS being on 
or prompts to insert more tapes. Respond to each prompt as 
appropriate, and then press Enter.
When the backup completes, it will be verified. If you used more 
than one tape, you will have to reinsert each tape.
Any time you need to insert a tape, allow it to rewind and reposition 
before you press Enter.
Step 3: Label and 
store the tapes
3
After the tape verification, the system prompts you to label the tapes and 
then returns you to the system prompt:
Label the tapes as instructed. Bundle them with the 
vfstab printout and 
put them away in a safe place.# cmsadm
Lucent Technologies CentreVu(R) Call Management 
System Administration Menu
Select a command from the list below.
1) acd_create Define a new ACD 
....
The backup will need approximately 2 tapes.
You will be prompted for additional tapes.
Be sure to number the cartridge tapes 
consecutively in the order they will be 
inserted.
Please insert the first cartridge tape into 
/dev/rmt/

Press ENTER when ready:
Please label the backup tape(s) with the date and 
the current CMS version (
).
# 
						

							  Maintaining Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Restoring from a CMSADM Backup43
Restoring from a CMSADM Backup3
This section contains the procedure for restoring /cms data files from a 
traditional CMSADM backup tape.
You may want to perform a CMSADM restore when, for example, your file 
systems are still intact, but some data has been corrupted.
If your CMS is running on a 
Sun Enterprise 3500, and you have had a 
crashed or corrupted disk, check the 
/kernel/drv/st.conf file before you 
begin the restore. Make certain the file contains the following entry:
# Begin CMS tape configuration list.
tape-config-list=
EXABYTE EXB-8900, Mammoth EXB-8900 8mm Helical
Scan, EXB-8900,
TANDBERG TDC 4200, Tandberg 2.5 Gig QIC, TAND-25G-
FIXED,
TANDBERG SLR5, Tandberg 8 Gig QIC, TAND-8G-FIXED;
EXB-8900 = 1,0x29,0,0xce39,4,0x7f,0x7f,0x7f,0x7f,0;
TAND-25G-FIXED = 1,0x37,512,0x867a,1,0x00,0;
TAND-8G-FIXED =
1,0x37,512,0x963a,4,0xA0,0xD0,0xD0,0xD0,3;
# End CMS Tape configuration list.
If the file does not contain the entry, add it. The 3500’s Mammoth 8mm 
tape drive will not operate if the entry is absent.
To restore a CMSADM backup, do these steps:
1. Obtain the latest CMSADM backup tape.
2. Load the backup tape into the tape drive.
3. Enter the following command:
where 
 is one of the following:
/dev/rmt/0
The internal, noncompressing tape drive (14-GB, 
8-mm drive) with the lowest target address.
/dev/rmt/1
The external, noncompressing tape drive (QIC-150 
or 5-GB, 8-mm drive) with the second lowest target 
address.
/dev/rmt/0c
The internal, compression-capable tape drive 
(usually a 14-GB or 40-GB) with the lowest target 
address.
/dev/rmt/1c
The external, compression-capable tape drive 
(either a QIC 2.5-GB or a 14-GB tape drive) with 
the second lowest target address. # cpio -icmudv -C 10240 -I 
 
						

							  Maintaining Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Restoring from a CMSADM Backup44
You may get error messages concerning the /home directory. These errors 
display when the directory is already present. Ignore them.
4. Restore any 
CentreVu CMS maintenance backups dated after the 
latest CDMADM backup. See the 
CentreVu CMS R3V8 
Administration 
(585-210-941) document for details on restoring a 
maintenance backup.
NOTE: