Thanks Shawn!
I cleaned up the volume history. I think I was just a little hesitant because
of the warning it gives you in the explanation of delete volhist when you use
DRM, but what you said makes sense! Thanks again!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Shawn Drew
Sent: Monday, July 20, 2009 11:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Del volh
Yes, we use DRM, however we have since moved to using a remote VTL for the
DB Backups.
Ever since then, we've also added "del volh todate=-7 t=dbb" since we
don't manage those volumes with DRM.
If you are worried about losing track of tapes that become scratch or
"Vault Retreive" while they are offsite, that won't be a problem. TSM
doesn't actually remove them from the Copy storage pool until they are
returned and you run the "move drm xxxx tostat=onsiteret
Regards,
Shawn
________________________________________________
Shawn Drew
Internet
joni.moyer AT HIGHMARK DOT COM
Sent by: ADSM-L AT VM.MARIST DOT EDU
07/20/2009 11:24 AM
Please respond to
ADSM-L AT VM.MARIST DOT EDU
To
ADSM-L
cc
Subject
Re: [ADSM-L] Del volh
Hi Shawn,
You are probably right about the syntax. I didn't see anything indicating
you could place commas between the types. Do you use DRM in your
environment?
Thanks again!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Shawn Drew
Sent: Monday, July 20, 2009 11:22 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Del volh
I run the following every day with no issues:
del volh todate=-7 t=stgn
del volh todate=-7 t=stgr
del volh todate=-7 t=stgd
I didn't think you could use multiple types on one line like that.
Regards,
Shawn
Internet
joni.moyer AT HIGHMARK DOT COM
Sent by: ADSM-L AT VM.MARIST DOT EDU
07/20/2009 10:27 AM
Please respond to
ADSM-L AT VM.MARIST DOT EDU
To
ADSM-L
cc
Subject
[ADSM-L] Del volh
Hi Everyone,
I would like to clean up the volume history, but I do not want to cause
issues with tapes that are managed by DRM. In looking at the command &
what it can accomplish I would probably like to get rid of all old volume
information for new, reused & deleted volumes from years ago.
del volhist todate=01/01/2007 type=stgnew,stgreuse,stgdelete
Would running this del volhist command have any negative impact on volumes
managed by DRM that are still in storage groups and have a long retention
period?
How often do most of you run this command and what do you typically purge
from the volume history?
Thanks in advance!
Joni Moyer
Storage Administrator III
(717)302-9966
joni.moyer AT highmark DOT com
________________________________
This e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed. If
you have received this e-mail in error, please notify the sender
immediately and then delete it. If you are not the intended recipient, you
must not keep, use, disclose, copy or distribute this e-mail without the
author's prior permission. The views expressed in this e-mail message do
not necessarily represent the views of Highmark Inc., its subsidiaries, or
affiliates.
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 e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed. If
you have received this e-mail in error, please notify the sender
immediately and then delete it. If you are not the intended recipient,
you must not keep, use, disclose, copy or distribute this e-mail without
the author's prior permission. The views expressed in this e-mail message
do not necessarily represent the views of Highmark Inc., its subsidiaries,
or affiliates.
This e-mail and any attachments to it are confidential and are intended solely
for use of the individual or entity to whom they are addressed. If you have
received this e-mail in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this e-mail without the author's prior permission.
The views expressed in this e-mail message do not necessarily represent the
views of Highmark Inc., its subsidiaries, or affiliates.
|
