Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error 71

Created: 13 Oct 2012 • Updated: 17 Oct 2012 | 2 comments
This issue has been solved. See solution.

Hi All,

I am facing error 71 in our environment , let me explain you in detail we have a Policy for backing CIFS SAHRES alone maped to a Active Directory server , now can anybody tell me how to fix this error

MASTER , MEDIA and CLIENTS are WINDOWS 2008 R2 and  Netbackup Version is 7.1 

 

Thanks,

Nayab

 

Comments 2 CommentsJump to latest comment

sazz.'s picture

Hi Nayab,

You are not providing enough information, where is the detailed status log?

Is it always failing with same error message?

Was it working before?

Status 71 is none of the file exist and this can happen is different circumstances

1> If the file doesn't exist and you are trying to backup that file. Eg. If you are backing up c:\temp\nbu.txt in the backup and if the file nbu.txt is removed from that folder you will get status 71

2> If you are running a job with multi streaming on

K:\mssqldumps

Q:\Mssqldumps

And if for that server q doesn't exist it will give you that error message.

3>As you are backing up CIFS through AD server, what credentials NBU client using on AD server ?

Make sure NBU client service on AD server should be started with the credentials that has access to the cifs share. If it doesn't have access that will give you status 71

 

 

SOLUTION
Marianne's picture

Requirements for backing up network shares on Windows:

1. Select 'Backup network drives' in policy attributes

2. Specify UNC path in Backup Selection

3. Change the NetBackup Client Service Logon account to a domain user with read and write permissions on the share.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links