Henrik, I have had this same problem with the 5.1.0.1 client version. Backups running fine then all of a sudden the backups on the System Objects will not complete with the same problem you are describing.
My immediate resolution was to upgrade the client to 5.1.5.9, which may not be suitable to you. I also renamed the System Object at the TSM server for the node, and then was able to do a "fresh" backup of the system object. This was a hassle when I could, whenever possible, just update the client code. You will just have to remember to go back and get rid of that renamed system object filespace at the appropriate time. I hope this helps. These are just work arounds to the issue. Matt Adams Tivoli Storage Manager Team Hermitage Site Tech Deloitte and Touche USA LLP -----Original Message----- From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2003 7:20 AM To: [EMAIL PROTECTED] Subject: 4.2.2.0 client crach rc=4, System object? Hi, I have a w2k sp3 client with TSM 4.2.2.0. TSM server is 4.1.3.0. During backupwindow my backup schedule starts and completes and fails with RC=4. Then the schedule start to loop i.e restart the schedule during backup window like 30 times and do a backup......each time. I can backup everything with the GUI except System files. If I select System files in a manuel backup the client crash. I´ve read about similar problems http://msgs.adsm.org/cgi-bin/get/adsm0201/210.html. But wasn´t that bug fixed? Only thing I can find in dsm*.log and ACT is 'ANR0480W Session 9571 for node W02 (WinNT) terminated connection with client severed.' at almost the same time the client starts to backup SYSTEM OBJECT. Any ideas? //Henrik ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. - This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
