Video Screencast Help

How to add client from another domain.

Created: 14 Jan 2013 • Updated: 15 Jan 2013 | 4 comments
This issue has been solved. See solution.

So, have two appliances, using AIR with SLP's to make the second one a disaster recovery resource.

Went to test restoring, and got confused.   So, i'm using BAR in the second domain -- so figured have to add the client I backed up and SLP'd over to the DR domain.

Figured the best way to add the client to the domain was to create a backup policy with it in.  After all, the client software is already installed.  So, now it shows up in my "Clients" list.

BUT I can't do anything with it, since the master server in the DR domain (the 5220) isn't one of it's allowed servers.  I have already successfully went from my original (source) domain and added the FQDN of the master server in the DR domain, but obvious, if we're in a distaster scenario, my source domain isn't there.

I did find the regedit on the client (it's windows, should have mentioned that), and I think that did the trick.

BUT in a real disaster, YUCK, regediting machines before you restore them?  What am I missing.

Maybe there's an easy way to "import" a client that already has the NetBackup client software on it, and is a client in another domain

 

Oh, version 7.5.0.4 all around

 

Thanks for any tips, and sorry in advance if this is a dumb question!

Discussion Filed Under:

Comments 4 CommentsJump to latest comment

sazz.'s picture

The client should have been imported into the catalog of your DR master server if it was replicated using AIR

So it would be a normal restore the way we do.

If you are having issues please make sure that DR master is able to connect to the client. You can also try backing up clients in DR and see if they are restoring fine. The issue could be in the DR itself.

Lynne Seamans's picture

Hmm, when I did the regedit and told the machine the DR master was an "OK" server to access it, then the restore was successful, so i'm thinking I have connectivity.. 

But i do wonder if i'm missing something, cause no, the client was not in the catalog of the DR, at least it didn't show in the "Clients" list. 

The import must have worked, since I could restore.

Hmm, confused...

 

Thanks for the thinking fodder, Sazz :)

Andrew Madsen's picture

AIR images do not have a client id. So you need to look for them by name in the BAR. For the client to be populated in the BAR you need to have performed at least one backup. I am not sure if even then the AIR images will show up.

The above comments are not to be construed as an official stance of the company I work for; hell half the time they are not even an official stance for me.

Lynne Seamans's picture

Just talked to support.  Here's the deal.  YES, the DR master knows enough about the client from the import, but the client itself doesn't know the DR master as a server.   You have to tell it.

1) Windows machine (my case right now). .  open the BAR on the client.  in the "file" menu, select the "Specifiy Netbackup Machines and Policy Type"..  then click the "Edit Server List" button, and add the DR Master.  (The Regedit i mentioned accomplishes the same thing, but using the GUI is faster and safer)

2) Unix machine -- edit bp.conf  (/usr/openv/netbackup/bp.conf) and add the DR Master.

 

VOILA!  The client now knows about the DR master and will allow a restore, which you can do from the DR master (you might have to edit the client list and add) or the client itself.

SOLUTION