Well - here goes.
It looks like the problem was due to some entries in the MM database that
still had invalid robot numbers against them - there were a couple for the
robot I was moving and a few for a robot that was decommissioned over a year
ago.
When starting NB Master, the vmd process was adding the extra line to the
vm.conf file. I guess when it was searching for robots it was getting as
far as the invalid entries and not going any further or something.
So the problem was resolved by moving the old media volumes to standalone,
which automatically made the 2 invalid robot selections in the media manager
disappear. For some reason these old volume entries didn't show up on the
inventory list I had originally worked with.
Once the config was sorted out and master and slave servers were restarted,
everything worked.
Thanks to those who offered suggestions.
Cheers, Gavin
-----Original Message-----
From: Gregory, Gavin [mailto:Gavin.Gregory AT airnz.co DOT nz]
Sent: Monday, 3 February 2003 12:11
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] Moving robot to a new server
Further info.
I've removed the old media server and storage unit completely from the
Netbackup config.
I've removed any reference to the old server from the vm.conf file on the
master.
However, when I restart Netbackup on the master, something adds the
following line to my vm.conf file:
DEVICE_HOST = aknmd04u
which is the old media server.
Also the xvmadm and bpadm utils still reference robot #1 as still being
attached to the old server.
Cheers, Gavin
-----Original Message-----
From: Gregory, Gavin [mailto:Gavin.Gregory AT airnz.co DOT nz]
Sent: Sunday, 2 February 2003 17:24
To: 'Steven L. Sesar'
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] Moving robot to a new server
Output from "tpconfig -d" on the old media server shows only a standalone
drive that is still connected:
aknmd04u:/ # tpconfig -d
Index DriveName DrivePath Type Multihost
Status
***** ********* ********** **** *********
******
0 Drive0 /dev/rmt/4cbn dlt No UP
Standalone drive volume database host = cpamaster-p1.airnz.co.nz
aknmd04u:/ #
and on the new media server, gives the expected results:
aklxp074:/ # tpconfig -d
Index DriveName DrivePath Type Multihost
Status
***** ********* ********** **** *********
******
0 Drive0 /dev/rmt/0cbn dlt No UP
TLD(1) Definition DRIVE=1
1 Drive1 /dev/rmt/1cbn dlt No UP
TLD(1) Definition DRIVE=2
2 Drive2 /dev/rmt/2cbn dlt No UP
TLD(1) Definition DRIVE=3
3 Drive3 /dev/rmt/3cbn dlt No UP
TLD(1) Definition DRIVE=4
Currently defined robotics are:
TLD(1) robotic path = /dev/sg/c2t0l0, volume database host = aklxp074
aklxp074:/ #
I/m thinking maybe I need to delete the old media server completely, then
see if the robot is detected on the new server. I've already moved the
media db for all volumes from the library to the new media server.
Thanks,
Gavin
-----Original Message-----
From: Steven L. Sesar [mailto:ssesar AT mitre DOT org]
Sent: Sunday, 2 February 2003 14:08
To: Gregory, Gavin
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: Re: [Veritas-bu] Moving robot to a new server
Your master server still thinks that the robot is connected to your old
media server. What does tpconfig -d tell you? If it reveals your
mismatch, then you can simply update it using tpconfig. It's fairly
self-documenting, if you haven't used that tool before.
However, your work isn't quite done yet, if the tapes that went to the
new media server with the robot. You will need to move the images over
to the new server, as well. I think that you use bpimage to do that, but
don't quote me on it.
--Steve
Gregory, Gavin wrote:
> Hi all.
>
> I've just moved a Storagetek robot from one media server to another. It
> seems to be working as I can get an inventory of the contents by
specifying
> the hostname of the new server in the MM gui "Robot Inventory" options,
but
> the list of existing robots still has the old server name.
>
> If I try to update the volume config based on the robot contents I get
> "robot number and robot host mismatch".
>
> I've done this before with no problems but I think I may have missed
> something this time - we have several NB environments but it's been a
while
> since I've had to do anything with this old one.
>
> NB Master: Solaris 2.6 / Netbackup 3.2GA
> Both media servers: Solaris 2.6 / Netbackup 3.2GA
>
> Thanks for any help!
> regards, Gavin
>
> ____________________________________________________________________
> CAUTION - This message may contain privileged and confidential
> information intended only for the use of the addressee named above.
> If you are not the intended recipient of this message you are hereby
> notified that any use, dissemination, distribution or reproduction
> of this message is prohibited. If you have received this message in
> error please notify Air New Zealand immediately. Any views expressed
> in this message are those of the individual sender and may not
> necessarily reflect the views of Air New Zealand.
> _____________________________________________________________________
> For more information on the Air New Zealand Group, visit us online
> at http://www.airnewzealand.com
> _____________________________________________________________________
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
--
===================================
Steven L. Sesar
Ops. Sys. Programmer/Analyst, Sr.
UNIX Infrastructure R101
The MITRE Corporation
202 Burlington Road - R101
Bedford, MA 01730
tel: (781) 271-7702
fax: (781) 271-2600
email: ssesar AT mitre DOT org
mobile: (617) 893-9635
===================================
____________________________________________________________________
CAUTION - This message may contain privileged and confidential
information intended only for the use of the addressee named above.
If you are not the intended recipient of this message you are hereby
notified that any use, dissemination, distribution or reproduction
of this message is prohibited. If you have received this message in
error please notify Air New Zealand immediately. Any views expressed
in this message are those of the individual sender and may not
necessarily reflect the views of Air New Zealand.
_____________________________________________________________________
For more information on the Air New Zealand Group, visit us online
at http://www.airnewzealand.com
_____________________________________________________________________
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
____________________________________________________________________
CAUTION - This message may contain privileged and confidential
information intended only for the use of the addressee named above.
If you are not the intended recipient of this message you are hereby
notified that any use, dissemination, distribution or reproduction
of this message is prohibited. If you have received this message in
error please notify Air New Zealand immediately. Any views expressed
in this message are those of the individual sender and may not
necessarily reflect the views of Air New Zealand.
_____________________________________________________________________
For more information on the Air New Zealand Group, visit us online
at http://www.airnewzealand.com
_____________________________________________________________________
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
____________________________________________________________________
CAUTION - This message may contain privileged and confidential
information intended only for the use of the addressee named above.
If you are not the intended recipient of this message you are hereby
notified that any use, dissemination, distribution or reproduction
of this message is prohibited. If you have received this message in
error please notify Air New Zealand immediately. Any views expressed
in this message are those of the individual sender and may not
necessarily reflect the views of Air New Zealand.
_____________________________________________________________________
For more information on the Air New Zealand Group, visit us online
at http://www.airnewzealand.com
_____________________________________________________________________
|
