This is a multipart message in MIME format.
--=_alternative 004DB27A87256C3F_=
Content-Type: text/plain; charset="us-ascii"
Larry,
Thanx for the additional info. I had a pair of "younger eyes" look at the
massed-together info from vmupdate -help and he did indeed find a -vh
(volume database host) parameter that I had missed. I added it to my
vmupdate command and it is now in sync with vmquery.
Strange, that although orginally I ran vmupdate from my Master/volDB host
(nbuh1), it assumed--in the absence of the -vh parameter--that the volDB
host was the same as the robot host (nbuh2). Maybe Veritas will document
this command in a future release.
Jim
Larry Kingery <larry.kingery AT veritas DOT com>
09/25/2002 07:29 AM
Please respond to larry.kingery
To: JLaurie AT csu DOT org
cc:
bcc:
Subject: Re: [Veritas-bu] CLI vmupdate & vmquery mismatch
JLaurie AT csu DOT org writes:
>
> Larry,
>
> Thanx for the response.
>
> I'm not sure why this is happening.
> I ran both commands on my NBU master, nbuh1 but vmupdate updated the
> volDB on nbuh2
> I used vmupdate (obviously, not a supported command) to update the
> inventory of tapes in the robot controlled by robot host nbuh2; but I
> guess it assumed that the robot host is the volume DB host, which I did
> not want to happen. Other commands make the distinction between robot
> host and volume DB host (vmquery, vmchange, etc).
vmupdate also takes a -h parameter.
>
> Am I "violating the rules" here? I really only want one volDB
> I added a Compaq TL892 robot and attached it to a media server (nbuh2)
> but I would prefer to have all database info in one place to make it
> easier to manage.
>
> Any thoughts?
Check volume database host configuration and volDB sizes on master and
media.
>
> Jim
>
>
>
> Larry Kingery <larry.kingery AT veritas DOT com>
>
>
> 09/24/2002 02:38 PM
> Please respond to larry.kingery
>
> To: JLaurie AT csu DOT org
> cc:
> bcc:
> Subject: Re: [Veritas-bu] CLI vmupdate & vmquery mismatch
>
>
>
>
> Where are you running these commands (master or media), and what are
> the settings for your volDB host on each? Also, is the size of the
> volDB on any host besides the master (or the volDB host) greater than
> 8 bytes?
>
> I think what you may have done is updated a volDB on the wrong host,
> so vmquery is looking at a different volDB. This would be quite bad.
>
>
> JLaurie AT csu DOT org writes:
> >
> > I used the CLI vmupdate & vmquery commands and received the
> > following--note that vmquery still shows the contents of the robot
> > before swapping tapes. Am I missing something here? I can use vmadm to
> > "interactively" update the robot inventory but that won't help me
> script
> > it.
> > Suggestions?
> >
> > TLI,
> > Jim
> >
> > vmupdate -rn 1 -rt tld -rh nbuh2
> > Generating list of recommended changes ...
> >
> > Proposed Change(s) to Update the Volume Configuration
> > =====================================================
> > Logically move media ID DF7985 (barcode DF7985) from slot 10 to
> > standalone residence.
> > Logically move media ID AP4169 (barcode AP4169) from slot 1 to
> > standalone residence.
> > Logically move media ID AZ9657 (barcode AZ9657) from slot 2 to
> > standalone residence.
> > Logically move media ID AZ9748 (barcode AZ9748) from slot 3 to
> > standalone residence.
> > Logically move media ID AZ9759 (barcode AZ9759) from slot 4 to
> > standalone residence.
> > Logically move media ID AZ9245 (barcode AZ9245) from slot 7 to
> > standalone residence.
> > Logically move media ID AZ9745 (barcode AZ9745) from slot 5 to
> > standalone residence.
> > Logically move media ID AZ9733 (barcode AZ9733) from slot 6 to
> > standalone residence.
> > Logically move media ID AZ9753 (barcode AZ9753) from slot 8 to
> > standalone residence.
> > Logically move media ID AZ9251 (barcode AZ9251) from slot 9 to
> > standalone residence.
> > Logically move media ID AP4169 (barcode AP4169) from standalone to
> slot
> > 10.
> > Logically move media ID AZ9245 (barcode AZ9245) from standalone to
> slot
> > 5.
> > Logically add new media AZ9754 (barcode AZ9754) to robot slot 1.
> > Logically add new media AZ9659 (barcode AZ9659) to robot slot 2.
> > Logically add new media AZ9656 (barcode AZ9656) to robot slot 3.
> > Logically add new media AZ9604 (barcode AZ9604) to robot slot 4.
> > Logically add new media AP4165 (barcode AP4165) to robot slot 7.
> > Logically add new media AZ9236 (barcode AZ9236) to robot slot 6.
> > Logically add new media DF7971 (barcode DF7971) to robot slot 8.
> > Logically add new media CC3332 (barcode CC3332) to robot slot 9.
> > Updating volume configuration ...
> >
> > Processing existing media removed from or moved within the robotic
> > library by
> > logically moving media to standalone residence as follows...
> > Media ID Slot
> > ======== ====
> > DF7985 10
> > AP4169 1
> > AZ9657 2
> > AZ9748 3
> > AZ9759 4
> > AZ9245 7
> > AZ9745 5
> > AZ9733 6
> > AZ9753 8
> > AZ9251 9
> >
> > Processing existing media added to or moved within the robotic library
> > by
> > logically moving media as follows...
> > Media ID Slot
> > ======== ====
> > AP4169 10
> > AZ9245 5
> >
> > Processing new media added to the robotic library by logically
> > adding media with new media IDs as follows...
> > Media ID Slot
> > ======== ====
> > AZ9754 1
> > AZ9659 2
> > AZ9656 3
> > AZ9604 4
> > AP4165 7
> > AZ9236 6
> > DF7971 8
> > CC3332 9
> >
> >
> > Volume configuration successfully updated.
> >
> > # vmquery -b -rn 1
> > media media robot robot robot side/ optical # mounts/
> last
> > ID type type # slot face partner cleanings mount
> > time
> >
> ------------------------------------------------------------------------
> > -------
> > AP4169 DLT TLD 1 1 - - 3
> > 08/22/2002 13:40
> > AZ9657 DLT TLD 1 2 - - 3
> > 09/23/2002 23:41
> > AZ9748 DLT TLD 1 3 - - 9
> > 09/20/2002 16:10
> > AZ9759 DLT TLD 1 4 - - 2
> > 09/20/2002 19:13
> > AZ9245 DLT TLD 1 7 - - 2
> > 08/16/2002 14:33
> > AZ9745 DLT TLD 1 5 - - 2
> > 09/20/2002 21:13
> > AZ9733 DLT TLD 1 6 - - 3
> > 09/23/2002 17:02
> > AZ9753 DLT TLD 1 8 - - 2
> > 09/23/2002 17:42
> > AZ9251 DLT TLD 1 9 - - 2
> > 09/23/2002 19:41
> > DF7985 DLT TLD 1 10 - - 2
> > 09/23/2002 21:41
> >
--=_alternative 004DB27A87256C3F_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">Larry,</font>
<br>
<br><font size=2 face="sans-serif">Thanx for the additional info. I had a pair
of "younger eyes" look at the massed-together info from vmupdate
-help and he did indeed find a -vh (volume database host) parameter that I had
missed. I added it to my vmupdate command and it is now in sync with
vmquery.</font>
<br><font size=2 face="sans-serif">Strange, that although orginally I ran
vmupdate from my Master/volDB host (nbuh1), it assumed--in the absence of the
-vh parameter--that the volDB host was the same as the robot host (nbuh2).
Maybe Veritas will document this command in a future release.</font>
<br>
<br><font size=2 face="sans-serif">Jim</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Larry Kingery <larry.kingery AT
veritas DOT com></b></font>
<p><font size=1 face="sans-serif">09/25/2002 07:29 AM</font>
<br><font size=1 face="sans-serif">Please respond to larry.kingery</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
JLaurie AT csu DOT org</font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> bcc:
</font>
<br><font size=1 face="sans-serif"> Subject:
Re: [Veritas-bu] CLI vmupdate & vmquery
mismatch</font></table>
<br>
<br>
<br><font size=2 face="Courier New">JLaurie AT csu DOT org writes:<br>
> <br>
> Larry, <br>
> <br>
> Thanx for the response. <br>
> <br>
> I'm not sure why this is happening. <br>
> I ran both commands on my NBU master, nbuh1 but vmupdate updated the<br>
> volDB on nbuh2 <br>
> I used vmupdate (obviously, not a supported command) to update the<br>
> inventory of tapes in the robot controlled by robot host nbuh2; but I<br>
> guess it assumed that the robot host is the volume DB host, which I did<br>
> not want to happen. Other commands make the distinction between robot<br>
> host and volume DB host (vmquery, vmchange, etc). <br>
<br>
vmupdate also takes a -h parameter.<br>
<br>
> <br>
> Am I "violating the rules" here? I really only want one volDB
<br>
> I added a Compaq TL892 robot and attached it to a media server (nbuh2)<br>
> but I would prefer to have all database info in one place to make it<br>
> easier to manage. <br>
> <br>
> Any thoughts? <br>
<br>
Check volume database host configuration and volDB sizes on master and<br>
media. <br>
<br>
> <br>
> Jim <br>
> <br>
> <br>
> <br>
> Larry
Kingery <larry.kingery AT veritas DOT com> <br>
> <br>
> <br>
> 09/24/2002 02:38 PM <br>
> Please respond to larry.kingery <br>
> <br>
> To: JLaurie AT csu
DOT org <br>
> cc: <br>
> bcc: <br>
> Subject: Re:
[Veritas-bu] CLI vmupdate & vmquery mismatch<br>
> <br>
> <br>
> <br>
> <br>
> Where are you running these commands (master or media), and what are<br>
> the settings for your volDB host on each? Also, is the size of
the<br>
> volDB on any host besides the master (or the volDB host) greater than<br>
> 8 bytes?<br>
> <br>
> I think what you may have done is updated a volDB on the wrong host,<br>
> so vmquery is looking at a different volDB. This would be quite
bad.<br>
> <br>
> <br>
> JLaurie AT csu DOT org writes:<br>
> > <br>
> > I used the CLI vmupdate & vmquery commands and received the<br>
> > following--note that vmquery still shows the contents of the robot<br>
> > before swapping tapes. Am I missing something here? I can use vmadm
to<br>
> > "interactively" update the robot inventory but that won't
help me<br>
> script<br>
> > it. <br>
> > Suggestions? <br>
> > <br>
> > TLI, <br>
> > Jim <br>
> > <br>
> > vmupdate -rn 1 -rt tld -rh nbuh2<br>
> > Generating list of recommended changes ...<br>
> > <br>
> > Proposed Change(s) to Update the Volume Configuration<br>
> > =====================================================<br>
> > Logically move media ID DF7985 (barcode DF7985) from slot 10 to<br>
> > standalone residence.<br>
> > Logically move media ID AP4169 (barcode AP4169) from slot 1 to<br>
> > standalone residence.<br>
> > Logically move media ID AZ9657 (barcode AZ9657) from slot 2 to<br>
> > standalone residence.<br>
> > Logically move media ID AZ9748 (barcode AZ9748) from slot 3 to<br>
> > standalone residence.<br>
> > Logically move media ID AZ9759 (barcode AZ9759) from slot 4 to<br>
> > standalone residence.<br>
> > Logically move media ID AZ9245 (barcode AZ9245) from slot 7 to<br>
> > standalone residence.<br>
> > Logically move media ID AZ9745 (barcode AZ9745) from slot 5 to<br>
> > standalone residence.<br>
> > Logically move media ID AZ9733 (barcode AZ9733) from slot 6 to<br>
> > standalone residence.<br>
> > Logically move media ID AZ9753 (barcode AZ9753) from slot 8 to<br>
> > standalone residence.<br>
> > Logically move media ID AZ9251 (barcode AZ9251) from slot 9 to<br>
> > standalone residence.<br>
> > Logically move media ID AP4169 (barcode AP4169) from standalone to<br>
> slot<br>
> > 10.<br>
> > Logically move media ID AZ9245 (barcode AZ9245) from standalone to<br>
> slot<br>
> > 5.<br>
> > Logically add new media AZ9754 (barcode AZ9754) to robot slot 1.<br>
> > Logically add new media AZ9659 (barcode AZ9659) to robot slot 2.<br>
> > Logically add new media AZ9656 (barcode AZ9656) to robot slot 3.<br>
> > Logically add new media AZ9604 (barcode AZ9604) to robot slot 4.<br>
> > Logically add new media AP4165 (barcode AP4165) to robot slot 7.<br>
> > Logically add new media AZ9236 (barcode AZ9236) to robot slot 6.<br>
> > Logically add new media DF7971 (barcode DF7971) to robot slot 8.<br>
> > Logically add new media CC3332 (barcode CC3332) to robot slot 9.<br>
> > Updating volume configuration ...<br>
> > <br>
> > Processing existing media removed from or moved within the robotic<br>
> > library by<br>
> > logically moving media to standalone residence as follows...<br>
> > Media ID
Slot<br>
> > ========
====<br>
> > DF7985
10<br>
> > AP4169
1<br>
> > AZ9657
2<br>
> > AZ9748
3<br>
> > AZ9759
4<br>
> > AZ9245
7<br>
> > AZ9745
5<br>
> > AZ9733
6<br>
> > AZ9753
8<br>
> > AZ9251
9<br>
> > <br>
> > Processing existing media added to or moved within the robotic
library<br>
> > by<br>
> > logically moving media as follows...<br>
> > Media ID
Slot<br>
> > ========
====<br>
> > AP4169
10<br>
> > AZ9245
5<br>
> > <br>
> > Processing new media added to the robotic library by logically<br>
> > adding media with new media IDs as follows...<br>
> > Media ID
Slot<br>
> > ========
====<br>
> > AZ9754
1<br>
> > AZ9659
2<br>
> > AZ9656
3<br>
> > AZ9604
4<br>
> > AP4165
7<br>
> > AZ9236
6<br>
> > DF7971
8<br>
> > CC3332
9<br>
> > <br>
> > <br>
> > Volume configuration successfully updated.<br>
> > <br>
> > # vmquery -b -rn 1<br>
> > media media robot robot robot side/
optical # mounts/<br>
> last<br>
> > ID type type # slot
face partner cleanings mount<br>
> > time </font>
<br><font size=2 face="Courier New">> ><br>
>
------------------------------------------------------------------------<br>
> > -------<br>
> > AP4169 DLT TLD 1
1 - -
3<br>
> > 08/22/2002 13:40<br>
> > AZ9657 DLT TLD 1
2 - -
3<br>
> > 09/23/2002 23:41<br>
> > AZ9748 DLT TLD 1
3 - -
9<br>
> > 09/20/2002 16:10<br>
> > AZ9759 DLT TLD 1
4 - -
2<br>
> > 09/20/2002 19:13<br>
> > AZ9245 DLT TLD 1
7 - -
2<br>
> > 08/16/2002 14:33<br>
> > AZ9745 DLT TLD 1
5 - -
2<br>
> > 09/20/2002 21:13<br>
> > AZ9733 DLT TLD 1
6 - -
3<br>
> > 09/23/2002 17:02<br>
> > AZ9753 DLT TLD 1
8 - -
2<br>
> > 09/23/2002 17:42<br>
> > AZ9251 DLT TLD 1
9 - -
2<br>
> > 09/23/2002 19:41<br>
> > DF7985 DLT TLD 1
10 - -
2<br>
> > 09/23/2002 21:41<br>
> ></font>
<br>
--=_alternative 004DB27A87256C3F_=--
|
