Re: delete volhistory

[Lee, Gary D.]

Sir:

Note that all are series 1. You have a full and incramentals.  That constitutes 
a series.

If you wish to delete them you will have to do another full.  That will 
invalidate the previous incramentals and full. 


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bruno 
Oliveira
Sent: Friday, September 11, 2009 10:09 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: delete volhistory

Volume history:

Date/Time : 14/07/09 13h22min58s BRT
 Volume Type : BACKUPFULL
   Backup Series : 1
Backup Operation : 0
  Volume Seq : 1
Device Class : GENCLASS3
 Volume Name : VXA201
Volume Location :
 Command :

   Date/Time : 04/09/09 9h0min15s BRT
 Volume Type : BACKUPINCR
   Backup Series : 1
Backup Operation : 1
  Volume Seq : 1
Device Class : GENCLASS3
 Volume Name : VXA001
Volume Location :
 Command :

   Date/Time : 10/09/09 10h28min15s BRT
 Volume Type : BACKUPINCR
   Backup Series : 1
Backup Operation : 2
  Volume Seq : 1
Device Class : GENCLASS3
 Volume Name : VXA002
Volume Location :
 Command :


2009/9/11 Lee, Gary D. 

> Is this your most recent backup series?  If so, tsm will not delete that.
> Keeps you from shooting yourself.
>
>
> Gary Lee
> Senior System Programmer
> Ball State University
> phone: 765-285-1310
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf 
> Of Bruno Oliveira
> Sent: Friday, September 11, 2009 9:48 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: delete volhistory
>
>  command 'q volhistory'
>
> Date/Time : 04/09/09 9h0min15s BRT
> Volume Type : BACKUPINCR
> Backup Series : 1
> Backup Operation : 1
> Volume Seq : 1
> Device Class : GENCLASS3
> Volume Name : VXA001
> Volume Location :
> Command :
> command 'delete volhistory type=all todate=09/04/2009'
>
> ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were 
> successfully deleted.
>
> Why?
>
>  Note: BRT in the date format is dd/mm/yy
>
> --
> abs,
>
> Bruno Oliveira
> Beagá - Minas Gerais - Brazil
> 55 31 9342 4111
>



--
abs,

Bruno Oliveira
Beagá - Minas Gerais - Brazil
55 31 9342 4111

Re: delete volhistory

[Bruno Oliveira]

Volume history:

Date/Time : 14/07/09 13h22min58s BRT
 Volume Type : BACKUPFULL
   Backup Series : 1
Backup Operation : 0
  Volume Seq : 1
Device Class : GENCLASS3
 Volume Name : VXA201
Volume Location :
 Command :

   Date/Time : 04/09/09 9h0min15s BRT
 Volume Type : BACKUPINCR
   Backup Series : 1
Backup Operation : 1
  Volume Seq : 1
Device Class : GENCLASS3
 Volume Name : VXA001
Volume Location :
 Command :

   Date/Time : 10/09/09 10h28min15s BRT
 Volume Type : BACKUPINCR
   Backup Series : 1
Backup Operation : 2
  Volume Seq : 1
Device Class : GENCLASS3
 Volume Name : VXA002
Volume Location :
 Command :


2009/9/11 Lee, Gary D. 

> Is this your most recent backup series?  If so, tsm will not delete that.
> Keeps you from shooting yourself.
>
>
> Gary Lee
> Senior System Programmer
> Ball State University
> phone: 765-285-1310
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Bruno Oliveira
> Sent: Friday, September 11, 2009 9:48 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: delete volhistory
>
>  command 'q volhistory'
>
> Date/Time : 04/09/09 9h0min15s BRT
> Volume Type : BACKUPINCR
> Backup Series : 1
> Backup Operation : 1
> Volume Seq : 1
> Device Class : GENCLASS3
> Volume Name : VXA001
> Volume Location :
> Command :
> command 'delete volhistory type=all todate=09/04/2009'
>
> ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
> successfully deleted.
>
> Why?
>
>  Note: BRT in the date format is dd/mm/yy
>
> --
> abs,
>
> Bruno Oliveira
> Beagá - Minas Gerais - Brazil
> 55 31 9342 4111
>



-- 
abs,

Bruno Oliveira
Beagá - Minas Gerais - Brazil
55 31 9342 4111

Re: delete volhistory

[PAC Brion Arnaud]

Bruno,

TSM won't let you delete the last full DB backup existing, and therefore the 
incrementals made since then. 
Try to do a new full backup, end re-issue you command : this time it should 
work  !!

Cheers.

Arnaud 

**
Panalpina Management Ltd., Basle, Switzerland,
CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.br...@panalpina.com
**


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bruno 
Oliveira
Sent: vendredi 11 septembre 2009 15:48
To: ADSM-L@VM.MARIST.EDU
Subject: delete volhistory

command 'q volhistory'

Date/Time : 04/09/09 9h0min15s BRT
Volume Type : BACKUPINCR
Backup Series : 1
Backup Operation : 1
Volume Seq : 1
Device Class : GENCLASS3
Volume Name : VXA001
Volume Location :
Command :
command 'delete volhistory type=all todate=09/04/2009'

ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were 
successfully deleted.

Why?

 Note: BRT in the date format is dd/mm/yy

--
abs,

Bruno Oliveira
Beagá - Minas Gerais - Brazil
55 31 9342 4111

Re: delete volhistory

[Lee, Gary D.]

Is this your most recent backup series?  If so, tsm will not delete that. Keeps 
you from shooting yourself. 


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bruno 
Oliveira
Sent: Friday, September 11, 2009 9:48 AM
To: ADSM-L@VM.MARIST.EDU
Subject: delete volhistory

command 'q volhistory'

Date/Time : 04/09/09 9h0min15s BRT
Volume Type : BACKUPINCR
Backup Series : 1
Backup Operation : 1
Volume Seq : 1
Device Class : GENCLASS3
Volume Name : VXA001
Volume Location :
Command :
command 'delete volhistory type=all todate=09/04/2009'

ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were 
successfully deleted.

Why?

 Note: BRT in the date format is dd/mm/yy

--
abs,

Bruno Oliveira
Beagá - Minas Gerais - Brazil
55 31 9342 4111

Re: delete volhistory

[Skylar Thompson]

Do you have a subsequent backup series? This would be started by a full
DB backup taken after this incremental backup.

Bruno Oliveira wrote:
> command 'q volhistory'
>
> Date/Time : 04/09/09 9h0min15s BRT
> Volume Type : BACKUPINCR
> Backup Series : 1
> Backup Operation : 1
> Volume Seq : 1
> Device Class : GENCLASS3
> Volume Name : VXA001
> Volume Location :
> Command :
> command 'delete volhistory type=all todate=09/04/2009'
>
> ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
> successfully deleted.
>
> Why?
>
>  Note: BRT in the date format is dd/mm/yy
>

--
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S048, (206)-685-7354
-- University of Washington School of Medicine

delete volhistory

[Bruno Oliveira]

command 'q volhistory'

Date/Time : 04/09/09 9h0min15s BRT
Volume Type : BACKUPINCR
Backup Series : 1
Backup Operation : 1
Volume Seq : 1
Device Class : GENCLASS3
Volume Name : VXA001
Volume Location :
Command :
command 'delete volhistory type=all todate=09/04/2009'

ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
successfully deleted.

Why?

 Note: BRT in the date format is dd/mm/yy

-- 
abs,

Bruno Oliveira
Beagá - Minas Gerais - Brazil
55 31 9342 4111

Re: How to delete Volhistory...

[ashish sharma]

I agree with Robben,this command worked for me when library manager was
owning a lot of tapes for client nodes thinking that they still conatin DB
backup of client while actually they were not.




On Wed, Jan 21, 2009 at 8:55 PM, Robben Leaf  wrote:

