FBackup Forum

About 70 GB, way more than the new and changed files in those jobs would require.

Good point. Various messages at various times: The shadow copy of volume D: was aborted because of a failed free space computation. The shadow copy of volume D: became low on diff area space before it was properly installed. The shadow copy of volume D: was aborted because the diff area file could n...

Yeah, looks like it crashes with the larger backups. Not so much the job size, but the amount of data that needs backing up at that moment. Strange thing is that these jobs are identical to the ones I used in FB4 where I very rarely had VSC related crashes. In FB5 it's like clockwork.

I think it's mostly the larger backups (but again, they're exactly the same jobs that ran just fine under FB4). I'll have to look at it again when my weekly backups are running as my desktop is currently busy doing other things.

Just started a large backup job and vscsrv.exe is still crashing I'm afraid. Is there anything else I can poke at?

Strange, it wasn't. I'll keep an eye on my next scheduled backup, see if this fixed it. Thanks

WinXP SP3, so yeah. Same as in FB4, was pretty stable there

Under FB4 this was quite rare, but vscsrv.exe for some reason frequently crashes under FB5 (WinXP x86 SP3). The strange thing is that the backup job just continues, so what exactly is going on?

Softland wrote:Hi,

The log folder is limited at 20 MB at this moment, we will increase the size in the next release.

One of my jobs with lots and lots of small files generated a log file at 16MB when first run, so yeah a 20MB maximum would explain it
Could you make this maximum log size user set please?

Yes, but the expected behaviour tends to be that an app only touches files it created itself (i.e. in this case log files). Bit unusual to have it do general spring cleaning and delete other files as well.