Sburk Posted December 28, 2009 Report Share Posted December 28, 2009 (edited) I have a backup script that basically backs up entire drives on several different computers. I noticed that it was attempting to backup mssql file extensions .mdf and .ldf which is causing roughly 130 errors upon backup completion. I added two exclude by name selectors: *.mdf *.ldf In the operations log it is still showing that the script is attempting to backup files with the above extensions. So, I'm still getting 130 errors upon completion. I have included a couple screenshots of the selector setup....the *.mdf and *.ldf selectors are setup exactly the same. Any ideas ladies and gentlemen? Thanks! Edited December 28, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
rhwalker Posted December 28, 2009 Report Share Posted December 28, 2009 Seems like you are doing it right, but have you tried instead: "file name ends with .mdf" or "file name ends with .ldf" Also, what are the errors? Russ Quote Link to comment Share on other sites More sharing options...
Sburk Posted December 28, 2009 Author Report Share Posted December 28, 2009 The errors are all ...\mssql\data\filename.mdf: can't read, error -1020 (sharing violation) ...\mssql\data\filename.ldf: can't read, error -1020 (sharing violation) Which I think is by design since the sql server is running. I will give your suggestion on the selectors a shot. I'll know if it worked by tomorrow morning and will report back. Thanks! Quote Link to comment Share on other sites More sharing options...
Sburk Posted December 31, 2009 Author Report Share Posted December 31, 2009 I'm still getting these errors. Any ideas? Quote Link to comment Share on other sites More sharing options...
rcohen Posted January 4, 2010 Report Share Posted January 4, 2010 A couple suggestions: 1) I have had better luck with "Windows file name ends with .ldf", rather than "file name ends with .ldf". 2) Also, you could try "Windows file or folder starts with "c:\mssql\data\" (or whatever). It's faster to check if your selector is working with the Check Selector feature, rather than running a backup. Quote Link to comment Share on other sites More sharing options...
Sburk Posted January 12, 2010 Author Report Share Posted January 12, 2010 I tried your suggestions and still no joy. Excuse my ignorance, but when I run the "check selector" tool, it appears to just pull up an entire list of the entire source drive. I drill down to find a .mdf or a .ldf and both are still selected. Is this expected?? Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted January 13, 2010 Report Share Posted January 13, 2010 Excuse my ignorance, but when I run the "check selector" tool, it appears to just pull up an entire list of the entire source drive. I drill down to find a .mdf or a .ldf and both are still selected. Is this expected?? Yes and No. You should expect a list of all files and folders. Some files/folders should be selected, but not others. The fact that .mdf and .ldf are still selected means your selector doesn't work. Quote Link to comment Share on other sites More sharing options...
Ramon88 Posted January 13, 2010 Report Share Posted January 13, 2010 Recently we used a wildcard (*) in a selector and that didn't work. Only when we entered the full blown path it worked. So it seems to me the (*) wildcard doesn't (always?) work. Could be a bug? B.t.w., we use 7.6.123 Multi Server. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.