Job Taking to long, so cancels itself

[andrewparkes]

We are running Backup Exec 2012 on a Windows Server 2008 R2 Server. It has been running fine for the the best part of the last year ,however over the past few months it seems to be taking longer to backup, but the extra amount of data is only ab increase of about 10GB or so. On 28th December it took 15:43:18 to backup 680GB @ 893.23MB/Min. 26th January it backed up 686GB @ 882.76MB/Min , but cancelled it self due to reaching the maximum configured run time.

We could turn off the maximum run time but this would mean it clashing with the start time of the next job due it it being a full backup, so thats not really the answer to it as has worked fine for past god knows how long.

So what causes it, as 6GB of data shouldnt really take an extra 6+ hours to backup and verify.

Any ideas?

[andrewparkes]

Yeah, they will be run later today. Will report back if the uncover anything :)

[pkh]

it only backs up the one drive. al ldata is stored on that

I thought that you meant that all the backup data are stored on that one drive together with the data.

=================

Regarding your SEP, see this document

http://www.symantec.com/docs/TECH168940

==================

We dont back up the C:\ drive, there is no need to.

As an aside, if you don't backup the C: drive, how are you going to restore the server?

[andrewparkes]

I thought that you meant that all the backup data are stored on that one drive together with the data.

Nope, that would be stupid and a waste of time/money. It does state on the discussion that its backed up to tape

=================

Looking into the SEP exclusions, although it worked fine previously, using the same SEP policies so not sure if that is the issue, but will check anyway.

==================

We dont back up the C:\ drive, there is no need to.

It backs up the data on another drive, not C:, the data is the important bit. The server is not as it can be restored to another server if required

[andrewparkes]

Well todays backup is still running the backup operation, by the time it gets to the verify stage it will have cancelled itself again anyway! Going to swap the drives over and backup to another library to see if that makes a difference

[andrewparkes · Accepted solution]

Would seem that adding the exclusions and unticking the "scan on backup" option in the SEP polices have sorted it. The past few backups have all finished on time. Must be yet another bug in SEP 12.1.2 that causes the problem as we never had it in 12.1.1 and before as it always finished in time.

Fun and games, I swear this SEP AV is just designed to cause more problems than it solves