> There are other non-optional parameters in the DELETE VOLHIST command -
> those still need to be there.
>
> DELete VOLHistory TODate=TODAY Type=REMOTE VOLUME= FORCE=YES
>
> Robben Leaf
> Enterprise Storage Backup and Retention
> 651-962-2698
> robben.l...@usbank.com
>
>
>
> From:
> Maria Ilieva 
> To:
> ADSM-L@VM.MARIST.EDU
> Date:
> 01/16/2009 02:34 AM
> Subject:
> Re: [ADSM-L] How to delete Volhistory...
> Sent by:
> "ADSM: Dist Stor Manager" 
>
>
>
> Try audit library X checklabel=barcode  from the library client.
> That worked for me.
>
> Maria Ilieva
>
>
> On Fri, Jan 16, 2009 at 8:14 AM, KIRAN-SYSTEMS
>  wrote:
> > I am using the below command to delete volhis of a library client server
> > from library manager server
> >
> > Del volhis vol= force=yes
> >
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> > Steven Harris
> > Sent: Friday, January 16, 2009 11:24 AM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: Re: [ADSM-L] How to delete Volhistory...
> >
> > We need detail Kiran, if we are to help.
> >
> >
> > Please post the command you are using and the output when it "doesn't
> > work".  also  the output of a
> >
> > select * from volhistory where volume_name='XYZ000L3'  - with your
> > volume of interest substituted
> >
> > Thanks
> >
> > Steve
> >
> > Steven Harris
> > TSM Administrator, Sydney Australia
> >
> >
> >
> >
> >     KIRAN-SYSTEMS
> >  > NMENT.COM <http://nment.com/>> To
> > Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
> > Dist Stor cc
> > Manager"
> >  > .EDU> Re: [ADSM-L] How to delete
> >   Volhistory...
> >
> > 16/01/2009 04:12
> > PM
> >
> >
> > Please respond to
> > "ADSM: Dist Stor
> > Manager"
> >  >   .EDU>
> >
> >
> >
> >
> >
> >
> > The below command is not working for me.Iam using TSM Server 5.5.0
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> > Robben Leaf
> > Sent: Friday, January 09, 2009 1:02 AM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: Re: [ADSM-L] How to delete Volhistory...
> >
> > Not entirely true. The product doesn't provide a DOCUMENTED way to do
> > this.
> >
> > There are some undocumented parameters for the DELETE VOLHIST command.
> > Specifically, you can add "vol=VOLNAME force=yes" to the command to
> remove
> > the volume forcibly from the volhistory.
> >
> > We have found this command necessary when our library manager thinks
> > another TSM server instance still owns a tape, when that instance has
> > forgotten all about it.
> >
> > Robben Leaf
> >
> >
> >
> >
> > From:
> > Richard Sims 
> > To:
> > ADSM-L@VM.MARIST.EDU
> > Date:
> > 01/08/2009 06:14 AM
> > Subject:
> > Re: [ADSM-L] How to delete Volhistory...
> > Sent by:
> > "ADSM: Dist Stor Manager" 
> >
> >
> >
> > On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:
> >
> >> Please let me know how to delete volume history of a particular
> >> Volume.
> >
> > The product does not provide a way to do this.
> >
> >Richard Sims
> >
> >
> >
> > U.S. BANCORP made the following annotations
> > -
> > Electronic Privacy Notice. This e-mail, and any attachments, contains
> > information that is, or may be, covered by electronic communications
> > privacy
> > laws, and is also confidential and proprietary in nature. If you are not
> > the
> > intended recipient, please be advised that you are legally prohibited
> from
> > retaining, using, copying, distributing, or otherwise disclosing this
> > information in any manner. Instead, please reply to 

Re: How to delete Volhistory...

[Robben Leaf]

There are other non-optional parameters in the DELETE VOLHIST command -
those still need to be there.

DELete VOLHistory TODate=TODAY Type=REMOTE VOLUME= FORCE=YES

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
robben.l...@usbank.com



From:
Maria Ilieva 
To:
ADSM-L@VM.MARIST.EDU
Date:
01/16/2009 02:34 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
"ADSM: Dist Stor Manager" 



Try audit library X checklabel=barcode  from the library client.
That worked for me.

Maria Ilieva


On Fri, Jan 16, 2009 at 8:14 AM, KIRAN-SYSTEMS
 wrote:
> I am using the below command to delete volhis of a library client server
> from library manager server
>
> Del volhis vol= force=yes
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Steven Harris
> Sent: Friday, January 16, 2009 11:24 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] How to delete Volhistory...
>
> We need detail Kiran, if we are to help.
>
>
> Please post the command you are using and the output when it "doesn't
> work".  also  the output of a
>
> select * from volhistory where volume_name='XYZ000L3'  - with your
> volume of interest substituted
>
> Thanks
>
> Steve
>
> Steven Harris
> TSM Administrator, Sydney Australia
>
>
>
>
> KIRAN-SYSTEMS
>  NMENT.COM> To
> Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
> Dist Stor cc
> Manager"
>  .EDU> Re: [ADSM-L] How to delete
>   Volhistory...
>
> 16/01/2009 04:12
> PM
>
>
> Please respond to
> "ADSM: Dist Stor
> Manager"
>.EDU>
>
>
>
>
>
>
> The below command is not working for me.Iam using TSM Server 5.5.0
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Robben Leaf
> Sent: Friday, January 09, 2009 1:02 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] How to delete Volhistory...
>
> Not entirely true. The product doesn't provide a DOCUMENTED way to do
> this.
>
> There are some undocumented parameters for the DELETE VOLHIST command.
> Specifically, you can add "vol=VOLNAME force=yes" to the command to
remove
> the volume forcibly from the volhistory.
>
> We have found this command necessary when our library manager thinks
> another TSM server instance still owns a tape, when that instance has
> forgotten all about it.
>
> Robben Leaf
>
>
>
>
> From:
> Richard Sims 
> To:
> ADSM-L@VM.MARIST.EDU
> Date:
> 01/08/2009 06:14 AM
> Subject:
> Re: [ADSM-L] How to delete Volhistory...
> Sent by:
> "ADSM: Dist Stor Manager" 
>
>
>
> On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:
>
>> Please let me know how to delete volume history of a particular
>> Volume.
>
> The product does not provide a way to do this.
>
>Richard Sims
>
>
>
> U.S. BANCORP made the following annotations
> -
> Electronic Privacy Notice. This e-mail, and any attachments, contains
> information that is, or may be, covered by electronic communications
> privacy
> laws, and is also confidential and proprietary in nature. If you are not
> the
> intended recipient, please be advised that you are legally prohibited
from
> retaining, using, copying, distributing, or otherwise disclosing this
> information in any manner. Instead, please reply to the sender that you
> have
> received this communication in error, and then immediately delete it.
Thank
> you in advance for your cooperation.
>
>
>
> -
>
>
> Disclaimer:
> This email message (including attachments if any) may contain
privileged,
> proprietary, confidential information, which may be exempt from any kind
of
> disclosure whatsoever and is intended solely for the use of addressee
(s).
> If you are not the intended recipient, kindly inform us by return e-mail
> and also kindly disregard the contents of the e-mail, delete the
original
> message and destroy any copies thereof immediately. You are notified
that
> any dissemination, distribution or copying of this communication is
> strictly prohibited unless approved by the sender.
>
> DQ Entertainment (DQE) has taken every reasonable precaution to minimize
> the risk of transmission of computer viruses with this e-mail;

Re: How to delete Volhistory...

[Bob Levad]

I am not sure which parms are absolutely required, but this is the command I
used to get rid of an old entry.

DELETE VOLHISTORY type=backupset volume=D:\88894302.OST force=yes
todate=today

Bob.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
KIRAN-SYSTEMS
Sent: Friday, January 16, 2009 12:15 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to delete Volhistory...

I am using the below command to delete volhis of a library client server
from library manager server

