One additional item on this, having done a few times.
A slight "gotcha". When you run the "preview" to see what
tapes to bring onsite, then you bring them back. You do the
"restore" and then sometimes find out that you still need another
tape or two.
Why? You have been running reclamation on offsite volumes
and some of the data has been moved since you ran preview
and the time you got tapes back and did restore. So, just
run preview again and find the extra tape or two that you need.
Also, you can have a tape that you brought back, now has been
"emptied" and you can "loose" this tape if not careful. I always
keep a list of tapes brought back and then make sure they all come
back out of library and that they still have data before I send then back
offsite.
David Longo
>>> Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM> 8/20/2008 9:44 AM >>>
Correct, recalling specific offsite tapes for a restore would not be done
with "move drmedia"
Move drmedia follows a normal "lifecycle". Recalling a tape for a restore
is an interrupt in that cycle, so it needs to be handled manually by using
"upd vol $VOL acc=readonly". Running this command puts the tape back into
a drm "mountable" state and will be checked out again (and put back into
the cycle) the next time move drmedia is run to eject tapes for offsite.
Regards,
Shawn
________________________________________________
Shawn Drew
Internet
larry.mcnutt AT TIMKEN DOT COM
Sent by: ADSM-L AT VM.MARIST DOT EDU
08/20/2008 09:35 AM
Please respond to
ADSM-L AT VM.MARIST DOT EDU
To
ADSM-L
cc
Subject
Re: [ADSM-L] Recalling drmedia volumes to restore a damaged volume.
Thanks for the replies Howard and Steve.
I guess I am looking for a confirmation that recalling specific offsite
copypool tapes is not handled by using "move drmedia" commands. It
won't let me "move drmedia volnnn wherestate=vault
tostate=vaultretrieve", or "move drmedia volnnn
tostate=courierretrieve". So, it looks like I must manually edit the
vaultretrieve report and add the volume(s) needed and edit the vault
inventory report to remove the volumes. After the tapes arrive, follow
the steps to restore the volume and send the copypool tapes back to the
vault.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steven Harris
Sent: Tuesday, August 19, 2008 6:54 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Recalling drmedia volumes to restore a damaged volume.
Hi Larry
If its the mismatch between the DRM location and the real location that
bothers you,
upd vol <vol_name> location='' access=readonly
will put it back to mountable.
Regards
Steve.
"Mcnutt, Larry
E."
<larry.mcnutt@TIM
To
KEN.COM> ADSM-L AT VM.MARIST DOT EDU
Sent by: "ADSM:
cc
Dist Stor
Manager"
Subject
<[email protected] [ADSM-L] Recalling drmedia
volumes
.EDU> to restore a damaged volume.
20/08/2008 07:22
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
TSM 5.4.3.0
AIX 5.3
Hello list,
I have a damaged primary storage pool volume. Fortunately, the data is
on copy pool volumes. I found a nicely detailed procedure for handling
the restoral of the data from mail-archive.
http://www.mail-archive.com/adsm-l AT vm.marist DOT edu/msg25446/adsm_restore_a
_tape_volume.doc
The part that I do not see how to do "cleanly" is recalling the specific
volumes from offsite using "move drmedia" commands. I know I can
manually add the volumes to the "vaultretrieve" list and remove them
from the "vault" inventory report. But that doesn't feel right. Am I
missing something?
Thanks,
Larry McNutt
-----------------------------------------
This message and any attachments are intended for the individual or
entity named above. If you are not the intended recipient, please
do not forward, copy, print, use or disclose this communication to
others; also please notify the sender by replying to this message,
and then delete it from your system. The Timken Company / The
Timken Corporation
This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
#####################################
This message is for the named person's use only. It may
contain private, proprietary, or legally privileged information.
No privilege is waived or lost by any mistransmission. If you
receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it,
and notify the sender. You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message if you
are not the intended recipient. Health First reserves the right to
monitor all e-mail communications through its networks. Any views
or opinions expressed in this message are solely those of the
individual sender, except (1) where the message states such views
or opinions are on behalf of a particular entity; and (2) the sender
is authorized by the entity to give such views or opinions.
#####################################
|
