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 todat
=yes (to mark the invalid files for deletion)
-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: [ADSM-L] Delete Volhist
If I wanting to keep two weeks of
Subject: [ADSM-L] Delete Volhist
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 running only type=dbb I'm noticing a lot of volum
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 running only type=dbb I'm noticing a lot of volumes that no longer exist
in t
ttp://www-01.ibm.com/support/docview.wss?uid=swg21653710&myns=swgtiv&mynp=OCSSGSG7&mync=E
>
> We generally set the DRM with SET DRMDBBACKUPEXPIREDAYS and then after
> tapes moved to vault for the day, run the following commands
>
> delete volhist type=ALL todate=TODAY-180
&
he following commands
delete volhist type=ALL todate=TODAY-180
delete volhist type=DBB todate=TODAY-3
Should I be concerned?
Thank You,
-Nick
Nick Marouf | Systems Administrator Consultant
PA Department of Transportation | Bureau of Infrastructure and Operations
1400A North Cameron St | Harrisb
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
MARIST.EDU
Subject: Re: [ADSM-L] delete volhist for dbsnapshots
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 [mai
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 t
@VM.MARIST.EDU] On Behalf Of
Ehresman,David E.
Sent: Wednesday, May 29, 2013 9:47 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] delete volhist for dbsnapshots
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
: Wednesday, May 29, 2013 9:39 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] delete volhist for dbsnapshots
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=
Tim
Brown
Sent: Wednesday, May 29, 2013 9:36 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] delete volhist for dbsnapshots
Issuing this command doesn't delete any vol historys for dbsnapshots
tsm: TSMPOK_SERVER1>del volh type=dbsnapshot todate=today-6
Do you wish to proceed? (Yes (Y)/No
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
Issuing this command doesn't delete any vol historys for dbsnapshots
tsm: TSMPOK_SERVER1>del volh type=dbsnapshot todate=today-6
Do you wish to proceed? (Yes (Y)/No (N)) y
ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
successfully deleted.
tsm: TSMPOK_SERVER1>q volh t=db
ent: den 29 mars 2010 10:51
> To: ADSM-L@vm.marist.edu
> Subject: Re: [ADSM-L] delete volhist
>
>
>> 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=t
ore program which volumes to
use.
Jerry Michalak
jerry_...@yahoo.com
From: Mehdi Salehi
To: ADSM-L@VM.MARIST.EDU
Sent: Sun, March 28, 2010 4:44:41 AM
Subject: [ADSM-L] delete volhist
Hi,
- A TSM server has weekly full and daily incremental database back
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
iginal Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Christian Svensson
Sent: zondag 28 maart 2010 11:50
To: ADSM-L@VM.MARIST.EDU
Subject: SV: delete volhist
TSM will always keep minimum 1 full TSM DB Backup.
You can never delete that volume from Volhist unt
> E-mail: christian.svens...@cristie.se
> Skype: cristie.christian.svensson
> Supported Platform for CPU2TSM::
> http://www.cristie.se/cpu2tsm-supported-platforms
>
>
> Från: Mehdi Salehi [ezzo...@googlemail.com]
> Skickat: den 28 mars 2010 11:4
See the documentation of DSMSERV DISPLAY DBBACKUPVOLUME
On Mar 28, 2010, at 6:13 AM, Mehdi Salehi wrote:
Thank Christian,
Say I have another copy of .dbb files of a backup in another path. So,
"delete volhist" could not affect (delete) them. Is there any way to
use
these backu
Thank Christian,
Say I have another copy of .dbb files of a backup in another path. So,
"delete volhist" could not affect (delete) them. Is there any way to use
these backup files to restore the database while "q volhist" knows nothing
about them?
2010 11:44
Till: ADSM-L@VM.MARIST.EDU
Ämne: delete volhist
Hi,
- A TSM server has weekly full and daily incremental database backups.
- All volume history information are accidentally deleted by "delete volhist
type=all todate=today"
- Can TSM admin restore database backups?
Thanks
Hi,
- A TSM server has weekly full and daily incremental database backups.
- All volume history information are accidentally deleted by "delete volhist
type=all todate=today"
- Can TSM admin restore database backups?
Thanks
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; tha
I have a question about a schedule that has been running on a TSM server
in our system.
Each day at about 12:30 it runs this command:
"del volhistory todate=-90 type=all"
My question is, would anyone know of a reason to be doing this? I
haven't historically set anything like this up on an
7:53
> À : ADSM-L@VM.MARIST.EDU
> Objet : Re: [ADSM-L] AW: [ADSM-L] Unable to delete volhist entries
>
> But a force works. I just tried it. :)
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
> On Behalf Of Otto Chvosta
> Sent: Mo
But a force works. I just tried it. :)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Otto
Chvosta
Sent: Monday, October 01, 2007 10:06 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] AW: [ADSM-L] Unable to delete volhist entries
Thank you !
In
40
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: [ADSM-L] Unable to delete volhist entries
In the help of del volh command, you can find :
DBSnapshot
Specifies to delete only records that contain information about
volumes used for snapshot database backups, and that mee
You can try :
del volh t=dbs force=y tod=today
Regards,
Pierre Cayé
> -Message d'origine-
> De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De
> la part de Richard Sims
> Envoyé : lundi 1 octobre 2007 13:18
> À : ADSM-L@VM.MARIST.EDU
> Objet : Re: [A
On Oct 1, 2007, at 4:48 AM, Otto Chvosta wrote:
... ANR2467I DELETE VOLHISTORY: 0 sequential volume history
entries were
successfully deleted.
Any suggestions how to delete the entries ?
Otto -
There is really one entry, for a single backup series (#2),
consisting of multiple volumes. As
Hi TSMer's,
At our TSM Server 5.3.4 on AIX 5.3 we use a deviceclass devtype FILE for
database snapshots.
tsm: TSM1>q devclass FILE32G f=d
Device Class Name: FILE32G
Device Access Strategy: Sequential
Storage Pool Count: 0
Device Type: FILE
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 volhis
> 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
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 sure why that would be an issue or if there
is something I
thanks a lot
Force=y worked .
Of cource it is not decomented.
Hana
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Remco Post
Sent: Friday, June 08, 2007 10:33 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Canot delete volhist after load db
ing?
I
> would think this would remove it from volhist as well.
>
depend on weather or not you use drm, but delete volhist -todate=-5
force=y does do the trick (at least did t=it for me), and should be
better documented.
> On 6/6/07, Richard Sims <[EMAIL PROTECTED]> wrote:
>>
Doug Fox wrote:
> Can't you just change your retention of DBBackup sets to 1 and let it
> expire
> itself, then change it back? Or am I not thinking about the same thing? I
> would think this would remove it from volhist as well.
>
depend on weather or not you use drm, but de
Can't you just change your retention of DBBackup sets to 1 and let it expire
itself, then change it back? Or am I not thinking about the same thing? I
would think this would remove it from volhist as well.
On 6/6/07, Richard Sims <[EMAIL PROTECTED]> wrote:
On Jun 6, 2007, at 10:48 AM, חנה דרזי
On Jun 6, 2007, at 10:48 AM, חנה דרזי wrote:
After Unload and load database 5.3.5 on windows.
When I triy to delete dbbackup records from volume history I get:
DELETE VOLHISTORY: 0 sequential volume history entries were
I delete volumes from 4 days befor and I have volumes from 30 May
How can I
After Unload and load database 5.3.5 on windows.
When I triy to delete dbbackup records from volume history I get:
DELETE VOLHISTORY: 0 sequential volume history entries were
I delete volumes from 4 days befor and I have volumes from 30 May
How can I fix it ?
Thanks Hana
-
lem with delete volhist type=dbb
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Kauffman, Tom
I'm using a dedicated pool of tapes for off-site database
backups, which seems to be working OK - almost. The problem is
that the delete volhist returns the tape to scratch status,
--Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Of Stapleton, Mark
> Sent: Thursday, August 26, 2004 9:02 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with delete volhist type=dbb
>
> From: ADSM: Dist Stor Manager [mailto:[EMAIL
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Kauffman, Tom
>I'm using a dedicated pool of tapes for off-site database
>backups, which seems to be working OK - almost. The problem is
>that the delete volhist returns the tape to scratch status,
>making it
I'm using a dedicated pool of tapes for off-site database backups, which
seems to be working OK - almost. The problem is that the delete volhist
returns the tape to scratch status, making it available to the next
process that wants a scratch tape. 15 days later (my rotation) the
database b
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
n the Volume History File, because they have been used for
Database Backups for instance. Tapes listed in the Volume History File
are not in a Storage Pool per se, although they could be considered to
be in their own different kind of storage pool. When you run the DELETE
VOLHIST command, or whe
: 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
Has anyone seen this? I'm on server version 4.2.3.0 (W2K).
I run a 'delete volhist type=dbb tod=today-1'. The volume history is
deleted, but the tape, which is in the library, doesn't return to
scratch?
Thanks for any replies!
Paul Miller
01 8:37 AM
To: [EMAIL PROTECTED]
Subject: Delete volhist question
All-
The answer to this is probably obvious, but I never thought about the
question until recently.
As a routine practice, we have always set up TSM servers to do a "delete
volhist type=dbb" (for machines not using DRM) t
All-
The answer to this is probably obvious, but I never thought about the
question until recently.
As a routine practice, we have always set up TSM servers to do a "delete
volhist type=dbb" (for machines not using DRM) to get rid of entries for
old database backups...pretty stand
57 matches
Mail list logo
