VSS Maintenance
-
I'm interested in automating VSS maintenance including ANALYZE. I am trying to maintain a sizeable database which has gotten out of hand with respect to corruption, so I need the script to be able to handle errors as they occur. Can anyone recomend an approach to this? What tools/technology would you recomend I start with? Would this be best handled by a batch file or something more advanced? Let me know if I need to furnish you with more information... Thanks very much for any suggestions, -Jordan Atlas
-
I'm interested in automating VSS maintenance including ANALYZE. I am trying to maintain a sizeable database which has gotten out of hand with respect to corruption, so I need the script to be able to handle errors as they occur. Can anyone recomend an approach to this? What tools/technology would you recomend I start with? Would this be best handled by a batch file or something more advanced? Let me know if I need to furnish you with more information... Thanks very much for any suggestions, -Jordan Atlas
Jordan: We simply use a batch file that calls the VSS utilities on the command-line and have the batch file run as a night job on the server. Every database is backed-up first, then it has analyze run on them. Each day I visual scan the log files for problems. We've never had an issue doing it this way to date. :-D D.
-
Jordan: We simply use a batch file that calls the VSS utilities on the command-line and have the batch file run as a night job on the server. Every database is backed-up first, then it has analyze run on them. Each day I visual scan the log files for problems. We've never had an issue doing it this way to date. :-D D.
Douglas: Thanks for the reply. Now does your batch file handle errors from analyze? I'm talking about the errors that make analyze abort. -Jordan
-
Douglas: Thanks for the reply. Now does your batch file handle errors from analyze? I'm talking about the errors that make analyze abort. -Jordan
Well, I was trying to dig up the batch file for you, so I could send it your way, but our IS group has once again moved stuff about and I don't see it anymore (probably on a secure server). :(( So ... you should be able to check the dos error level coming back from Analyze (i.e. if errorlevel = 1 goto BadData ) to determine if a problem occurred. Also, if you look in the VSS on-help, you'll find examples on how to handle using the Ananlyze Utilitiy, the command-line prompt, and those switches that need to be set in order to properly handle problems. It provides for an active dump to a text file of issues found and resolved (we run ours every day). Now, if your database is so trashed that it's dumping Analyze out with no chance to fix the problems, then you have much deeper issues at hand. Does that help any? :confused: Hope so. D.