Re: AW: [ADSM-L] Unable to delete volhist entries
Force parameter is not documented but it exist ! And it work (more often, I never tried it on dbb...) Pierre > -Message d'origine- > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > la part de Bell, Charles (Chip) > Envoyé : lundi 1 octobre 2007 17: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: 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 the future I'll read a little bit slower ;-) > > ( ... latest snapshot database backup will not be deleted.) > > Regards, > Otto > > -Ursprüngliche Nachricht- > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im > Auftrag von CAYE PIERRE > Gesendet: Montag, 1. Oktober 2007 13: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 meet the > specified date and time criteria. The latest > snapshot database > backup will not be deleted. > DEVclass=classname >Specifies the device class name that was used > to create the >database backups. This optional parameter can > be used to >delete database backups created using a > server-to-server >virtual volume device class. The type of the > device class >must be SERVER. This parameter can only be > used to delete >volume history entries of type BACKUPFULL, > BACKUPINCR, or >DBSNAPSHOT. > >A full, incremental, or snapshot database > backup volume is >eligible to be deleted if all of the following > conditions are >met: > + The device class used to create the > database backup > volume matches the specified device class > + The volume was created on or before the > specified date > and time > + The volume is not part of the latest full plus > incremental database backup series if the > specified > volume type is DBBackup, or snapshot > database backup > series if the volume type is DBSnapshot > > 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: [ADSM-L] Unable to delete volhist > > entries > > > > 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 TSM documentation says, it doesn't > want you > > to destroy your last/only database backup. (See Technote 1083952.) > > You could supplant the old snapshot with a new one, or try adding > > FORCE=Yes to the delete. > > > > Richard Sims http://people.bu.edu/rbs/ > > > > - > Confidentiality Notice: > The information contained in this email message is privileged > and confidential information and intended only for the use of > the individual or entity named in the address. If you are not > the intended recipient, you are hereby notified that any > dissemination, distribution, or copying of this information > is strictly prohibited. If you received this information in > error, please notify the sender and delete this information > from your computer and retain no copies of any of this information. >
Re: 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: 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 the future I'll read a little bit slower ;-) ( ... latest snapshot database backup will not be deleted.) Regards, Otto -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von CAYE PIERRE Gesendet: Montag, 1. Oktober 2007 13: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 meet the specified date and time criteria. The latest snapshot database backup will not be deleted. DEVclass=classname Specifies the device class name that was used to create the database backups. This optional parameter can be used to delete database backups created using a server-to-server virtual volume device class. The type of the device class must be SERVER. This parameter can only be used to delete volume history entries of type BACKUPFULL, BACKUPINCR, or DBSNAPSHOT. A full, incremental, or snapshot database backup volume is eligible to be deleted if all of the following conditions are met: + The device class used to create the database backup volume matches the specified device class + The volume was created on or before the specified date and time + The volume is not part of the latest full plus incremental database backup series if the specified volume type is DBBackup, or snapshot database backup series if the volume type is DBSnapshot 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: [ADSM-L] Unable to delete volhist > entries > > 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 TSM documentation says, it doesn't want you > to destroy your last/only database backup. (See Technote 1083952.) > You could supplant the old snapshot with a new one, or try adding > FORCE=Yes to the delete. > > Richard Sims http://people.bu.edu/rbs/ > - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
AW: [ADSM-L] Unable to delete volhist entries
Thank you ! In the future I'll read a little bit slower ;-) ( ... latest snapshot database backup will not be deleted.) Regards, Otto -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von CAYE PIERRE Gesendet: Montag, 1. Oktober 2007 13: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 meet the specified date and time criteria. The latest snapshot database backup will not be deleted. DEVclass=classname Specifies the device class name that was used to create the database backups. This optional parameter can be used to delete database backups created using a server-to-server virtual volume device class. The type of the device class must be SERVER. This parameter can only be used to delete volume history entries of type BACKUPFULL, BACKUPINCR, or DBSNAPSHOT. A full, incremental, or snapshot database backup volume is eligible to be deleted if all of the following conditions are met: + The device class used to create the database backup volume matches the specified device class + The volume was created on or before the specified date and time + The volume is not part of the latest full plus incremental database backup series if the specified volume type is DBBackup, or snapshot database backup series if the volume type is DBSnapshot 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: [ADSM-L] Unable to delete volhist > entries > > 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 TSM documentation says, it doesn't want you > to destroy your last/only database backup. (See Technote 1083952.) > You could supplant the old snapshot with a new one, or try adding > FORCE=Yes to the delete. > > Richard Sims http://people.bu.edu/rbs/ >
