cancel
Showing results for 
Search instead for 
Did you mean: 

Critical bpbrm(pid=39056) from client XXXX: FTL - fatal error during enumeration of journal data for <C:\> <reason=unable to get track log entry>

julien17
Level 3

10/02/2016 22:16:19 - Info bpbkar(pid=2784) will attempt to use change journal data for <C:\>    
10/02/2016 22:16:19 - Info bpbkar(pid=2784) not using change journal data for <System State:\>: not supported for non-local volumes / file systems
10/02/2016 22:16:19 - Info bpbkar(pid=2784) not using change journal data for <_BACKUP_SPECIAL_OBJECTS AFTER System State:>: not supported for non-local volumes / file systems
10/02/2016 22:16:19 - Info bpbkar(pid=2784) not using change journal data for <EFI System Partition:\>: not supported for non-local volumes / file systems
10/02/2016 22:28:20 - Info bpbkar(pid=2784) using change journal data for <C:\>       
10/02/2016 22:29:02 - Critical bpbrm(pid=39056) from client XXXX: FTL - fatal error during enumeration of journal data for <C:\> <reason=unable to get track log entry>
10/02/2016 23:31:20 - Info bpbkar(pid=2784) accelerator sent 3495979520 bytes out of 10549121024 bytes to server, optimization 66.9%
10/02/2016 23:31:21 - Error bptm(pid=39085) system call failed - Connection reset by peer (at child.c.1306)   
10/02/2016 23:31:21 - Error bptm(pid=39085) unable to perform read from client socket, connection may have been broken
10/02/2016 23:31:22 - Error bptm(pid=39072) media manager terminated by parent process       
10/02/2016 23:31:39 - Info mediapp1(pid=39072) StorageServer=PureDisk:mediapp1; Report=PDDO Stats for (mediapp1): scanned: 10305128 KB, CR sent: 91360 KB, CR sent over FC: 0 KB, dedup: 99.1%, cache disabled
10/02/2016 23:31:41 - Error bpbrm(pid=39056) could not send server status message       
10/02/2016 23:31:42 - Info bpbkar(pid=2784) done. status: 6: the backup failed to back up the requested files

2 REPLIES 2

julien17
Level 3

no answer ?

sdo
Moderator
Moderator
Partner    VIP    Certified

Delete the contents of the \track folder on the client.   Run another full backup.   The tack log is corrupt.  It says so.  Not fixable.  Delete track log and re-run a full backup.