You may need to do something like this:
1. Stop all tape operations and make sure
all tapes are rewound and unloaded.
(Shutdown NetBackup and media manager
daemons) use:
bpps -a (to check processes)
bp.kill_all
then kill or kill -9 if processes are left
2. Modify the /kernel/drv/st.conf file
so that it has the correct entries in it.
3. Do a "modinfo | grep tape" to
make sure the st driver is not loaded. If the driver does not unload, there
will be an entry like this:
"86 61290000 dfe9 33 1 st (SCSI tape
Driver 1.173)" in the output
If that is the case, then the module may
have to be specified. To specify the module, run modunload -i <module_id>
or to match the above output, run "modunload -i 86"
4. Once the st driver module is properly
unloaded, run rm /dev/rmt/*
This will delete all of the symbolic links
in the /dev/rmt directory.
5. Next, run the "drvconfig -i
st" command.
This will re-install the st driver with
the new /kernel/drv/st.conf settings.
7. Then, run the following command:
/usr/sbin/tapes, this should make the links in /dev/rmt
Cheers,
Dom
From:
DULLAART Rob ONL [mailto:rob.dullaart AT orange-ftgroup DOT com]
Sent: Friday, 22 June 2007 8:05 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Change of
WWN-numbers
Hi,
This week we enabled the
WWN-feature on our L700 tape-robot. This means that all the devices
(tape-drives, robotic arm) got a new WWN-number. The devices own WWN-number is
not longer advertised now the robot itself advertises a WWN-number for the
device. The benefit of this is that in case of a hardware-replacement nothing
has to be changed. Not on the SAN and not on the OS and not in Netbackup.
This week, after we
enabled the feature, we changed the SAN, then we started to connect the
tape-drives at OS-level.
We have several Solaris 9
mediaservers. On all servers we could connect the drives without a reboot with
hthese commands
-
cfgadm -al (to show what
is connected)
-
cfgadm -c configure cX
(to configure controller X)
-
devfsadm -C -c tape (to
get device files for the tape-drives with the new WWN)
After that we could
configure them in Netbackup
This went fine for all
the mediaserver without a reboot. Except one and this server is our main
production system and cannot easily be rebooted.
We tried a lot of
commands we found with google. But the output of cfgadm –al keeps showing
the old WWN-numbers of the tape-drives.
Has anyone seen this
behavior before? Or does anyone has a clue on how to solve this without a
reboot?
Regards,
Rob