cancel
Showing results for 
Search instead for 
Did you mean: 

NAT-ed Client Connectivity Failed

riazjee
Level 4

Dear All,

 

We are running Netbackup 7.6.0.1. We have a NAT-ed client (we will backup plain OS files from this client and probably restore, too, if required). While trying to check the basic connectivity between Master server and client (by following http://www.symantec.com/connect/forums/how-can-we-do-basic-netbackup-troubleshooting-windows-any-aspect), the name resolution check is failed:

From Client

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -pn


expecting response from server <Master Server Name>
10.X.X.X *NULL* 10.X.X.X 61889

Where 10.X.X.X is the NAT-ed IP Address. Can you please guide how to resolve this issue so that we can take files backup? Once the connectivity issue is resolved, we will be performing two tests:

(1) Backup Files from NAT-ed server

(2) Restore Files to NAT-ed server

 

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

Using NAT with Netbackup is not supported

Network Address Translation and Port Address Translation are not supported for Symantec NetBackup (tm) 6.x and 7.x

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

You are seeing name resolution problems because NAT changes the IP source address. Netbackup IP address is also enclosed in the IP packet as part of the Netbackup security model.

You can try to configure the client host file so the NAT address resolves to the master server name, but I doubt it will work.

View solution in original post

1 REPLY 1

Nicolai
Moderator
Moderator
Partner    VIP   

Using NAT with Netbackup is not supported

Network Address Translation and Port Address Translation are not supported for Symantec NetBackup (tm) 6.x and 7.x

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

You are seeing name resolution problems because NAT changes the IP source address. Netbackup IP address is also enclosed in the IP packet as part of the Netbackup security model.

You can try to configure the client host file so the NAT address resolves to the master server name, but I doubt it will work.