Del volhis vol= force=yes


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Steven Harris
Sent: Friday, January 16, 2009 11:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to delete Volhistory...

We need detail Kiran, if we are to help.


Please post the command you are using and the output when it "doesn't
work".  also  the output of a

select * from volhistory where volume_name='XYZ000L3'  - with your
volume of interest substituted

Thanks

Steve

Steven Harris
TSM Administrator, Sydney Australia




 KIRAN-SYSTEMS
  To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
      Re: [ADSM-L] How to delete
   Volhistory...

 16/01/2009 04:12
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






The below command is not working for me.Iam using TSM Server 5.5.0

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Robben Leaf
Sent: Friday, January 09, 2009 1:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to delete Volhistory...

Not entirely true. The product doesn't provide a DOCUMENTED way to do
this.

There are some undocumented parameters for the DELETE VOLHIST command.
Specifically, you can add "vol=VOLNAME force=yes" to the command to remove
the volume forcibly from the volhistory.

We have found this command necessary when our library manager thinks
another TSM server instance still owns a tape, when that instance has
forgotten all about it.

Robben Leaf




From:
Richard Sims 
To:
ADSM-L@VM.MARIST.EDU
Date:
01/08/2009 06:14 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
"ADSM: Dist Stor Manager" 



On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:

> Please let me know how to delete volume history of a particular
> Volume.

The product does not provide a way to do this.

Richard Sims



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications
privacy
laws, and is also confidential and proprietary in nature. If you are not
the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you
have
received this communication in error, and then immediately delete it. Thank
you in advance for your cooperation.



-


Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind of
disclosure whatsoever and is intended solely for the use of addressee (s).
If you are not the intended recipient, kindly inform us by return e-mail
and also kindly disregard the contents of the e-mail, delete the original
message and destroy any copies thereof immediately. You are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize
the risk of transmission of computer viruses with this e-mail; DQE is not
liable for any damage you may sustain as a result of any virus in this
e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE
reserves the right to monitor and review the content of all messages sent
to or from this e-mail address


Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind of
disclosure whatsoever and is intended solely for the use of addressee (s).
If you are not the intended recipient, kindly inform us by return e-mail and
also kindly disregard the contents of the e-mail, delete the original
message and destroy any copies thereof immediately. You are notified that
any dissemination,

Re: How to delete Volhistory...

[Maria Ilieva]

Try audit library X checklabel=barcode  from the library client.
That worked for me.

Maria Ilieva


On Fri, Jan 16, 2009 at 8:14 AM, KIRAN-SYSTEMS
 wrote:
> I am using the below command to delete volhis of a library client server
> from library manager server
>
> Del volhis vol= force=yes
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Steven Harris
> Sent: Friday, January 16, 2009 11:24 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] How to delete Volhistory...
>
> We need detail Kiran, if we are to help.
>
>
> Please post the command you are using and the output when it "doesn't
> work".  also  the output of a
>
> select * from volhistory where volume_name='XYZ000L3'  - with your
> volume of interest substituted
>
> Thanks
>
> Steve
>
> Steven Harris
> TSM Administrator, Sydney Australia
>
>
>
>
> KIRAN-SYSTEMS
>  NMENT.COM> To
> Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
> Dist Stor  cc
> Manager"
>  .EDU> Re: [ADSM-L] How to delete
>   Volhistory...
>
> 16/01/2009 04:12
> PM
>
>
> Please respond to
> "ADSM: Dist Stor
> Manager"
>.EDU>
>
>
>
>
>
>
> The below command is not working for me.Iam using TSM Server 5.5.0
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Robben Leaf
> Sent: Friday, January 09, 2009 1:02 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] How to delete Volhistory...
>
> Not entirely true. The product doesn't provide a DOCUMENTED way to do
> this.
>
> There are some undocumented parameters for the DELETE VOLHIST command.
> Specifically, you can add "vol=VOLNAME force=yes" to the command to remove
> the volume forcibly from the volhistory.
>
> We have found this command necessary when our library manager thinks
> another TSM server instance still owns a tape, when that instance has
> forgotten all about it.
>
> Robben Leaf
>
>
>
>
> From:
> Richard Sims 
> To:
> ADSM-L@VM.MARIST.EDU
> Date:
> 01/08/2009 06:14 AM
> Subject:
> Re: [ADSM-L] How to delete Volhistory...
> Sent by:
> "ADSM: Dist Stor Manager" 
>
>
>
> On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:
>
>> Please let me know how to delete volume history of a particular
>> Volume.
>
> The product does not provide a way to do this.
>
>Richard Sims
>
>
>
> U.S. BANCORP made the following annotations
> -
> Electronic Privacy Notice. This e-mail, and any attachments, contains
> information that is, or may be, covered by electronic communications
> privacy
> laws, and is also confidential and proprietary in nature. If you are not
> the
> intended recipient, please be advised that you are legally prohibited from
> retaining, using, copying, distributing, or otherwise disclosing this
> information in any manner. Instead, please reply to the sender that you
> have
> received this communication in error, and then immediately delete it. Thank
> you in advance for your cooperation.
>
>
>
> -
>
>
> Disclaimer:
> This email message (including attachments if any) may contain privileged,
> proprietary, confidential information, which may be exempt from any kind of
> disclosure whatsoever and is intended solely for the use of addressee (s).
> If you are not the intended recipient, kindly inform us by return e-mail
> and also kindly disregard the contents of the e-mail, delete the original
> message and destroy any copies thereof immediately. You are notified that
> any dissemination, distribution or copying of this communication is
> strictly prohibited unless approved by the sender.
>
> DQ Entertainment (DQE) has taken every reasonable precaution to minimize
> the risk of transmission of computer viruses with this e-mail; DQE is not
> liable for any damage you may sustain as a result of any virus in this
> e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE
> reserves the right to monitor and review the content of all messages sent
> to or from this e-mail address
>
>
> Disclaimer:
> Thi

Re: How to delete Volhistory...

[KIRAN-SYSTEMS]

I am using the below command to delete volhis of a library client server
from library manager server

Del volhis vol= force=yes


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Steven Harris
Sent: Friday, January 16, 2009 11:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to delete Volhistory...

We need detail Kiran, if we are to help.


Please post the command you are using and the output when it "doesn't
work".  also  the output of a

select * from volhistory where volume_name='XYZ000L3'  - with your
volume of interest substituted

Thanks

Steve

Steven Harris
TSM Administrator, Sydney Australia




 KIRAN-SYSTEMS
  To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
      Re: [ADSM-L] How to delete
   Volhistory...

 16/01/2009 04:12
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






The below command is not working for me.Iam using TSM Server 5.5.0

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Robben Leaf
Sent: Friday, January 09, 2009 1:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to delete Volhistory...

Not entirely true. The product doesn't provide a DOCUMENTED way to do
this.

There are some undocumented parameters for the DELETE VOLHIST command.
Specifically, you can add "vol=VOLNAME force=yes" to the command to remove
the volume forcibly from the volhistory.

We have found this command necessary when our library manager thinks
another TSM server instance still owns a tape, when that instance has
forgotten all about it.

Robben Leaf




From:
Richard Sims 
To:
ADSM-L@VM.MARIST.EDU
Date:
01/08/2009 06:14 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
"ADSM: Dist Stor Manager" 



On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:

> Please let me know how to delete volume history of a particular
> Volume.

The product does not provide a way to do this.

Richard Sims



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications
privacy
laws, and is also confidential and proprietary in nature. If you are not
the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you
have
received this communication in error, and then immediately delete it. Thank
you in advance for your cooperation.



-


Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind of
disclosure whatsoever and is intended solely for the use of addressee (s).
If you are not the intended recipient, kindly inform us by return e-mail
and also kindly disregard the contents of the e-mail, delete the original
message and destroy any copies thereof immediately. You are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize
the risk of transmission of computer viruses with this e-mail; DQE is not
liable for any damage you may sustain as a result of any virus in this
e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE
reserves the right to monitor and review the content of all messages sent
to or from this e-mail address


