The out of memory condition looks like a successful backup, but it really is not.
How much memory is on the Solaris machine and how many files does the largest filesystem tree path have? Unfortunately, there were some memory leaks fixed in later releases of TSM that may apply all the way back to 3.1.0.8 but they will never be fixed there. The client you are using is the last one that was created for 2.5.1. No vendors support Solaris 2.5.1 any longer. Sucks, but that is just a financial fact. The vendors cannot support every release of an OS anymore. It is just too costly for them to do certification testing. -----Original Message----- From: Nancy R. Brizuela [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 5:55 PM To: [EMAIL PROTECTED] Subject: File systems skipped with Sun Solaris 2.5.1 running TSM client 3.1.0.8 with OS/390 TSM Server 4.2.1.9 Hello All, We have a backup client running on Sun Solaris 2.5.1 with TSM client 3.1.0.8. Our server is running on OS/390 V 2.6 with TSM server 4.2.1.9. Some of the time, the backups for this client are successful. It is occasionally and randomly missing entire file systems, though. The backup is marked as successful and the error log show nothing amiss. The error log did show an "out of memory" condition on a day that the backup worked correctly. Has anyone run into this problem? Did you find a solution? Is anyone using a higher level TSM version on a Sun Solaris 2.5.1 client? We know we have an old OS and an old TSM client, but upgrading the client OS so that we could use a newer version of the TSM client is not an option right now. Thanks, Nancy Brizuela University of Wyoming IBM Systems Group Ivinson Room 238 (307)766-2958
