08-23-2010 08:28 AM
Solved! Go to Solution.
08-24-2010 07:50 AM
08-23-2010 08:45 AM
08-23-2010 11:22 AM
Hey Flavor4real,
It sounds like the most straightforward answer for you would be to use and exclude list (in which you can use wildcards) to exclude the files in question from backup. Take a look at the SAG I Guide "Syntax rules for exclude list"; but basically you would create an exclude list for any client that has the corrupt filename and use a wildcard in place of the characters that you can not enter.
Worth a try anyway :>
Vanessa
08-23-2010 12:00 PM
08-23-2010 01:55 PM
08-24-2010 05:05 AM
08-24-2010 05:26 AM
See the problem I'm having is that we have bottleneck in our network, we are workin gon it to get this issue resolved but it might take a while. The oranization switched to Netbacakup 6.5 and I'm the temp. backup admin.
If I run a backup job, it kicks in and runs, so everything looks good. This particular job runs up to 55% and then slows down and don't go further. I opened up the clients job tracker and see that the job is stuck on a file where it's naming convention seems to be corrupted. I've made several searches for that special character and found them and removed these files. Last night i've started the job again and a nother job had a nameing convention with special characters.
Now, I can put up a exclusion list from what I've heard but that means i have to restart the job again. and since those special characters are randomly within the file name itself. It's actually hard to filter out. If I filter the extention out then i will most likley block all other 300GB of files out too.
Is there somewhere a setting, like time out for backing up files, skips corrupt files, or anything which tells the job that if a files is unreadable or can't be backed up simple right away go to the next file?
how do you setup a exclusion list?
08-24-2010 05:33 AM
so, from my understanding and correct meif i'm wrong.
Changing hte client property > timeouts > file brows timeout to (example: 300 seconds, having the Use OS dependent timeouts unchecked) might helps with this issue.
08-24-2010 06:17 AM
08-24-2010 07:29 AM
08-24-2010 07:50 AM