Spoold does not start due to TLOG corruption

[tjosuweit]

Hi all,

my customer has a problem with his deduplication storage. It won't come up again reporting an error in a TLOG file.

Of course I filed a case with symantec the day the problem occured but although I send them mails on a daily basis they didn't even bother calling me back at the agreed time. So my customer has no backup for nearly a week. How's that for support?

Anyway I need a solution quickly now, so I'm hoping there's anybody out there who had a similar problem!

Here is a clip from the log file:

January 16 14:49:25 TRACE [000000000212F910]: Spooler Cache Manager: importing R:\BackupExecDeduplicationStorageFolder\queue\57937.tlog

January 16 14:49:25 ERR [000000000212F910]: 25000: Transaction 0 failed: invalid entry type 0 in transaction log R:\BackupExecDeduplicationStorageFolder\queue\57937.tlog. CRC mismatch, header contains crc 0, calculated crc 1310721.The data is lost. Transaction aborted.

January 16 14:49:25 WARNING [000000000212F910]: 25032: _spoolerRestoreTlog: Tlog file 57937.tlog corrupt, now try to restore it with backup copy.

January 16 14:49:25 TRACE [000000000212F910]: CRMapError: called by SpoolTlogOpen (../spooler.c:3101), errno = 2

January 16 14:49:25 ERR [000000000212F910]: -1: SpoolTlogOpen failed(no such object).

January 16 14:49:25 ERR [000000000212F910]: -1: Backup copy R:\BackupExecDeduplicationStorageFolder\processed\57937.tlog is corrupt also, we cannot go further for queue processing.

In case anyone from Symantec is reading this and wants take a look at it, the case number is 08053408.

Cheers

Thomas

[VJware]

Looking over your case & will get an engineer assigned asap. Afaik, this issue would require running internal utility(s) and difficult to work on the forum directly.

[tjosuweit]

Hi all,

thanks to VJware's help (I suppose) I got a call from symantec technical support yesterday.

Basically what they did was delete the corrupt tlog files, in my case 57937.tlog. After that the spoold process found several other tlog files that they deleted also.

Finally the process started without an error and we could start the backups.

Still two things that bother me:
1. Symantec never told me the root cause of the corrupt files. There seems to be more than one possibe reason.
2. Later that night all backup jobs crashed, the Dedupe Storage went Offline again and when I start spoold today it simply reports other tlog files are corrupt.

Since this "solution" did not work and the customer need a full backup over the weekend, we deleted and recreated the Dedupe Storage.

Hopefully the new storage works until monday!

Cheers

Thomas