I am sure that the problem has something to do with the accelerator as backup jobs only fail when the accelerator is enabled. No matter if is the client or the server which deduplcates the data, change journal enabled, etc.

You may have old vss snapshots on your Windows machine. Can you please try to list if there is existing snapshots using either "diskshadow / list all shadows" on Windows 2008 or the "vssadmin" tool for Windows 2003.

Then I have deleted the track log (as commented by cds171612) and launched a full backups with accelerator. This one has has finished ok (creating again the track log) and a second attempt has finished ok using the brand new accelerator's track log.

So It seems the workaround works BUT the cost is to high as it is necessary to re-create the tracklog again.

Thanks for the comment, I checked and they are at 15 mins so thats not it. Also that job had been running since at least 11:34am(first line of my log) and the 5 mins you are talking about is when it first spit out an error.

This can happen 6 hours in on alarge client to 30 mins in on a remote client.. seems random.

However as Juasiepo mentioned although my workaround seems to resolve the issue for awhile..the cost is very high for remote backups and nothing stpos it from happeing again.

Welcome any more feedback or comments...this must be happening to others that use Accelerator?

I only have windows servers, but what I can say is I have a large enviroment going over 2 countries with 2 completely seperate masters and I get the exact same issues on both.

If I am not mistaken, this might be related to the bug I reported in 7.5.0.1 that resulted in the Track file growing till it used up all disk space! They fixed that in 7.5.0.4, however perhaps part of the issue still remains..in that it no longer takes down your server but it still doesn't let you complete a full.

It doesn't happen to every server, and some more than others. In some cases just the 1 time.

I have tried changing every setting I can think of, but it still seems to exist in each scenario. It might be related to checkpoints..but with remote backups that needs to be enabled. That said will run a full accel with them disabled and then report back if by some miracle that works.

I'm on 7.5.0.4, currently, and recently had this problem pop up on one of my Windows backup policies using accellerator. I just tested turning off accellerator and re-running the job, and it completed successfully.

The odd part is that all the incremental backups worked fine. It was only the FULL jobs that bombed.