Re: Expiration problem with TSM 5.1.1.1 on AIX 4.3.3

Yes, 5.1.2.0 was supposed to come out with 4.2.2.7, but something happened which was not exlained to me. Quoting "Seay, Paul" <[EMAIL PROTECTED]>: > I have seen the same problem under V4.2.1.15 but not quite as severe. The > problem went away with 4.2.2.7. > > Paul D. Seay, Jr. > Technical Sp

Re: Expiration problem with TSM 5.1.1.1 on AIX 4.3.3

I should have posted this weeks ago, but I've been fighting the losing battle against the shrinking scratch pool for a month. I called this in on July 3. I've since gone from 5.1.1.0 to 5.1.1.1 to 5.1.1.2. I've spent hours on the phone with Level 2 and burned lots of innocent electrons in intem

Re: Expiration problem with TSM 5.1.1.1 on AIX 4.3.3

Same here on 5.1.1.1 - looks like the stall (error message is that a resource waiter has been aborted) happens whenever database change-intensive processes run at the same time when expiration runs. I had this happen when move nodedata ran concurrent with expiration and also when migration ran con

Re: Backups of a file when it hasn't changed.

Thanks for the thought, but I know of nothing that would have changed security permissions. Non on my workstation. John -Original Message- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 03, 2002 10:25 AM To: [EMAIL PROTECTED] Subject: Re: Backups of a file when it has

Re: Backups of a file when it hasn't changed.

I am sure everyone is aware that if the security permissions are changed the file does not get modified nor its modified date but it will be backed up again to get the new permissions. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Talafous, J

Re: TSM backing up in a DMZ zone.

See my responses inline. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: William Rosette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: [EMAIL PROTECTED] Subject: Re: TSM backing up in a DMZ zone. HI TSMr's, I h

Re: Backups of a file when it hasn't changed.

I too have seen this same phenomenon. Our environment is TSM 4.2.1.9 Server on AIX 5.1. Clients where I have seen multiple backups of files are on Windows NT/2000. It is puzzling because we have COPYMODE of MODIFIED in our management classes. I have various files on my Win2000 workstation that ha

Re: Expiration problem with TSM 5.1.1.1 on AIX 4.3.3

I have seen the same problem under V4.2.1.15 but not quite as severe. The problem went away with 4.2.2.7. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Magura, Curtis [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 03, 2002 7:29 AM To: [EM

Re: Trapping TSM Messages on NT4 and W2K

We do this all the time for about 200 NT and W2K nodes the way Andy has described with a product called Control-M. The only issue we have ever had is Control-M loses its registry stuff every now and then and the backup does not complete at all. ESP may not have this problem. To alleviate this,

Re: Expiration problem with TSM 5.1.1.1 on AIX 4.3.3

Yep - seeing the same thing. We have three servers. Two are the same config you mentioned. The thrid one is hosted on win2k. Also seeing the same symptoms. Please post back to the list results of the PMR. Curt Magura Lockheed Martin EIS Gaithersburg, Md. 301-240-6305 -Original Message-

Re: Trapping TSM Messages on NT4 and W2K

See the chapter on "Automating Tasks" in the 5.1 client manual for information on return codes from the command line client. In Windows, return codes from the last command (or program) executed can be detected via the %errorlevel% variable. For example: dsmc incremental echo TSM return cod