cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to take the Backup

avsupport
Level 3
Product : Net Backup
Version : 6.5
Master & Media server on Redhat 4 update 3 on single system
  2 Windows Clients.

Hi All,

We have installed netbackup server on Linux platform and installed a client on Addl Domain Controller (Win 2003) server.
When we initiate a backup it fails with a error " access to the client was not allowed".



1 ACCEPTED SOLUTION

Accepted Solutions

Ajju
Level 4
Hi,

Some Key things to check:

Check the host file entry of both Master Server and the Client.
(In the host file add the local machine IP addr and Hostname, in both the Server and Client
ie., in Master Server host file add the Master server IP and Hostname)

Check the version of the Netbackup installed on the Client.

Check the Services of the NetBackup Client.

Check the Antivirus Rules and services running (Which Antivirus have you installed).

Check the Windows firewall (Disable the services).



 

View solution in original post

14 REPLIES 14

lknishad
Level 3
Certified
Please check the communication between client and server by using the bpclntcmd command


#bpclntcmd -ip <ip address of backup server>

#bpclntcmd -hn <hostname of backup server>

lknishad
Level 3
Certified
you can use telnet <hostname of client> bpcd .

which can make sure client software is installed in client system.

lknishad
Level 3
Certified

From Symantec



Message: access to the client was not allowed

Explanation: The master or slave server is trying to access the client, but the server is not recognized by the client as a valid server.

Recommended Action:

1.      If the server is a valid server, verify that it is in the server list on the client.   If necessary add it as follows:

o        On Windows NT, 98, and 95 clients, add the server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

o        On UNIX, and Macintosh clients, add a SERVER entry in the bp.conf file.

o        On NetWare target and OS/2 clients add a SERVER entry in the bp.ini file.

If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes to take effect. On Windows NT, stop and restart the NetBackup Request Manager and NetBackup Database Manager services.

2.      On Windows NT clients, enable bpinetd activity logging as follows:

a.    Create a bpinetd activity log directory on the client.

b.    Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

c.    Retry the backup and examine the resulting logs to determine the cause of the failure.

1.      On all but Macintosh clients, enable bpcd activity logging as follows:

a.    Create a bpcd activity log directory on the client.

b.    On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

c.    On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

d.    Retry the backup and examine the resulting logs to determine the cause of the failure.

2.      On Macintosh clients, check the inetd and bpcd activity logs. Both logs are created automatically.

o        Check the inetd log to see if NetBackupListen is running.

o        Check the bpbkar and tar messages in the bpcd log file.  To increase the amount of information included in the logs, set the loglevel parameter in the mac.conf file to a higher value.

1.      Check the bpcd activity log to determine the server's peername and what comparisons are being made.  The bpcd process compares NetBackup server list entries to the peername of the server attempting the connection and rejects the connection if the names are different. If necessary, change the server list entry on the client to match the peername.

2.      On Windows NT clients, check the following:

o        Verify that NetBackup for Windows NT software was installed under a Windows NT administrator account.

If NetBackup is under another type of account, reinstall it under an administrator account. The installation will complete successfully under a non-administrator account but the NetBackup Client service is not added to Windows NT and the NetBackup server cannot access the client.

o        Verify that the Windows NT TCP/IP service specifies the domain server that resolves names for the subnet that contains the NetBackup servers.  UNIX and Windows NT clients are frequently not on the same subnet and use different domain servers. When this condition exists the NetBackup servers and Windows NT clients may be able to ping one another, but the server is still unable to access the Windows NT client.

3.      If the preceding steps do not resolve this problem, see "Resolving Network Communication Problems" on page 21.
 

avsupport
Level 3
Hi,
Thanks for the steps.

As per the above steps provided I have already tested the communication and telnet, it is working fine.
Even configured as per the admin guide.

But the problem is that moment the Back up job is fired it allocates the tape and says "begin wiriting"

and hangs.

Ajju
Level 4

Enable the logs and verfiy

Go to the client
 Open netback up client console
Select Netbackup Client Properties
Select Troubleshooting
In Debug
                  Select General to 2

                              Verbose to 5

Check the logs in
Program Files\Veritas\NetBackup\logs\bpcd

lknishad
Level 3
Certified
What status code you are getting the same 59 or some other status code.

Ajju
Level 4
By default the status code should be 59.

But in symantec there is no much info about it.  It only talks about the Ip addr

avsupport
Level 3
Yes the error code is 59.

avsupport
Level 3

I got this doc which talks about the comm issue but all these are configured.


ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/277539.pdf

lknishad
Level 3
Certified
Go ahead check the logs .... bpcd this docs just have the flow for 59.

Amit_Karia
Level 6

Are you able to do bpcoverage from media server  to client

/usr/openv/netbackup/bin/admincmd/bpcoverage -c <clientname>

in your clients make sure all  media servers are having entry

for unix and linux client /usr/openv/netbackup/ bp.conf

for windows client

backup archive and restore -> specify server -> servers

 



 

Nicolai
Moderator
Moderator
Partner    VIP   

Each client has a server list witch specify what host are authorized to perform the backup. You got the list wrong on the client.

Start the Backup /Restore GUI on the client -> File -> Specify netbackup Machines and Policy. Check the server list section. You're master server must be listed here and marked "Current". Add media server if you have any. Use full qualified domain names. Click OK and retry the operation.

regards

Nicolai

PS: make sure DNS is in place and able to  perform normal and reverse lookup.


Ajju
Level 4
Hi,

Some Key things to check:

Check the host file entry of both Master Server and the Client.
(In the host file add the local machine IP addr and Hostname, in both the Server and Client
ie., in Master Server host file add the Master server IP and Hostname)

Check the version of the Netbackup installed on the Client.

Check the Services of the NetBackup Client.

Check the Antivirus Rules and services running (Which Antivirus have you installed).

Check the Windows firewall (Disable the services).



 

avsupport
Level 3
Thanks for the solution after adding the Hostname entry in the local system and disable the Windows firewall service, I'm able to take the backup.

I have verfied the Net backup Client and Server both are having Version 6.5 and in the bp.conf file it was added.