cancel
Showing results for 
Search instead for 
Did you mean: 

Can't select a destination client for a restore

Wile_E__Coyote
Level 4

Testing disaster recovery for our old NB5.1 install.

 

Built a netbackup server and restored the catalog. Everything's there and restorable.

 

In the GUI, the "Destination Client" tab cannot be selected.

5 REPLIES 5

Nathan_Kippen
Level 6
Certified

Can you "Edit the client list"  and manually enter one?

 

 

Stumpr2
Level 6

DOCUMENTATION: Possible reasons why the Destination Client tab is grayed out in the NetBackup Java Administration GUI

http://seer.entsupport.symantec.com/docs/241668.htm

 

 

NBU_TSE
Level 4
Employee

Hi,

 

If you are either doing a redirected restore (source and destination are different) or you backed up a cluster, then you will need to create the touch file on Master Server to allow the redirected restore from the client to work.

 

Touch file to create is either No.Restrictions or client hostname (without any file extension)

location = <install_path>\Veritas\NetBackup\db\altnames for Windows or

/usr/openv/netbackup/db/altnames for Unix

 

If altnames directory does not exist please create this, then create the appropriate touch file

 

No.Restrictions is case sensitive, this allows all clients to do a redirected restore

clientname touch file will allow just that client to do the redirected restore

 

In addition to this, you may need to add the destination client to the server list from the Backup Archive and Restore, specify NetBackup Machines and Policy Type > Edit Server List

 

What this does is add the client to the 'additional servers that can access this server' in the Client Host Properties Server list.

 

Hope this helps

Gary Yeardley (NetBackup Database Support Engineer)

Stumpr2
Level 6
If you are missing the altnames then also consider restoring the other touchfiles and configuration files from your last full backup of the master server.

Wile_E__Coyote
Level 4

It turns out to be a DNS issue.

 

I was using the Java GUI remotely, via the server's IP address because it's not in DNS yet. There is another netbackup server by the same name already on the network.

 

Once I switched to the jnbSA GUI displayed remotely from the server, everything was fine.