Author: Chuck Mattern <Chuck_Mattern AT HOMEDEPOT DOT COM>
Date: Mon, 23 Jun 2003 07:55:12 -0400
Ever since we transitioned from adsm v3 to adsm v4 we have encountered an extremely high "failure rate". Essentially when adsm went from backing up Unix filesystems like tar (see a file; get a file)
Author: "Mr. Lindsay Morris" <lmorris AT SERVERGRAPH DOT COM>
Date: Mon, 23 Jun 2003 09:22:53 -0400
Chuck, would a missed-files report that grouped them by reason-missed help you? eg: Files Missed for Nodexxx Not found: 562 Changing: 2 Locked: 132 Then of course you'd want to be able to click each
Author: Chuck Mattern <Chuck_Mattern AT HOMEDEPOT DOT COM>
Date: Mon, 23 Jun 2003 12:33:41 -0400
Lindsay, This sounds great. We would need full path names to evaluate the consequences of the event. Is something like this already floating around? Chuck Mattern The Home Depot Phone: 770-433-8211 x
Author: "Garrison, Tony" <Anthony.Garrison AT USAA DOT COM>
Date: Mon, 23 Jun 2003 14:32:48 -0500
Sounds good to me also. Anthony A. Garrison Jr. Sr. Systems Programmer USAA (210 456-5755 Lindsay, This sounds great. We would need full path names to evaluate the consequences of the event. Is somet
Author: "Mr. Lindsay Morris" <lmorris AT SERVERGRAPH DOT COM>
Date: Mon, 23 Jun 2003 15:56:43 -0400
Tony, doesn't the Unexpected events page in Servergraph let you click on each of the ANExxxx messages, and see every individual filename that was missed / retried/ locked / etc? I initially responded
Author: Zlatko Krastev/ACIT <acit AT ATTGLOBAL DOT NET>
Date: Wed, 25 Jun 2003 09:36:13 +0300
Chuck, I would say these files are very good candidates for exclude as any other temporary file. If they are existing for a very limited period and even now you are not backuing up those files withou