Huge CBSpersist_xxxxxxxxxxx.log file on server

Cooners · 16 Jun 2014 at 15:39

Hi
I went into one of the little schools that I check on every other week to find the backup hasn't been running because the RDX tape was too small, it worked fine until shortly after my last visit but then the windows folder ballooned in size stopping it from working, I've traced this to a cbspersist_xxxxxxx.log file that is 100GB in size! I have two questions.
1. Is it ok to delete it? There are newer versions of the file that are not as big
2. Should I be worried about why it did it?

What would have caused it? I haven't run SFC ever since I migrated them onto this server last May and it happened on a Saturday when nobody would have been in the building, the event log isn't showing any issues on that day at all.

anything I don't mind · 16 Jun 2014 at 16:44

http://support.microsoft.com/kb/928228

Never seen that happen before. Id imagine it would be ok to remove it as its just a log file, i would be more concerned about what is in it. ie why sfc log managed to get so large.

http://social.technet.microsoft.com...spersistlog-can-delete?forum=winservermanager

I figured this out. I had a relatively new WMI query that was checking on windows updates status. It was set to run too frequently and was filling up my logs.

Ploppy2k3 · 16 Jun 2014 at 16:59

yup 100% safe to delete.

100GB! wow never seen a log file outside of Exchange or SQl get that big.

Cooners · 16 Jun 2014 at 19:35

Ok thanks. Might just copy it to a external drive and check whats in it back at the office first (don't really want to open a file that big on the server).

Ploppy2k3 · 16 Jun 2014 at 20:03

hah I would like to see Notepad open that lol

Quartz · 16 Jun 2014 at 20:13

Cooners said:
Ok thanks. Might just copy it to a external drive and check whats in it back at the office first (don't really want to open a file that big on the server).

Rename it, compress it, then copy it. It'll save you a lot of time.