cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup 7.6.1.2 is unable to backup sparse file

DBA
Level 1

Hi all,

Last week we upgraded our netbackup from 7.0.1 to 7.6.1.2 and we started having problem 

backing up Mongodb replica via snapshot.

We receive this error: 

07/04/2015 01:05:31 - Error bpbrm (pid=24670) from XXXXX: ERR - Wrote 1491340544 of 2146435072 bytes from file YYYYYYYY - No such file or directory

Yes, it is a sparse file but this ends my backup with status code "the requested operation was partially successful  (1)"

The worse thing is that if we try to restore that files netbackup continues writing untill filesystem is full and at the end deletes the file.

SO THEY ARE UNRECOVERABLE!

We tried the same operation with netbackup 7.0.1 and all went fine!

We opened a case with Symantec and they recognize the issue but they said that there will take long time to debug and have a patch.

Are we the only ones having this kind of problem?

 

1 ACCEPTED SOLUTION

Accepted Solutions

watsons
Level 6

sparse file could be a problem as shown here:

http://www.symantec.com/docs/TECH209380

Check bpbkar logs to see if files like that was handled correctly, if there is any error, call Support to report the issue. The entry "IGNORE_SPARSE_FILES = 1" in bp.conf might work but skipping it may mean restore would be an issue.

View solution in original post

2 REPLIES 2

Marianne
Level 6
Partner    VIP    Accredited Certified

I have not seen this issue or heard of customers or other forum members experiencing this issue. 

Issue is also not mentioned in NBU 7.6.1 Late Breaking News:  http://www.symantec.com/docs/TECH227580  

Keep working with Symantec Support to get call escalated to backline and Engineering until a solution is found.

watsons
Level 6

sparse file could be a problem as shown here:

http://www.symantec.com/docs/TECH209380

Check bpbkar logs to see if files like that was handled correctly, if there is any error, call Support to report the issue. The entry "IGNORE_SPARSE_FILES = 1" in bp.conf might work but skipping it may mean restore would be an issue.