Disclaimer:
This email message (including attachments if any) may contain privileged, 
proprietary, confidential information, which may be exempt from any kind of 
disclosure whatsoever and is intended solely for the use of addressee (s). If 
you are not the intended recipient, kindly inform us by return e-mail and also 
kindly disregard the contents of the e-mail, delete the original message and 
destroy any copies thereof immediately. You are notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the 
risk of transmission of computer viruses with this e-mail; DQE is not liable 
for any damage you may sustain as a result of any virus in this e-mail. DQE 
shall not be liable for the views expressed in the e-mail. DQE reserves the 
right to

Re: How to delete Volhistory...

[Steven Harris]

We need detail Kiran, if we are to help.


Please post the command you are using and the output when it "doesn't
work".  also  the output of a

select * from volhistory where volume_name='XYZ000L3'  - with your
volume of interest substituted

Thanks

Steve

Steven Harris
TSM Administrator, Sydney Australia




 KIRAN-SYSTEMS
  To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
      Re: [ADSM-L] How to delete
   Volhistory...

 16/01/2009 04:12
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






The below command is not working for me.Iam using TSM Server 5.5.0

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Robben Leaf
Sent: Friday, January 09, 2009 1:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to delete Volhistory...

Not entirely true. The product doesn't provide a DOCUMENTED way to do
this.

There are some undocumented parameters for the DELETE VOLHIST command.
Specifically, you can add "vol=VOLNAME force=yes" to the command to remove
the volume forcibly from the volhistory.

We have found this command necessary when our library manager thinks
another TSM server instance still owns a tape, when that instance has
forgotten all about it.

Robben Leaf




From:
Richard Sims 
To:
ADSM-L@VM.MARIST.EDU
Date:
01/08/2009 06:14 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
"ADSM: Dist Stor Manager" 



On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:

> Please let me know how to delete volume history of a particular
> Volume.

The product does not provide a way to do this.

Richard Sims



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications
privacy
laws, and is also confidential and proprietary in nature. If you are not
the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you
have
received this communication in error, and then immediately delete it. Thank
you in advance for your cooperation.



-


Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind of
disclosure whatsoever and is intended solely for the use of addressee (s).
If you are not the intended recipient, kindly inform us by return e-mail
and also kindly disregard the contents of the e-mail, delete the original
message and destroy any copies thereof immediately. You are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize
the risk of transmission of computer viruses with this e-mail; DQE is not
liable for any damage you may sustain as a result of any virus in this
e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE
reserves the right to monitor and review the content of all messages sent
to or from this e-mail address

Re: How to delete Volhistory...

[KIRAN-SYSTEMS]

The below command is not working for me.Iam using TSM Server 5.5.0

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Robben Leaf
Sent: Friday, January 09, 2009 1:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to delete Volhistory...

Not entirely true. The product doesn't provide a DOCUMENTED way to do
this.

There are some undocumented parameters for the DELETE VOLHIST command.
Specifically, you can add "vol=VOLNAME force=yes" to the command to remove
the volume forcibly from the volhistory.

We have found this command necessary when our library manager thinks
another TSM server instance still owns a tape, when that instance has
forgotten all about it.

Robben Leaf




From:
Richard Sims 
To:
ADSM-L@VM.MARIST.EDU
Date:
01/08/2009 06:14 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
"ADSM: Dist Stor Manager" 



On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:

> Please let me know how to delete volume history of a particular
> Volume.

The product does not provide a way to do this.

Richard Sims



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications privacy
laws, and is also confidential and proprietary in nature. If you are not the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you have
received this communication in error, and then immediately delete it. Thank
you in advance for your cooperation.



-


Disclaimer:
This email message (including attachments if any) may contain privileged, 
proprietary, confidential information, which may be exempt from any kind of 
disclosure whatsoever and is intended solely for the use of addressee (s). If 
you are not the intended recipient, kindly inform us by return e-mail and also 
kindly disregard the contents of the e-mail, delete the original message and 
destroy any copies thereof immediately. You are notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the 
risk of transmission of computer viruses with this e-mail; DQE is not liable 
for any damage you may sustain as a result of any virus in this e-mail. DQE 
shall not be liable for the views expressed in the e-mail. DQE reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail address

Re: How to delete Volhistory...

[KIRAN-SYSTEMS]

Thanks for the information. I am facing the same issue with the tapes with
shared library owing to the client server.


Regards,
Kiran.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Robben Leaf
Sent: Friday, January 09, 2009 1:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to delete Volhistory...

Not entirely true. The product doesn't provide a DOCUMENTED way to do
this.

There are some undocumented parameters for the DELETE VOLHIST command.
Specifically, you can add "vol=VOLNAME force=yes" to the command to remove
the volume forcibly from the volhistory.

We have found this command necessary when our library manager thinks
another TSM server instance still owns a tape, when that instance has
forgotten all about it.

Robben Leaf




From:
Richard Sims 
To:
ADSM-L@VM.MARIST.EDU
Date:
01/08/2009 06:14 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
"ADSM: Dist Stor Manager" 



On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:

> Please let me know how to delete volume history of a particular
> Volume.

The product does not provide a way to do this.

Richard Sims



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications privacy
laws, and is also confidential and proprietary in nature. If you are not the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you have
received this communication in error, and then immediately delete it. Thank
you in advance for your cooperation.



-


Disclaimer:
This email message (including attachments if any) may contain privileged, 
proprietary, confidential information, which may be exempt from any kind of 
disclosure whatsoever and is intended solely for the use of addressee (s). If 
you are not the intended recipient, kindly inform us by return e-mail and also 
kindly disregard the contents of the e-mail, delete the original message and 
destroy any copies thereof immediately. You are notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the 
risk of transmission of computer viruses with this e-mail; DQE is not liable 
for any damage you may sustain as a result of any virus in this e-mail. DQE 
shall not be liable for the views expressed in the e-mail. DQE reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail address

Re: How to delete Volhistory...

[Robben Leaf]

Not entirely true. The product doesn't provide a DOCUMENTED way to do
this.

There are some undocumented parameters for the DELETE VOLHIST command.
Specifically, you can add "vol=VOLNAME force=yes" to the command to remove
the volume forcibly from the volhistory.

We have found this command necessary when our library manager thinks
another TSM server instance still owns a tape, when that instance has
forgotten all about it.

Robben Leaf




From:
Richard Sims 
To:
ADSM-L@VM.MARIST.EDU
Date:
01/08/2009 06:14 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
"ADSM: Dist Stor Manager" 



On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:

> Please let me know how to delete volume history of a particular
> Volume.

The product does not provide a way to do this.

Richard Sims



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-

Re: How to delete Volhistory...

[Bob Levad]

Kiran,

This worked for me for a backupset.  I don't know if it will work for your
particular case.  The volume was a FILE type volume that no longer existed.

DELETE VOLHISTORY type=backupset volume=D:\88894302.OST force=yes
todate=today

Bob

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
KIRAN-SYSTEMS
Sent: Wednesday, January 07, 2009 11:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] How to delete Volhistory...

Hi,



Please let me know how to delete volume history of a particular Volume.



Regards,

Kiran.

Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind of
disclosure whatsoever and is intended solely for the use of addressee (s).
If you are not the intended recipient, kindly inform us by return e-mail and
also kindly disregard the contents of the e-mail, delete the original
message and destroy any copies thereof immediately. You are notified that
any dissemination, distribution or copying of this communication is strictly
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the
risk of transmission of computer viruses with this e-mail; DQE is not liable
for any damage you may sustain as a result of any virus in this e-mail. DQE
shall not be liable for the views expressed in the e-mail. DQE reserves the
right to monitor and review the content of all messages sent to or from this
e-mail address

