status 13
Created: 21 Feb 2012 | Updated: 27 Feb 2012 | 4 comments
This issue has been solved. See solution.
Hi, my master server and media servers are all NBU 7.1 on Windows 2008 R2 SP1. We have some old clients which are backed up by an old NBU 6.5.3 master server (windows 2003, NBU 6.5.3.1).
One of these client is a SharePoint server (SharePoint 2007, Windows 2008, NBU 6.5.3). I moved this SharePoint server to be backed up by the NBU 7.1 media server. The SharePoint backup completed successfully but the file system backup of this client failed with status 13. The NBU version in this SharePoint server is still 6.5.3. I only change the server entry in the registery of the SharePoint server and restart the NBU services.
Does anyone see similar issue before? Thanks.
Discussion Filed Under:
Comments 4 Comments • Jump to latest comment
Status 13 can be many things - a file read error, a network read error, a network timeout.
As a start, please copy all the text in the Details tab of the job and post here.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Marianne makes a good point, especially about the timeout
Work checking the Client Read timeout setting on the Master / Media Servers - it may be that in your V7.1 environment they have not been set as high as your V 6.5.3 environment
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
if there is any NFS mount point ..... and NFS service not started then also backu pwill fail with 13.
Thanks for all your replies. With the help of Symantec support, we found it is due to VSP. The resolution is to upgrade the client from NBU 6.5.3 to 7.1.
Would you like to reply?
Login or Register to post your comment.