Hi, Thanks for your reply Efim, We run Full DB backup every night and they happen fine (see log below). The management class is the same for Full bkps and logs bkps.
We encounter the issue on all the infrastructure (more than 70 MSSQL instances). FULL DB backup objects and log backup objects have the same behavior, they do not get inactive and thus do not expire I'm quite sure that inactivate manually the objects will generate the expire. But, from our side, that is not a way to rule a production infrastructure and we must find the root cause.... Have a great day, Emmanuel 10/12/2016 21:25:36 ========================================================================= 10/12/2016 21:25:38 ========================================================================= 10/12/2016 21:25:38 Request : FULL BACKUP 10/12/2016 21:25:38 Database Input List : * 10/12/2016 21:25:38 Group Input List : - 10/12/2016 21:25:38 File Input List : - 10/12/2016 21:25:38 Number of Buffers : 3 10/12/2016 21:25:38 Buffer Size : 1024 10/12/2016 21:25:38 Number of SQL Buffers : 0 10/12/2016 21:25:38 SQL Buffer Size : 1024 10/12/2016 21:25:38 Number of Stripes specified : 1 10/12/2016 21:25:38 Estimate : - 10/12/2016 21:25:38 Truncate Log? : - 10/12/2016 21:25:38 SQL Checksum enabled? : No 10/12/2016 21:25:38 Wait for Tape Mounts? : Yes 10/12/2016 21:25:38 TSM Options File : c:\Program Files\Tivoli\TSM\TDPSql\dsm_H1_TDP.opt 10/12/2016 21:25:38 TSM Nodename Override : - 10/12/2016 21:25:39 Sqlserver : H1\INSTANCE1 10/12/2016 21:25:54 Total SQL backups selected: 10 10/12/2016 21:25:54 Total SQL backups attempted: 4 10/12/2016 21:25:54 Total SQL backups completed: 4 10/12/2016 21:25:54 Total SQL backups excluded: 6 10/12/2016 21:25:54 Total SQL backups inactivated: 216 10/12/2016 21:25:54 Total SQL backups deduplicated: 0 10/12/2016 21:25:54 Throughput rate: 8,183.72 Kb/Sec 10/12/2016 21:25:54 Total bytes inspected: 52,090,880 10/12/2016 21:25:54 Total bytes transferred: 52,090,880 10/12/2016 21:25:54 Total LanFree bytes transferred: 0 10/12/2016 21:25:54 Total bytes before deduplication: 0 10/12/2016 21:25:54 Total bytes after deduplication: 0 10/12/2016 21:25:54 Data compressed by: 0% 10/12/2016 21:25:54 Deduplication reduction: 0.00% 10/12/2016 21:25:54 Total data reduction ratio: 0.00% 10/12/2016 21:25:54 Elapsed processing time: 6.22 Secs 10/12/2016 21:41:44 ============== Log file pruned using log retention period of 60 day(s) 10/12/2016 21:41:44 ============== No log entries pruned 10/12/2016 21:41:46 ========================================================================= -----Message d'origine----- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Efim Envoyé : jeudi 13 octobre 2016 11:45 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] MSQSSQL TDP 6.4 and 7.4.1 : legacy backup do not expire HI, You shows the LOG object but it will deactivated as GROUP object. The GROUP leader is FULL backup. Do you have only ONE active FULL object for this DB? If yes, is the FULL active object is younger than this active LOG? If yes - you can use inactivate (or delete) command for inactivate(delete) log older than last active full and monitor situation. Efim > 13 окт. 2016 г., в 11:10, BOVE Emmanuel (EXT) <emmanuel.bove-...@socgen.com> > написал(а): > > MC_PROD_LOG_SQL
