Thanks Tim, The problem solved with: DELETE VOLHISTORY TODATE=today+9999 TYPE=DBBACKUP force=yes
Best regards Ricardo Negrete Project Manager CIENTEC S.A. Av. Presidente Riesco 5711 Piso 7º Las Condes-Santiago-Chile Fono: (56-2) 426 2700 www.cientec.com "Rushforth, Tim" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 19-04-2007 16:17 Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] paradox problem to expire db backups! I wonder if Delete Volhistory ... Force=yes will help? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ricardo Negrete Sent: Thursday, April 19, 2007 10:02 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] paradox problem to expire db backups! Hi,.. I have a very singular Customer, they install TSM server 5,3 on Linux with the mistaken time-date, December-3 -2007 having to be March-12-2007, they run the backup of DB TSM all week days and continued operating. Any time later they modify the date-time in correct form and they run the backup of DB TSM all week days and continued operating Today, they have problems to expire old TSM database backups because the registry of Volhistrory indicate valid database backups in the future (December- 3-2007) and the present database backups never expired after that date. as this problem can be solved? Thanks in advance Ricardo Negrete Project Manager CIENTEC S.A. Av. Presidente Riesco 5711 Piso 7º Las Condes-Santiago-Chile Fono: (56-2) 426 2700 www.cientec.com