This electronic transmission and any documents accompanying this electronic 
transmission contain confidential information belonging to the sender.  This 
information may be legally privileged.  The information is intended only for 
the use of the individual or entity named above.  If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, distribution, 
or the taking of any action in reliance on or regarding the contents of this 
electronically transmitted information is strictly prohibited.

Re: How to delete Volhistory...

[Richard Sims]

On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:


Please let me know how to delete volume history of a particular
Volume.


The product does not provide a way to do this.

   Richard Sims

How to delete Volhistory...

[KIRAN-SYSTEMS]

Hi,



Please let me know how to delete volume history of a particular Volume.



Regards,

Kiran.

Disclaimer:
This email message (including attachments if any) may contain privileged, 
proprietary, confidential information, which may be exempt from any kind of 
disclosure whatsoever and is intended solely for the use of addressee (s). If 
you are not the intended recipient, kindly inform us by return e-mail and also 
kindly disregard the contents of the e-mail, delete the original message and 
destroy any copies thereof immediately. You are notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize the 
risk of transmission of computer viruses with this e-mail; DQE is not liable 
for any damage you may sustain as a result of any virus in this e-mail. DQE 
shall not be liable for the views expressed in the e-mail. DQE reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail address

Re: Help DELETE VOLHISTORY

[Remco Post]

Rushforth, Tim wrote:
> That sounds similar to a problem we had years ago (APAR IC30429) - have
> you tried the "FORCE=YES" option.
>

I is exactly what I see on one of our servers:

tsm: BASKET>q volhist t=dbs

Date/TimeVolume TypeBackupBackup
Volume Device Class Volume NameVolume
LocationCommand
Series Operation
Seq

 -- -- -
--  --
-- --
05/23/2006 08:18:09  DBSNAPSHOT449 0
  1 9940B200894

05/24/2006 08:18:05  DBSNAPSHOT450 0
  1 9940B204480

05/25/2006 08:18:26  DBSNAPSHOT451 0
  1 9940B203142

04/01/2007 08:17:20  DBSNAPSHOT302 0
  1 9940B204626

04/03/2007 08:17:33  DBSNAPSHOT303 0
  1 9940B201304

04/04/2007 08:20:33  DBSNAPSHOT304 0
  1 9940B200869

04/05/2007 08:17:39  DBSNAPSHOT305 0
  1 9940B201297


using force=yes solved my problem for these 3 dbs volumes, thanks!

(I am using server version 5.3.4.1, which is a tad more recent than the
apar fix!)


> Tim Rushforth
> City of Winnipeg
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> TSM User
> Sent: Friday, March 30, 2007 12:44 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Help DELETE VOLHISTORY
>
> No, he is not most recent. She is but the old one.
> See the Volhistory...
>
> select * from volhistORY where type = 'BACKUPFULL'
>
>
>
>DATE_TIME: 2007-02-23 09:40:03.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 117
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.4
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-02 09:03:38.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 118
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.5
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-22 15:45:12.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 2
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.2
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-23 08:46:31.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 3
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.3
>
> LOCATION:
>
>
> On 3/30/07, Lee, Gary D. <[EMAIL PROTECTED]> wrote:
>> I'm guessing that this is your most recent db backup.
>> If that is the case, you can't delete it.  If you really must, then do
>> another db backup then you will be able to delete.
>>
>>
>> Gary Lee
>> Senior System Programmer
>> Ball State University
>> phone: 765-285-1310
>>
>>
>> -Original Message-
>> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Of
>> TSM User
>> Sent: Friday, March 30, 2007 11:46 AM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Help DELETE VOLHISTORY
>>
>> Somebody can help me with this?
>>
>> I need to eliminate volume DB.BACKUP.4.
>>
>> delete volhistory todate=today-30 type=DBBackup
>>
>> It does not eliminate it.
>>
>> I suppose that it is by "BACKUP_SERIES".
>>
>>
>>
>> select * from volhistORY where type = 'BACKUPFULL'
>>
>>
>>
>>DATE_TIME: 2007-02-23 09:40:03.00
>>
>>   UNIQUE: 0
>>
>> TYPE: BACKUPFULL
>>
>>BACKUP_SERIES: 117
>>
>> BACKUP_OPERATION: 0
>>
>>   VOLUME_SEQ: 1
>>
>> DEVCLASS: LTOCLASS1
>>
>>  VOLUME_NAME: DB.BACKUP.4
>>
>> LOCATION:
>>
>>  COMMAND:
>>
>>
>>
>>DATE_TIME: 2007-03-02 09:03:38.00
>>
>>   

Re: Help DELETE VOLHISTORY

[Sung Y Lee]

Can you verify the current date of your TSM server with "show time"?

Sung

"ADSM: Dist Stor Manager"  wrote on 03/30/2007
11:46:07 AM:

> Somebody can help me with this?
>
> I need to eliminate volume DB.BACKUP.4.
>
> delete volhistory todate=today-30 type=DBBackup
>
> It does not eliminate it.
>
> I suppose that it is by "BACKUP_SERIES".
>
>
>
> select * from volhistORY where type = 'BACKUPFULL'
>
>
>
>DATE_TIME: 2007-02-23 09:40:03.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 117
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.4
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-02 09:03:38.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 118
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.5
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-22 15:45:12.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 2
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.2
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-23 08:46:31.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 3
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.3
>
> LOCATION:

Re: Help DELETE VOLHISTORY

[Richard Sims]

On Mar 30, 2007, at 2:11 PM, TSM User wrote:


*ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
successfully deleted*





   DEVCLASS: LTOCLASS1
VOLUME_NAME: DB.BACKUP.4


I get the impression that there are site configuration factors you
aren't telling us.  That volume name is very peculiar (wrong) for an
LTO cartridge, which is to say not a 6 character volser, or that plus
a 2-character type identifier.  If you're doing Library Client stuff,
see "Deleting a library volume on the Library Manager" in redbook
"Get More Out of Your SAN with IBM Tivoli Storage Manager", where the
Delete has an additional keyword.  Otherwise, you need to determine
why you're getting volume names like that, relative to your
configuration.  (And, of course, do not use DELete VOLHistory if DRM
is being employed.)

   Richard Sims

Re: Help DELETE VOLHISTORY

[TSM User]

*ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
successfully deleted*

On 3/30/07, Richard Sims <[EMAIL PROTECTED]> wrote:


On Mar 30, 2007, at 11:46 AM, TSM User wrote:

> I need to eliminate volume DB.BACKUP.4.
>
> delete volhistory todate=today-30 type=DBBackup
>
> It does not eliminate it.

Error message?

Re: Help DELETE VOLHISTORY

[Richard Sims]

On Mar 30, 2007, at 11:46 AM, TSM User wrote:


I need to eliminate volume DB.BACKUP.4.

delete volhistory todate=today-30 type=DBBackup

It does not eliminate it.


Error message?

Re: Help DELETE VOLHISTORY

[Rushforth, Tim]

That sounds similar to a problem we had years ago (APAR IC30429) - have
you tried the "FORCE=YES" option.

Tim Rushforth
City of Winnipeg

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
TSM User
Sent: Friday, March 30, 2007 12:44 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Help DELETE VOLHISTORY

No, he is not most recent. She is but the old one.
See the Volhistory...

select * from volhistORY where type = 'BACKUPFULL'



   DATE_TIME: 2007-02-23 09:40:03.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 117

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.4

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-02 09:03:38.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 118

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.5

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-22 15:45:12.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 2

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.2

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-23 08:46:31.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 3

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.3

LOCATION:


