Op 12 mrt. 2014, om 22:05 heeft Maness, Eric het
volgende geschreven:
> If I wanting to keep two weeks of database backups I'm a little confused on
> how to run the delete volhist command. Usually I would run the following
> command:
>
> delete volhist type=dbb todate=today-14
>
> With runn
Also...
on source server do:
RECONCILE VOLUMES xxxCLASS (where xxxCLASS is the device classthis will
tell you if any volumes are invalid)
Output Example: Volume TSMNBG.DSS.372056474 not valid, source server missing
corresponding entry for
target server.
RECONCILE VOLUMES xxxCLASS fix=y
Hello. We include parms: force and devc
DELETE VOLHISTORY type=dbb todate=today-7 force=yes devc=xxxclass
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Maness, Eric
Sent: Wednesday, March 12, 2014 5:06 PM
To: ADSM-L@VM.MARIST.EDU
Subject
No, just audit your offsite storage site from time 2 time and get all
volumes back TSM lost track of.
Kind regards,
Karel
Op 12 nov. 2013 19:02 schreef "Marouf, Nick" :
> Hello,
> Can someone maybe provide a bit more clarification on this technote?
>
>
>
> http://www-01.ibm.com/support/docview.w
Got it!
I did:
delete volhist type=dbsnapshot todate=today-5 force=yes devc=nbgclass
19 vol hist entries successfully deleted.
Thanks everyone!!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan
Forray
Sent: Wednesday, May 29, 2013 10:5
Hello. Jeannie here, I work with Tim.
I did the q drmstat and it had 60 days. We just changed to 7 days.
I'm reading the documentation and I found:
Use this command to specify when a database backup series is eligible to be
expired.
The value set by this command applies to both a snapshot and
Have you tried adding DEVCLASS? This is what I use
DELETE VOLHIST TODATE=TODAY TYPE=DBSNAPSHOT DEVCLASS=EARTH
On Wed, May 29, 2013 at 10:06 AM, Jeanne Bruno wrote:
> Hello. I work with Tim.
>
> No, the Volume Seq goes up to Volume Seq: 10,019. We want to delete all
> of them actually.
>
Hello. I work with Tim.
No, the Volume Seq goes up to Volume Seq: 10,019. We want to delete all of
them actually.
Also, yes, we tried todate=today-5 and also more specifically todate=05/24/2013
totime=05:11:32
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST
Allen,
What are your setting for DRMSTATS ?
( q drmstats)
My understanding was that it controlled the retention of these volumes, just
like the normal DB backup vols.
~Rick
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Allen
S. Rout
Sent: We
Is that the complete output from " q volh t=dbs", i.e. is there only one
snapshot backup?
TSM won't delete the last db backup of a given type without a force action.
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Wednes
On 05/29/2013 09:35 AM, Tim Brown wrote:
> Issuing this command doesn't delete any vol historys for dbsnapshots
>
> tsm: TSMPOK_SERVER1>del volh type=dbsnapshot todate=today-6
>
6 days..
> Do you wish to proceed? (Yes (Y)/No (N)) y
> ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries
On 29 mrt 2010, at 10:59, Henrik Vahlstedt wrote:
> Does that include the last db backup per deviceclass too?
>
yes it does.
> //Henrik
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Loon, EJ van - SPLXM
> Sent: den 29 mars 2010 10:
I don't know of a way to put them back into the "volhistory" file. But if you
know the volumes and can protect them, track them manually.
As to restoring the TSM server from them, you should be able to, read up on the
"Disaster Recovery" sections. You can tell the restore program which volumes t
yes, force=yes deletes even the last DB backup, I tested that with TSM 5.3
Does that include the last db backup per deviceclass too?
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Loon,
EJ van - SPLXM
Sent: den 29 mars 2010 10:51
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] delete volhist
> You can neve
> You can never delete that volume from Volhist until you have done a new full
> successful backup.
Well, not officially. You can issue a del volh type=dbb todate=today force=yes
which deletes all database backup volumes.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Mess
If you don't delete the volhistory, it grows forever.
If you do a PREPARE command, or send your volhistory file offsite for DR, an
enormously large volhistory becomes a nuisance.
OTOH, if you create backupsets or EXPORT tapes, you don't want to do the
delete volhist with TYPE=ALL; that will get t
What is the output of command q volh t=dbb please ?
> -Message d'origine-
> De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De
> la part de Gill, Geoffrey L.
> Envoyé : mardi 28 août 2007 17:34
> À : ADSM-L@VM.MARIST.EDU
> Objet : Re: [ADSM-L] delete volhist dbb
>
> > The switch
> The switch seems to have created dbb series orphans.
> Try adding DEVclass=__ to the delete.
Yea, I tried this yesterday but am getting "Invalid device class"
message. The weird thing is I can mount those tapes and move the data to
the new tape device so I'm a bit confused as to the mess
On Aug 27, 2007, at 12:22 PM, Gill, Geoffrey L. wrote:
About a month ago I changed the db backup to use a new device class/
tape
type and those are expiring as they should but the db backups that
were
done on a different device class before the change are still there
(looks like 5 of them). Not
where you used "today=today-500" is saying you only want to delete entries
OLDER than 500 days ago... In other words, you are asking it to KEEP things
that are less than about 1.5 years, probably not what you want...
Use "del volhist t=dbb tod=today-7" or some number smaller than 500...
I only keep
ller@;CARGILL.COM]
>Sent: Saturday, November 09, 2002 4:40 AM
>To: [EMAIL PROTECTED]
>Subject: Re: delete volhist doesn't return volume to scratch
>
>
>Thanks, everyone for your replies. I migrated one of the problem TSM
>servers to new hardware today (was going to do it
: Paul Miller [mailto:Paul_Miller@;CARGILL.COM]
Sent: Saturday, November 09, 2002 4:40 AM
To: [EMAIL PROTECTED]
Subject: Re: delete volhist doesn't return volume to scratch
Thanks, everyone for your replies. I migrated one of the problem TSM
servers to new hardware today (was going to do it a
vember 08, 2002 14:31
To: [EMAIL PROTECTED]
Subject: Re: delete volhist doesn't return volume to scratch
Did you perhaps label it and check it in the library as private? I seem
to recall I had similar thing happen with tapes I originally checked in
as
private. They return to their orig
er" <[EMAIL PROTECTED]>
11/08/2002 02:21 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: delete volhist doesn't return volume to
scratch
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Beh
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Paul Miller
> No, it's not the last one. It leaves the last one as it should. After
> I run the command, the volume history is indeed deleted, but the tape
> remains "private" with a last use of "dbbackup". I can update the
supposed to happen.
-Original Message-
From: [EMAIL PROTECTED] [mailto:TRushfor@;CITY.WINNIPEG.MB.CA]
Sent: Thursday, November 07, 2002 16:56
To: [EMAIL PROTECTED]
Subject: Re: delete volhist doesn't return volume to scratch
Is this the last DBB, you can't delete the last one.
Is this the last DBB, you can't delete the last one.
-Original Message-
From: Paul Miller [mailto:Paul_Miller@;CARGILL.COM]
Sent: November 7, 2002 4:17 PM
To: [EMAIL PROTECTED]
Subject: delete volhist doesn't return volume to scratch
Has anyone seen this? I'm on server version 4.2.3.0 (W
No problem. I delete ours regularly.
TSM doesn't make any use of the STGNEW, STGREUSE, and STGDELETE entries.
As far as I know, the only use for them is in the case where you have to
restore your data base to a back level; then looking at the volhist gives
you an idea of which tapes you need to
29 matches
Mail list logo
