FYI, FWIW, after increasing IDLETIMEOUT and COMMTIMEOUT to 120000 (ridiculous - yes I know one value is in seconds and the other in minutes) and 2-STRIPES, the SQL backup of this database finally finished after running 74-Hours.
Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services 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 From: Zoltan Forray/AC/VCU <zfor...@vcu.edu> To: ADSM-L@VM.MARIST.EDU Date: 09/05/2011 01:21 PM Subject: [ADSM-L] LARGE MS-SQL TDP backup keeps failing Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> I am trying to backup a LARGE SQL (4TB) database via the SQL TDP, without success. It will run for a while and then die - usually with the error: ANS1017E (RC-50): Session Rejected : TCP/IP communications failure. The last try backed up 125GB before failing. I have greatly increased the server communication timeout (6000 seconds) guessing it is a timeout issue. I know very little about the SQL TDP (v5.5.5.0 - base TSM client is 6.1.3.2 - yes I know it needs updating) and config options. Is there a way to breakup the backup into chunks, like you can do with Oracle backups? Suggestions? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services 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