On 3/30/07, Lee, Gary D. <[EMAIL PROTECTED]> wrote:
>
> I'm guessing that this is your most recent db backup.
> If that is the case, you can't delete it.  If you really must, then do
> another db backup then you will be able to delete.
>
>
> Gary Lee
> Senior System Programmer
> Ball State University
> phone: 765-285-1310
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
> TSM User
> Sent: Friday, March 30, 2007 11:46 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Help DELETE VOLHISTORY
>
> Somebody can help me with this?
>
> I need to eliminate volume DB.BACKUP.4.
>
> delete volhistory todate=today-30 type=DBBackup
>
> It does not eliminate it.
>
> I suppose that it is by "BACKUP_SERIES".
>
>
>
> select * from volhistORY where type = 'BACKUPFULL'
>
>
>
>DATE_TIME: 2007-02-23 09:40:03.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 117
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.4
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-02 09:03:38.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 118
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.5
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-22 15:45:12.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 2
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.2
>
> LOCATION:
>
>  COMMAND:
>
>
>
>DATE_TIME: 2007-03-23 08:46:31.00
>
>   UNIQUE: 0
>
> TYPE: BACKUPFULL
>
>BACKUP_SERIES: 3
>
> BACKUP_OPERATION: 0
>
>   VOLUME_SEQ: 1
>
> DEVCLASS: LTOCLASS1
>
>  VOLUME_NAME: DB.BACKUP.3
>
> LOCATION:
>

Re: Help DELETE VOLHISTORY

[TSM User]

No, he is not most recent. She is but the old one.
See the Volhistory…

select * from volhistORY where type = 'BACKUPFULL'



  DATE_TIME: 2007-02-23 09:40:03.00

 UNIQUE: 0

   TYPE: BACKUPFULL

  BACKUP_SERIES: 117

BACKUP_OPERATION: 0

 VOLUME_SEQ: 1

   DEVCLASS: LTOCLASS1

VOLUME_NAME: DB.BACKUP.4

   LOCATION:

COMMAND:



  DATE_TIME: 2007-03-02 09:03:38.00

 UNIQUE: 0

   TYPE: BACKUPFULL

  BACKUP_SERIES: 118

BACKUP_OPERATION: 0

 VOLUME_SEQ: 1

   DEVCLASS: LTOCLASS1

VOLUME_NAME: DB.BACKUP.5

   LOCATION:

COMMAND:



  DATE_TIME: 2007-03-22 15:45:12.00

 UNIQUE: 0

   TYPE: BACKUPFULL

  BACKUP_SERIES: 2

BACKUP_OPERATION: 0

 VOLUME_SEQ: 1

   DEVCLASS: LTOCLASS1

VOLUME_NAME: DB.BACKUP.2

   LOCATION:

COMMAND:



  DATE_TIME: 2007-03-23 08:46:31.00

 UNIQUE: 0

   TYPE: BACKUPFULL

  BACKUP_SERIES: 3

BACKUP_OPERATION: 0

 VOLUME_SEQ: 1

   DEVCLASS: LTOCLASS1

VOLUME_NAME: DB.BACKUP.3

   LOCATION:


On 3/30/07, Lee, Gary D. <[EMAIL PROTECTED]> wrote:


I'm guessing that this is your most recent db backup.
If that is the case, you can't delete it.  If you really must, then do
another db backup then you will be able to delete.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
TSM User
Sent: Friday, March 30, 2007 11:46 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Help DELETE VOLHISTORY

Somebody can help me with this?

I need to eliminate volume DB.BACKUP.4.

delete volhistory todate=today-30 type=DBBackup

It does not eliminate it.

I suppose that it is by "BACKUP_SERIES".



select * from volhistORY where type = 'BACKUPFULL'



   DATE_TIME: 2007-02-23 09:40:03.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 117

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.4

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-02 09:03:38.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 118

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.5

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-22 15:45:12.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 2

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.2

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-23 08:46:31.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 3

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.3

LOCATION:

Re: Help DELETE VOLHISTORY

[Lee, Gary D.]

I'm guessing that this is your most recent db backup.
If that is the case, you can't delete it.  If you really must, then do
another db backup then you will be able to delete. 


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
TSM User
Sent: Friday, March 30, 2007 11:46 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Help DELETE VOLHISTORY

Somebody can help me with this?

I need to eliminate volume DB.BACKUP.4.

delete volhistory todate=today-30 type=DBBackup

It does not eliminate it.

I suppose that it is by "BACKUP_SERIES".



select * from volhistORY where type = 'BACKUPFULL'



   DATE_TIME: 2007-02-23 09:40:03.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 117

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.4

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-02 09:03:38.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 118

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.5

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-22 15:45:12.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 2

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.2

LOCATION:

 COMMAND:



   DATE_TIME: 2007-03-23 08:46:31.00

  UNIQUE: 0

TYPE: BACKUPFULL

   BACKUP_SERIES: 3

BACKUP_OPERATION: 0

  VOLUME_SEQ: 1

DEVCLASS: LTOCLASS1

 VOLUME_NAME: DB.BACKUP.3

LOCATION:

Help DELETE VOLHISTORY

[TSM User]

Somebody can help me with this?

I need to eliminate volume DB.BACKUP.4.

delete volhistory todate=today-30 type=DBBackup

It does not eliminate it.

I suppose that it is by "BACKUP_SERIES".



select * from volhistORY where type = 'BACKUPFULL'



  DATE_TIME: 2007-02-23 09:40:03.00

 UNIQUE: 0

   TYPE: BACKUPFULL

  BACKUP_SERIES: 117

BACKUP_OPERATION: 0

 VOLUME_SEQ: 1

   DEVCLASS: LTOCLASS1

VOLUME_NAME: DB.BACKUP.4

   LOCATION:

COMMAND:



  DATE_TIME: 2007-03-02 09:03:38.00

 UNIQUE: 0

   TYPE: BACKUPFULL

  BACKUP_SERIES: 118

BACKUP_OPERATION: 0

 VOLUME_SEQ: 1

   DEVCLASS: LTOCLASS1

VOLUME_NAME: DB.BACKUP.5

   LOCATION:

COMMAND:



  DATE_TIME: 2007-03-22 15:45:12.00

 UNIQUE: 0

   TYPE: BACKUPFULL

  BACKUP_SERIES: 2

BACKUP_OPERATION: 0

 VOLUME_SEQ: 1

   DEVCLASS: LTOCLASS1

VOLUME_NAME: DB.BACKUP.2

   LOCATION:

COMMAND:



  DATE_TIME: 2007-03-23 08:46:31.00

 UNIQUE: 0

   TYPE: BACKUPFULL

  BACKUP_SERIES: 3

BACKUP_OPERATION: 0

 VOLUME_SEQ: 1

   DEVCLASS: LTOCLASS1

VOLUME_NAME: DB.BACKUP.3

   LOCATION:

delete volhistory

[Mark Strasheim]

thanks to all,
the hint with force=yes did the job.
But i have an otherone for you :).

The very first backup ever made, was done in the future ( well the server date was 
wrong )
it was/will be done on NOV 16 2004. Since the admin (me) is a funny guy, he set the 
new Date,
while the tape got moved to the takeaway bay. After restarting the TSM server, the 
tape was
still in the library. 
with this stats 
Library Name Volume Name Status Owner  Last Use  Home  
  Device
 Element   
  Type  
 --- -- -- - ---   
  --
4560SLXLIB   AKZ900L1Private 32


the status ist Private but i has no use anymore .. i have done almost anything i can 
imagine, but 
the status stays the same. 
More over my log points out that: 
--

ANRD date.c(986): ThreadId<28> Date 2004/8/20 is LESS THAN 2004/11/16.
Callchain of previous message: 0x08795893
outDiagf+0x203 <- 0x08782462  SubDate+0x142 <- 0x08110289  AdmQueryNode+0xdd9 <- 
0x080a8771  AdmCommandLocal+0x711 <-
0x080a802c  admCommand+0x123c <- 0x0869777e  SmAdminCommandThread+0x3e <- 0x0809c57f  
StartThread+0x8f <- 0x40062020
*UNKNOWN* <- 0x4013eeca  *UNKNOWN* <-
--
does that mean anything to someone 
I have restarted the server, but this message stays.
I guess if i get rid of one of them, the other will vanish as well.

