Backups Failing due to On-Access scanning

Hello OaksIT,

failing backups due to on-access scanning [...] false positives
failing because access to certain files (false positives?) is denied, or? How do you know these are false positives? And what exactly is your question [:)]?

Christian

Sorry, 

How do I exclude folders with long path names that reside on the network ie \\servername\sharename 

Hello OaksIT,

it's better to give a detailed description of a problem than asking for specifics of an assumed solution. If you prefer the latter please nevertheless try to be precise. IMO your posts are somewhat ambiguous (\\networklocation\sharename vs. long path names).
Apart from the point that a folder exclusion must end with a backslash (the GUI, endpoint or console, doesn't accept it anyway without one) there's no additional magic required to make an exclusion work. If your backups are still failing then an exclusion is not the solution. Or - if it's a matter of using the correct exclusion then, naturally, details are required to give potentially useful advice.

If it's indeed on-access scanning which eventually results in failing backups either disabling on-access or setting a process-exclusion for the backup process(es) should help. This shouldn't be done without consideration. Depending on the nature of the data/files to be backed up a(n additional) scan during backup isn't superfluous, a backup should be as "clean" as possible. There might be items which have not yet properly been dealt with. New and amended identities might detect previously unrecognized threats.

Christian

Hello OaksIT,

it's better to give a detailed description of a problem than asking for specifics of an assumed solution. If you prefer the latter please nevertheless try to be precise. IMO your posts are somewhat ambiguous (\\networklocation\sharename vs. long path names).
Apart from the point that a folder exclusion must end with a backslash (the GUI, endpoint or console, doesn't accept it anyway without one) there's no additional magic required to make an exclusion work. If your backups are still failing then an exclusion is not the solution. Or - if it's a matter of using the correct exclusion then, naturally, details are required to give potentially useful advice.

If it's indeed on-access scanning which eventually results in failing backups either disabling on-access or setting a process-exclusion for the backup process(es) should help. This shouldn't be done without consideration. Depending on the nature of the data/files to be backed up a(n additional) scan during backup isn't superfluous, a backup should be as "clean" as possible. There might be items which have not yet properly been dealt with. New and amended identities might detect previously unrecognized threats.

Christian