The alternative (which my SQL guy decided to implement) is to single-thread the backups, 1-DB-at-a-time. It is ugly (and generates lots of error messages on my TSM server) but since this version is required for 2014 server with mirrored DB's, he didn't have much of a choice.
On Wed, Jul 29, 2015 at 10:25 AM, John Keyes <ra...@gmx.net> wrote: > Thanks for the answer. I tried the patch anyway, but as you said, it did > not work. > Now I downgraded to 7.1.1.1 and it works again. > > Best regards, > John > > > > Gesendet: Mittwoch, 29. Juli 2015 um 14:33 Uhr > > Von: "Zoltan Forray" <zfor...@vcu.edu> > > An: ADSM-L@VM.MARIST.EDU > > Betreff: Re: [ADSM-L] TSM TDPSQL crashes on log backup > > > > If you go look at the ADSM-L archives you will see I just went through > this > > exact same problem, a week or so ago. It is a known problem: > > > > > http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/ibm-tsm-13/issued-with-tdp-sql-7-1-2-0-and-2014-sql-server-128607/ > > > > IT09192: DATABASE BACKUPS USING DATA PROTECTION FOR SQL CAN CRASH DURING > > PROCESSING WITH REFERENCES TO MODULE CLR.DLL > > > > IBM recently released TDP SQL patch 7.1.2.1 but it DOES NOT fix this > > problem fully/yet - at least not on our system with this issue. The APAR > > discussed 2-problem and the FIN mentioned is 7.1.3. > > > > On Wed, Jul 29, 2015 at 6:16 AM, John Keyes <ra...@gmx.net> wrote: > > > > > Hello, > > > > > > i have a strange problem with one of my SQL Servers. It's a SQL Server > > > 2014, running on Windows Server 2012 R2. TSM BA and TDPSQL are > installed in > > > version 7.1.2.0. Most Databases use a simple recovery plan, but a few > have > > > a transaction log. VSS Full Backups are working fine as always. We set > the > > > whole thing up a few weeks ago, but since last week every log backup, > or > > > even legacy full backup for that matter, causes the TSM software to > crash. > > > There are no error reports in the tsm log files, the windows event > viewer > > > shows this: > > > Faulting application name: tdpsqlc.exe, version: 7.1.2.0, time stamp: > > > 0x55102a96 > > > Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: > > > 0x5348a1ef > > > Exception code: 0xc0000409 > > > Fault offset: 0x0000000000355714 > > > Faulting process id: 0x1838 > > > Faulting application start time: 0x01d0c9e477c55264 > > > Faulting application path: C:\Progra~1\Tivoli\TSM\TDPSql\tdpsqlc.exe > > > Faulting module path: > > > C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll > > > Report Id: bfee8f36-35d7-11e5-80cb-00155dfd9cbb > > > Faulting package full name: > > > Faulting package-relative application ID: > > > > > > I also rebootet the server and reinstalled TSM, but to no avail. Does > > > anyone have any ideas? > > > > > > > > > Kind Regards, > > > John > > > > > > > > > > > -- > > *Zoltan Forray* > > TSM Software & Hardware Administrator > > Xymon Monitor Administrator > > Virginia Commonwealth University > > UCC/Office of Technology Services > > www.ucc.vcu.edu > > zfor...@vcu.edu - 804-828-4807 > > Don't be a phishing victim - VCU and other reputable organizations will > > never use email to request that you reply with your password, social > > security number or confidential personal information. For more details > > visit http://infosecurity.vcu.edu/phishing.html > > > -- *Zoltan Forray* TSM Software & Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html