best regrad
Mark Strasheim

--

definitiv! business applications GmbH & Co. KG
Fresnostrasse 14 - 18 · DE-48159 Münster
Tel. +49 (0) 251 21092 - 23 · Fax +49 (0) 251 21092 - 29
 mailto:[EMAIL PROTECTED] ·
 http://www.definitiv-ba.de

--

Re: Error during "delete volhistory"

[Paul Ripke]

On Thursday, January 16, 2003, at 11:18 PM, Raghu S wrote:

Hi

There is no


del volhist type=backupset command


See other posts - it's undocumented, but does exist.


use >del backupset   command to delete backup
sets.You can use preview option also.


Sorry, backupset expired, I believe. It just didn't remove the volume
entries from the volhistory table. I tried re-defining the backupset,
but couldn't as the tapes were in use.

Cheers,
--
Paul Ripke
Unix/OpenVMS/DBA
101 reasons why you can't find your Sysadmin:
68: It's 9AM. He/She is not working that late.
-- Koos van den Hout

Re: Error during "delete volhistory"

[Paul Ripke]

On Friday, January 17, 2003, at 01:30 AM, Mark Stapleton wrote:

On Thu, 2003-01-16 at 06:18, Raghu S wrote:

There is no


del volhist type=backupset command


While type=backupset is not listed as an option, it does work. It is a
holdover from version 4.1 days. There was a bug in the 4.2 days that
prevented some backupsets from being deleted with the DEL BACKUPSET
command; you could delete them with

del volh type=backupset volume= todate=

which is also undocumented, I believe.


That's correct. I've used it in the past to delete single-volume
backupsets successfully. In this case, it fails with the error in
my original post. I figure I'll have to raise this with Tivoli
directly.

Cheers,
--
Paul Ripke
Unix/OpenVMS/DBA
101 reasons why you can't find your Sysadmin:
68: It's 9AM. He/She is not working that late.
-- Koos van den Hout

Re: Error during "delete volhistory"

[Mark Stapleton]

On Thu, 2003-01-16 at 06:18, Raghu S wrote:
> There is no
>
> >del volhist type=backupset command

While type=backupset is not listed as an option, it does work. It is a
holdover from version 4.1 days. There was a bug in the 4.2 days that
prevented some backupsets from being deleted with the DEL BACKUPSET
command; you could delete them with

del volh type=backupset volume= todate=

which is also undocumented, I believe.

--
Mark Stapleton ([EMAIL PROTECTED])

Re: Error during "delete volhistory"

[Raghu S]

Hi

There is no

>del volhist type=backupset command

use >del backupset   command to delete backup
sets.You can use preview option also.


regards

Raghu



John Naylor
 cc:
Sent by: "ADSM: Dist Stor  Subject: Re: Error during 
"delete volhistory"
Manager"
<[EMAIL PROTECTED]>


01/14/2003 04:59 PM
Please respond to "ADSM:
Dist Stor Manager"





Paul,
You could try
del volh tod=today vol=xx type=backupset force=yes
(only the first volume in sequence is required the others will delete
automatically)




Paul Ripke <[EMAIL PROTECTED]> on 01/13/2003 06:58:04 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Error during "delete volhistory"



Anyone know how to delete multi-volume backupsets from volhistory?
BTW, server is 4.1.3.0 (waiting on my spare time for an upgrade...)

tsm: BHPS>q volhist ty=backupset

   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 1
Device Class: 3590
 Volume Name: SP0064
 Volume Location:
 Command: generate backupset ISDWOL-ES2 es2-fdrive \\isdwol-es2\f$
devcla=3590 scrat=y retent=90

   Date/Time: 09/19/02   12:34:34
...
   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 9
Device Class: 3590
 Volume Name: SP0469
 Volume Location:
 Command:

Actlog output looks ominous:
ANR2017I Administrator WERIPP issued command: DELETE VOLHISTORY
typ=backupset volu=SP0064 force=yes todate=today
ANRD tb.c(2029): Invalid Encoded Key Length
ANR0106E imarqry.c(3069): Unexpected error 100 fetching row in table
"Archive.Descriptions".
ANRD icvolhst.c(3473): Volume SP0064 initially found no longer exists
during volume deletion.
ANR2468E DELETE VOLHISTORY: An internal server error was encountered while
deleting server sequential volume history information.
ANR2017I Administrator WERIPP issued command: ROLLBACK

Tried first and last tape of the series, with same results.
A comma-separated list generated a "no such volume" type error.

Cheers,
--
Paul Ripke
UNIX/OpenVMS Sysadmin
CSC, Port Kembla 2502, NSW, Australia
Phone +61 2 4275 4101
Fax +61 2 4275 7801
Mobile +61 419 432 517
101 reasons why you can't find your Sysadmin:
68. It's 9 AM. He/she is not working that late.
-- Koos van den Hout




This email, including any attachments, is intended only for use by the
addressee(s) and may contain confidential and/or personal information and
may also be the subject of legal privilege. Any personal information
contained in this email is not to be used or disclosed for any purpose
other than the purpose for which you have received it. If you are not the
intended recipient, you must not disclose or use the information contained
in it. In this case, please let me know by return email, delete the message
permanently from your system and destroy any copies.










**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Re: Error during "delete volhistory"

[Paul Ripke]

John,

That's pretty much the command I used, displayed in the actlog below...

Cheers,
--
Paul

John Naylor <[EMAIL PROTECTED]> on 14/01/2003 22:29:

Paul,
You could try
del volh tod=today vol=xx type=backupset force=yes
(only the first volume in sequence is required the others will delete
automatically)

Paul Ripke <[EMAIL PROTECTED]> on 01/13/2003 06:58:04 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Error during "delete volhistory"


Anyone know how to delete multi-volume backupsets from volhistory?
BTW, server is 4.1.3.0 (waiting on my spare time for an upgrade...)

tsm: BHPS>q volhist ty=backupset

   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 1
Device Class: 3590
 Volume Name: SP0064
 Volume Location:
 Command: generate backupset ISDWOL-ES2 es2-fdrive \\isdwol-es2\f$
devcla=3590 scrat=y retent=90

   Date/Time: 09/19/02   12:34:34
...
   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 9
Device Class: 3590
 Volume Name: SP0469
 Volume Location:
 Command:

Actlog output looks ominous:
ANR2017I Administrator WERIPP issued command: DELETE VOLHISTORY
typ=backupset volu=SP0064 force=yes todate=today
ANRD tb.c(2029): Invalid Encoded Key Length
ANR0106E imarqry.c(3069): Unexpected error 100 fetching row in table
"Archive.Descriptions".
ANRD icvolhst.c(3473): Volume SP0064 initially found no longer exists
during volume deletion.
ANR2468E DELETE VOLHISTORY: An internal server error was encountered while
deleting server sequential volume history information.
ANR2017I Administrator WERIPP issued command: ROLLBACK

Tried first and last tape of the series, with same results.
A comma-separated list generated a "no such volume" type error.

Cheers,
--
Paul Ripke

Re: Error during "delete volhistory"

[John Naylor]

Paul,
You could try
del volh tod=today vol=xx type=backupset force=yes
(only the first volume in sequence is required the others will delete
automatically)




Paul Ripke <[EMAIL PROTECTED]> on 01/13/2003 06:58:04 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Error during "delete volhistory"



Anyone know how to delete multi-volume backupsets from volhistory?
BTW, server is 4.1.3.0 (waiting on my spare time for an upgrade...)

tsm: BHPS>q volhist ty=backupset

   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 1
Device Class: 3590
 Volume Name: SP0064
 Volume Location:
 Command: generate backupset ISDWOL-ES2 es2-fdrive \\isdwol-es2\f$
