Re: retries happenning with serialization=dynamic coded
One thought: When certain users or processes open files, they DENY READ ACCESS to the files for any other user or process. When this happens, even with serialization set to DYNAMIC or SHRDYNAMIC, ADSM does not back up the file. Is it only happening with these files with these extensions??? Files with these extensions are monitored by Windows Me System Restore based on the interval that you set or by default every 24 hours. This may be interfering with TSM's backup processing. -Original Message- From: [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 3:18 PM To: [EMAIL PROTECTED] Subject: Re: retries happenning with serialization=dynamic coded Yes, its happenning over and over again with more than 1 file, but my question is if I have dynamic coded, why does it retry at all? "Malbrough, Demetrius" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 12/19/2001 03:43:48 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: retries happenning with serialization=dynamic coded They seem to be different files to me... *.utx *.xtu Unless, there is something that I am not seeing here! -Original Message- From: [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 1:37 PM To: [EMAIL PROTECTED] Subject: retries happenning with serialization=dynamic coded I'm seeing a bizzare situation I can't explain on an NT client running a backup(I'm still hanging on to version 3.7) I have my policy for this client setup for copy serialization=dynamic which states that "TSM should backup the file or directory on the firs attempt regardless of whether the file or directory is being backed up during backup processing" Then why am i getting this in my dsmsched.log? Is there something else possible occurring causing TSM to retry? 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-1.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-1.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 1,297 \\srny4lm01\d$\notes\8859-14.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-14.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 683 \\srny4lm01\d$\notes\8859-15.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-15.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 883 \\srny4lm01\d$\notes\8859-2.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-2.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 823 \\srny4lm01\d$\notes\8859-3.utx [Sent]
Re: retries happenning with serialization=dynamic coded
Yes, its happenning over and over again with more than 1 file, but my question is if I have dynamic coded, why does it retry at all? "Malbrough, Demetrius" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 12/19/2001 03:43:48 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: retries happenning with serialization=dynamic coded They seem to be different files to me... *.utx *.xtu Unless, there is something that I am not seeing here! -Original Message- From: [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 1:37 PM To: [EMAIL PROTECTED] Subject: retries happenning with serialization=dynamic coded I'm seeing a bizzare situation I can't explain on an NT client running a backup(I'm still hanging on to version 3.7) I have my policy for this client setup for copy serialization=dynamic which states that "TSM should backup the file or directory on the firs attempt regardless of whether the file or directory is being backed up during backup processing" Then why am i getting this in my dsmsched.log? Is there something else possible occurring causing TSM to retry? 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-1.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-1.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 1,297 \\srny4lm01\d$\notes\8859-14.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-14.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 683 \\srny4lm01\d$\notes\8859-15.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-15.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 883 \\srny4lm01\d$\notes\8859-2.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-2.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 823 \\srny4lm01\d$\notes\8859-3.utx [Sent]
Re: retries happenning with serialization=dynamic coded
They seem to be different files to me... *.utx *.xtu Unless, there is something that I am not seeing here! -Original Message- From: [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 1:37 PM To: [EMAIL PROTECTED] Subject: retries happenning with serialization=dynamic coded I'm seeing a bizzare situation I can't explain on an NT client running a backup(I'm still hanging on to version 3.7) I have my policy for this client setup for copy serialization=dynamic which states that "TSM should backup the file or directory on the firs attempt regardless of whether the file or directory is being backed up during backup processing" Then why am i getting this in my dsmsched.log? Is there something else possible occurring causing TSM to retry? 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-1.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-1.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 1,297 \\srny4lm01\d$\notes\8859-14.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-14.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 683 \\srny4lm01\d$\notes\8859-15.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-15.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 883 \\srny4lm01\d$\notes\8859-2.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-2.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 823 \\srny4lm01\d$\notes\8859-3.utx [Sent]
retries happenning with serialization=dynamic coded
I'm seeing a bizzare situation I can't explain on an NT client running a backup(I'm still hanging on to version 3.7) I have my policy for this client setup for copy serialization=dynamic which states that "TSM should backup the file or directory on the firs attempt regardless of whether the file or directory is being backed up during backup processing" Then why am i getting this in my dsmsched.log? Is there something else possible occurring causing TSM to retry? 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-1.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-1.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 1,297 \\srny4lm01\d$\notes\8859-14.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-14.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 683 \\srny4lm01\d$\notes\8859-15.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-15.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 883 \\srny4lm01\d$\notes\8859-2.utx [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 565 \\srny4lm01\d$\notes\8859-2.xtu [Sent] 12/19/2001 12:20:29 Retry # 1 Normal File--> 823 \\srny4lm01\d$\notes\8859-3.utx [Sent]
