ERR - failure reading file: Microsoft SharePoint Resources:\Services\SPUserCodeV4/Metadata (TODVSQL02/90b158ba-3a23-4e54-95a5-3380db458dbe)\Metadata (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation.

[harryyu]

Hi,

Is there anybody out there ran into above error when backup SharePoint 2010 using NetBackup 7.1.0.2?

Here are environment:

NetBackup Master/Media Ver 7.1.0.2 on Solaris 10

SP 2010 Frontend Server, SP 2010 Backend Server, SQL 2005 Backend Server all servers have 7.1.0.3 client.

Policy Directive: Microsoft SharePoint Resources:\  (without GRT)

Policy Directive: Microsoft SharePoint Resources:\AllWebs (with GRT)

The Policy with GRT works fine.

The Policy without GRT has below error in Job Activity Monitor:

___________________________

03/19/2012 16:15:00 - Info nbjm (pid=986) starting backup job (jobid=579388) for client todventshrweb01.xxx.com, policy SP_DV, schedule User_Direct
03/19/2012 16:15:00 - estimated 0 kbytes needed
03/19/2012 16:15:00 - Info nbjm (pid=986) started backup job for client todventshrweb01.cmad.cibcmellon.com, policy SP_DV, schedule User_Direct on storage unit nbmaster_MSSP
03/19/2012 16:15:00 - started process bpbrm (pid=29153)
03/19/2012 16:15:01 - Info bpbrm (pid=29153) todventshrweb01.xxx.com is the host to backup data from
03/19/2012 16:15:01 - Info bpbrm (pid=29153) reading file list from client
03/19/2012 16:15:01 - connecting
03/19/2012 16:15:03 - Info bpbrm (pid=29153) starting bpbkar on client
03/19/2012 16:15:03 - connected; connect time: 0:00:00
03/19/2012 16:15:07 - Info bpbkar (pid=17264) Backup started
03/19/2012 16:15:07 - Info bpbrm (pid=29153) bptm pid: 29308
03/19/2012 16:15:08 - Info bptm (pid=29308) start
03/19/2012 16:15:08 - Info bptm (pid=29308) using 262144 data buffer size
03/19/2012 16:15:08 - Info bptm (pid=29308) using 16 data buffers
03/19/2012 16:15:10 - Info bptm (pid=29308) start backup
03/19/2012 16:15:11 - Info bptm (pid=29308) backup child process is pid 29311
03/19/2012 16:15:11 - begin writing
03/19/2012 16:15:13 - Error bpbrm (pid=29153) from client todventshrweb01.xxx.com: ERR - failure reading file: Microsoft SharePoint Resources:\Services\SPUserCodeV4/Metadata (TODVSQL02/90b158ba-3a23-4e54-95a5-3380db458dbe)\Metadata (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
03/19/2012 16:15:13 - Error bptm (pid=29311) system call failed - Connection reset by peer (at child.c.1295)
03/19/2012 16:15:13 - Error bptm (pid=29311) unable to perform read from client socket, connection may have been broken
03/19/2012 16:15:13 - Error bptm (pid=29308) media manager terminated by parent process
03/19/2012 16:15:16 - Error bpbrm (pid=29153) could not send server status message
03/19/2012 16:15:16 - Info bpbkar (pid=17264) done. status: 13: file read failed
03/19/2012 16:15:16 - end writing; write time: 0:00:05
Failed to get status code information (13)

I know there is an unsolved issue (http://www.symantec.com/business/support/index?page=content&id=TECH182628).

But my error doesn't show "Error: Unable to query the Team database meta-data."

I can't find other error message.

[Marianne]

This TN looks more relevant: http://www.symantec.com/docs/TECH162269

You will need bpbkar log to see if problem is the same.

If so, contact Symantec support as per the TN:

Symantec Engineering team is aware of this issue. A hotfix is available by contacting Symantec Technical Support and mentioning Etrack 2329716.

[harryyu]

Thank you Marianne,

I did find below error message in bpbkar log on SQL server. I will contact Symantec to get hotfix. Hope it can be fixed. I will post the result.

4:09:14.825 PM: [17264.14712] <4> tar_backup::backup_add_last_entry_state: INF - catalog message: Dfi - 0 0 72 -1 23 292 user other 0 1332187751 1332187751 1332187751 /VRTS_IMAGE_SIZE_RECORD
4:09:14.825 PM: [17264.14712] <2> tar_base::backup_finish: TAR - backup:                     3 files
4:09:14.825 PM: [17264.14712] <2> tar_base::backup_finish: TAR - backup:          file data:          0 bytes
4:09:14.825 PM: [17264.14712] <2> tar_base::backup_finish: TAR - backup:         image data:      37888 bytes
4:09:14.825 PM: [17264.14712] <2> tar_base::backup_finish: TAR - backup:       elapsed time:          5 secs         7577 bps
4:09:14.826 PM: [17264.14712] <2> tar_base::V_vTarMsgW: INF - Total Size:0
4:09:14.826 PM: [17264.14712] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
4:09:14.826 PM: [17264.14712] <4> tar_backup::backup_done_state: INF -     number of file directives found: 1
4:09:14.826 PM: [17264.14712] <2> tar_base::V_vTarMsgW: INF - Client completed sending data for backup
4:09:14.826 PM: [17264.14712] <4> tar_base::stopKeepaliveThread: INF - waiting for keepalive thread to exit ...
4:09:14.826 PM: [17264.12704] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
4:09:14.826 PM: [17264.14712] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
4:09:14.826 PM: [17264.14712] <8> tar_backup_tfi::cleanupTemp: WRN - will not cleanup 'temp' directory, debug level(s) are too high
4:09:14.826 PM: [17264.14712] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 13: file read failed
4:09:14.826 PM: [17264.14712] <4> tar_backup::backup_done_state: INF - Not waiting for server status
4:09:14.826 PM: [17264.14712] <4> dos_backup::tfs_reset: INF - Snapshot deletion start
4:09:14.826 PM: [17264.14712] <4> V_LNBackup_End: INF - V_LNBackup_End <Enter> ExitStatus:1 Recycle Logs:0
4:09:14.826 PM: [17264.14712] <4> OVStopCmd: INF - EXIT - status = 0
4:09:14.826 PM: [17264.14712] <4> OVStopCmd: INF - Shutdown stderr connection
4:09:14.826 PM: [17264.14712] <4> OVStopCmd: INF - Shutdown stdout connection
4:09:14.826 PM: [17264.14712] <4> OVStopCmd: INF - Shutdown stdin connection
4:09:14.826 PM: [17264.14712] <4> OVStopCmd: INF - Shutdown wait started
4:09:14.826 PM: [17264.14712] <2> tar_base::V_Close: closing...

[harryyu]

We have contacted Symantec and got a EEB (eebinstaller.2684271.1) which we had already installed before, that EEB can't solve our issue.

Do you know the name of hotfix or EEB for Etrack 2329716?

[Marianne]

Did you reference the etrack and TN when you logged the call?

[harryyu]

Yes I did.

But I was told that hotfix is not for our version. We are using 7.1.0.2 on master server and 7.1.0.3 on SharePoint Clients.

[Will_Restore]

Solution

Change the NetBackup Client service login account from LocalSystem to a domain account with SharePoint and local admin roles

Article URL http://www.symantec.com/docs/TECH143436

[harryyu]

Thank you for the reply,

We are using domain account on all clients.

And the above URL article mentioned the NB client version is 7.0.1

We are using 7.1.0.3 on all SharePoint clients.

[harryyu]

I compared my log with the log in above article (URL http://www.symantec.com/docs/TECH143436)

I found all messages except below line.

<2> ov_log::V_GlobalLog: INF - Failed to initialize ntFsh->dfsJunctionsToAvoid.

I think they are different issues.

[Marianne]

Please let the Symantec engineer know that the call needs to be escalated.

In the meantime, please upgrade master to 7.1.0.3 as well.

Although different  'triple-dot release' is supported (http://www.symantec.com/docs/TECH29677 ), it is never a good idea to have clients at a higher NBU version than the master, especially when database or application backup is involved.

[harryyu]

Thanks,

I did. We had a case with Symantec. No solution till now. Just try a defferent way to see if someone in this forum has same issue.

Actually, at beginning, we had client 7.1.0.2 with a hotfix, but same issue. That hotfix was included in the 7.1.0.3.

[harryyu]

Another strange thing is here.

The article says that the error messages are in front web bpbkar.log

But my bpbkar.log on front web server is empty, the messages I found in back end SQL server's bpbkar.log file instead.

[harryyu · Accepted solution]

Symantec provided a EEB ( eebinstaller.2708799.1.AMD64.exe ) solving the problem.