devcla=3590 scrat=y retent=90

   Date/Time: 09/19/02   12:34:34
...
   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 9
Device Class: 3590
 Volume Name: SP0469
 Volume Location:
 Command:

Actlog output looks ominous:
ANR2017I Administrator WERIPP issued command: DELETE VOLHISTORY
typ=backupset volu=SP0064 force=yes todate=today
ANRD tb.c(2029): Invalid Encoded Key Length
ANR0106E imarqry.c(3069): Unexpected error 100 fetching row in table
"Archive.Descriptions".
ANRD icvolhst.c(3473): Volume SP0064 initially found no longer exists
during volume deletion.
ANR2468E DELETE VOLHISTORY: An internal server error was encountered while
deleting server sequential volume history information.
ANR2017I Administrator WERIPP issued command: ROLLBACK

Tried first and last tape of the series, with same results.
A comma-separated list generated a "no such volume" type error.

Cheers,
--
Paul Ripke
UNIX/OpenVMS Sysadmin
CSC, Port Kembla 2502, NSW, Australia
Phone +61 2 4275 4101
Fax +61 2 4275 7801
Mobile +61 419 432 517
101 reasons why you can't find your Sysadmin:
68. It's 9 AM. He/she is not working that late.
-- Koos van den Hout



This email, including any attachments, is intended only for use by the
addressee(s) and may contain confidential and/or personal information and
may also be the subject of legal privilege. Any personal information
contained in this email is not to be used or disclosed for any purpose
other than the purpose for which you have received it. If you are not the
intended recipient, you must not disclose or use the information contained
in it. In this case, please let me know by return email, delete the message
permanently from your system and destroy any copies.









**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Error during "delete volhistory"

[Paul Ripke]

Anyone know how to delete multi-volume backupsets from volhistory?
BTW, server is 4.1.3.0 (waiting on my spare time for an upgrade...)

tsm: BHPS>q volhist ty=backupset

   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 1
Device Class: 3590
 Volume Name: SP0064
 Volume Location:
 Command: generate backupset ISDWOL-ES2 es2-fdrive \\isdwol-es2\f$
devcla=3590 scrat=y retent=90

   Date/Time: 09/19/02   12:34:34
...
   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 9
Device Class: 3590
 Volume Name: SP0469
 Volume Location:
 Command:

Actlog output looks ominous:
ANR2017I Administrator WERIPP issued command: DELETE VOLHISTORY
typ=backupset volu=SP0064 force=yes todate=today
ANRD tb.c(2029): Invalid Encoded Key Length
ANR0106E imarqry.c(3069): Unexpected error 100 fetching row in table
"Archive.Descriptions".
ANRD icvolhst.c(3473): Volume SP0064 initially found no longer exists
during volume deletion.
ANR2468E DELETE VOLHISTORY: An internal server error was encountered while
deleting server sequential volume history information.
ANR2017I Administrator WERIPP issued command: ROLLBACK

Tried first and last tape of the series, with same results.
A comma-separated list generated a "no such volume" type error.

Cheers,
--
Paul Ripke
UNIX/OpenVMS Sysadmin
CSC, Port Kembla 2502, NSW, Australia
Phone +61 2 4275 4101
Fax +61 2 4275 7801
Mobile +61 419 432 517
101 reasons why you can't find your Sysadmin:
68. It's 9 AM. He/she is not working that late.
-- Koos van den Hout


This email, including any attachments, is intended only for use by the
addressee(s) and may contain confidential and/or personal information and
may also be the subject of legal privilege. Any personal information
contained in this email is not to be used or disclosed for any purpose
other than the purpose for which you have received it. If you are not the
intended recipient, you must not disclose or use the information contained
in it. In this case, please let me know by return email, delete the message
permanently from your system and destroy any copies.

Re: delete volhistory

[Cook, Dwight E]

drop the - in front of the todate... that is a client type format... not an
admin session format !
just
del volhist tod=-30 t=dbb
or t=all or what ever type you want to get rid of

Dwight

-Original Message-
From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 10:14 AM
To: [EMAIL PROTECTED]
Subject: Re: delete volhistory


This is output..


tsm: TSM>delete volhistory  -todate=today-30
ANR2020E DELETE VOLHISTORY: Invalid parameter - -TODATE.
ANS8001I Return code 3.

Administartors Guide  PAge 711 ...says   delete volhistory
todate=today-8


shekhar




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 10/10/2000
10:30:28 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @
X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: delete volhistory

delete volhistory -todate=today-30

 a '-' to indicate an option

>>> [EMAIL PROTECTED] 10/10/00 10:13AM >>>
Where I am wrong ?

tsm: TSM>delete volhistory todate=today-30
ANR2022E DELETE VOLHISTORY: One or more parameters are missing.
ANS8001I Return code 3.

tsm: TSM>help ANR2022E

---


ANR2022E Command: One or more parameters are missing.

Explanation: The specified server command has been entered without all
required parameters.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

Re: delete volhistory

[Shekhar Dhotre]

Thanks ,




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 10/10/2000 10:20:26 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: delete volhistory

you forgot type=all


-Original Message-
From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 10:13 AM
To: [EMAIL PROTECTED]
Subject: delete volhistory


Where I am wrong ?

tsm: TSM>delete volhistory todate=today-30
ANR2022E DELETE VOLHISTORY: One or more parameters are missing.
ANS8001I Return code 3.

tsm: TSM>help ANR2022E

---


ANR2022E Command: One or more parameters are missing.

Explanation: The specified server command has been entered without all
required parameters.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: delete volhistory

[Shekhar Dhotre]

This is output..


tsm: TSM>delete volhistory  -todate=today-30
ANR2020E DELETE VOLHISTORY: Invalid parameter - -TODATE.
ANS8001I Return code 3.

Administartors Guide  PAge 711 ...says   delete volhistory  todate=today-8


shekhar




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 10/10/2000 10:30:28 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: delete volhistory

delete volhistory -todate=today-30

 a '-' to indicate an option

>>> [EMAIL PROTECTED] 10/10/00 10:13AM >>>
Where I am wrong ?

tsm: TSM>delete volhistory todate=today-30
ANR2022E DELETE VOLHISTORY: One or more parameters are missing.
ANS8001I Return code 3.

tsm: TSM>help ANR2022E
---


ANR2022E Command: One or more parameters are missing.

Explanation: The specified server command has been entered without all
required parameters.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

Re: delete volhistory

[Lawrence Clark]

delete volhistory -todate=today-30

 a '-' to indicate an option

>>> [EMAIL PROTECTED] 10/10/00 10:13AM >>>
Where I am wrong ?

tsm: TSM>delete volhistory todate=today-30
ANR2022E DELETE VOLHISTORY: One or more parameters are missing.
ANS8001I Return code 3.

tsm: TSM>help ANR2022E
---


ANR2022E Command: One or more parameters are missing.

Explanation: The specified server command has been entered without all
required parameters.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

Re: delete volhistory

[Remeta, Mark]

you forgot type=all


-Original Message-
From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 10:13 AM
To: [EMAIL PROTECTED]
Subject: delete volhistory


Where I am wrong ?

tsm: TSM>delete volhistory todate=today-30
ANR2022E DELETE VOLHISTORY: One or more parameters are missing.
ANS8001I Return code 3.

tsm: TSM>help ANR2022E

---


ANR2022E Command: One or more parameters are missing.

Explanation: The specified server command has been entered without all
required parameters.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

delete volhistory

[Shekhar Dhotre]

Where I am wrong ?

tsm: TSM>delete volhistory todate=today-30
ANR2022E DELETE VOLHISTORY: One or more parameters are missing.
ANS8001I Return code 3.

tsm: TSM>help ANR2022E
---


ANR2022E Command: One or more parameters are missing.

Explanation: The specified server command has been entered without all
required parameters.

System Action: The server ignores the command.

User Response: Reissue the command and enter the proper syntax.