Hi again,
Thank you Neil !
- Sorry, but 'UPD LIBV ... OWN=' do not solve the problem ...
---> ANR8969E The owner of volume XXXXXX can not be updated to owner TSM1.
- we also use 'EXPORT NODE ... TOSERVER=...' and it works great.
But it is not very useful to transfer nodedata (hundrets of TB) over
ethernet because there is no idea how to get the export volumes to scratch
state after importing on another server in a shared library environment ...
-> After importing the ownership changes to the importing server
-> volumes should get back to SCRATCH after 'DEL VOLHIST T=EXP' on the
exporting server
(the volumes are deleted from volhist but remain PRIVATE because owner
is another server)
-> after that the only way to put them to SCRATCH is 'AUDIT LIBRARY'
(otherwise the volumes stay PRIVATE forever)
Any other idea(s) ?
Thank you !
Otto
-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag von
Strand, Neil B.
Gesendet: Freitag, 27. Juni 2008 16:39
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: [ADSM-L] Export / import nodes with shared library
Otto,
- You should be able to just update the libvol owner on the library manager
to the new server.
- You may also consider using server-server export which transfers data
through the ethernet from the source to target server. This process allows
for concurrent export/import and reduces the chance of mixing up the
sequence of export tape volumes. To do this you need to set up server-server
communications betweeen the source and target servers.
See the help page for export node "EXPORT NODE -- Directly to Another
Server" for the export syntax.
Cheers,
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Otto Chvosta
Sent: Friday, June 27, 2008 10:06 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Export / import nodes with shared library
Hi TSM'ers,
We splitted our TSM Server up to five instances (four library clients, one
library manager, 3494)
To move the nodes to new instances we export/import them on tape
(TSM0 is library manager, TSM1-TSM4 are library clients)
(1) on instance TSM1: Export node to volume(s)
volhist entries are made
owner ist TSM1
(2) on instance TSM2: import node from those volumes
now owner is TSM2
there were no entries made into volhist
(3) after succesful import on instance TSM1: del volhist type=export ...
entries in volhist of
TSM1 are removed
But we got an error on TSM0 (Library manager):
ANR9999D smlshare.c(4724): ThreadId <21> Invalid owner(TSM1) attempting to
delete volume J20010.
....
Is this the normal behavior ?
Is the only way to get the volumes back to scratch an AUDIT LIBRARY on the
library clients ?
Is this the recommended way to do that ?
Where is the recommended way documented ?
TIA !
Otto
_________________________________
TSM Administration
Medical University Vienna Austria
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive or action-oriented messages to us via
electronic mail.
This message is intended for the addressee only and may contain privileged
or confidential information. Unless you are the intended recipient, you may
not use, copy or disclose to anyone any information contained in this
message. If you have received this message in error, please notify the
author by replying to this message and then kindly delete the message. Thank
you.
|
