Unable to Add linux as client machine on netbackup aix server

[hamzafayyaz1983]

I am using Netbackup server 6.5.0 on aix machine 5.3.

I am using Netbackup client 6.5.0 on linux machine 5.0.

I am trying to add linux client in netbackup policy on the aix server but the linux client is not shown in the client drop down list in netbackup server.

Kindly suggest how to add linux client on the netbackup server on aix.

Regards,

HAmza

[matt077]

what linux are you using? (Redhat,SUSE etc)

Also can the AIX system talk to the linux system? (can you ping or ssh to it?)

[Andy_Welburn]

on your AIX master?

http://www.symantec.com/business/support/index?page=content&id=TECH56633

This is from the Install Guide:

".......
Adding a UNIX client after initial server installation
You may want to add UNIX clients after the server installation if you forgot to
select one during the installation. You may also add a new UNIX client type to
your backup environment.
To install client software later, you must first install the NetBackup client
software onto the NetBackup server.
The client CD’s installation script lets you install the client software on the
server for each of the UNIX client types that NetBackup supports. You can then
“push” this client software from the server to your UNIX clients.
To add UNIX client types to servers after initial installation
1 Mount the client CD to open a menu that displays the available client types.
2 Change your working directory to the CD directory if you have a CD or to the directory that contains the downloaded files:
cd /cd_mount_point
The cd_mount_point is the path to the directory where you can access the
CD.
3 Enter the following command to execute the installation script:
./install
The client binaries represent the operating system versions on which the binaries were compiled. Often the binaries function perfectly on later versions of the operating system. For example, Solaris 9 binaries also are used on the Solaris 10 level of the operating system. The installation procedure attempts to load the appropriate binaries for your system. If the script does not recognize the local operating system, it presents choices.
4 Select the client type that you want to load and follow the prompts to install that client type. Repeat as necessary until all the client types you want are loaded.
Make sure you load the software for all the UNIX client types you intend to back up onto the server. Otherwise, you cannot add these client types to the NetBackup policy configuration.
5 After the installation is complete, unmount the client CD.
6 Install the NetBackup client software on the clients you specified, as described in “Installing UNIX clients remotely” on page 90.

......"

[Anonymous]

Andy's solution is correct. It's a post installation routine that can sometime be forgotten, then the light bulb comes on.

You want to get the correct media from your distribution kit or fileconnect.

Heres the choices depending on you *nix client which one to install from. Probably CLIENTS2.

==== NetBackup Unix Client1 (Tru64(Alpha), HP's and AIX)

    NetBackup_6.5_CLIENTS1.tar.gz

            -Tru64, AIX and HP Risc/IA64

==== NetBackup Unix Client2 (Mac and Linux's)

    NetBackup_6.5_CLIENTS2.tar.gz

            -Mac

            -all Supported Linux: Redhat & Suse; IA64/x86/X64;

             also IBMz and PowerPC

==== NetBackup Unix Client3 (Solaris's, FreeBSD and IRIX)

    NetBackup_6.5_CLIENTS3.tar.gz

            -Solaris Sparc & X86, FreeBSD and SGI-Irix

[hamzafayyaz1983]

My Netbackup AIX server is not able to ssh netbackup client on linux.

Although i am able to ping the client machine.

2ndly the linux client libraries are not installed on the server but i have patched my netbackup server to 6.5.4

so can i install the client libraries of netbackup_client(linux) 6.5.0 on my netbackup server after patching

[Andy_Welburn]

& patch them later if required.

You may have to use the -p option to upgrade these as the install will correctly identify that the 6.5.4 patch has already been installed.

From the install directory:

Usage: NB_update.install  [-h | -i ] | [ -n ] [-d PATHNAME] [ -s ] [ -v ]

   NB_update.install allows the user to install packs found
   in PATHNAME (default is current working directory).
   Installed packs are denoted with an asterisk.


   -h    Print this help information and exits.

   -d    PATHNAME
          Pack deliverable and README files are found in PATHNAME.
          PATHNAME can be a relative or absolute pathname of
          an existing directory.
          Default PATHNAME is the current working directory.

   -i    List packs installed and exits.

   -n    Disables the check to insure the selected pack
         is being applied in the proper order and that any
         prerequisite packs listed in the README file
         have been applied.

   -p    Disables the check to insure the selected pack
         has not been previously applied.

   -s    Disables the binary save step. Pack will not be
         uninstallable.

   -v    Disables the check to insure the selected pack
         is being applied to the proper base version.

[Anonymous]

Not being able to ssh to a server is not something to do with netbackup.

Thats down to things like tcpwrappers /etc/hosts.allow /etc/hosts.deny ssh configuration firewalls etc etc..

Also check the system logs of that client you try to ssh to.

SSH connect to the netbackup client using putty client.

[J_H_Is_gone]

I have AIX master and Linux clients.

Before you can "see" the linux client option when added to a policy you have to first install the Linux client on the master server.

As they said that would be install the client2 files,  both the 6.5 and the patch to bring it up to the same level as your master.

Once you get that in, Linux will show up as an OS option when added a client to a policy.

[CRZ]

If all you need is a dropdown menu entry, and the client software is already installed on the client save some time and don't bother with installing the clients on the master. Just `mkdir` the subdirectories for the correct client type underneath /usr/openv/client on the master.

For example:

# cd /usr/openv/netbackup/client
# mkdir Linux
# cd Linux
# mkdir RedHat2.6

(I've guessed at your client - make sure it matches whatever is after "NetBackup-" in your client's "version" file)

Stop and restart your GUI and the new entry should appear in your dropdown.

[Alexis_Gonzalo_]

Why does a UNIX NB Server requires the UNIX client binaries, but not the Windows binaries?

And why does a Windows NB Server doesn't require UNIX client binaries at all?

Finally, what is the purpose of installing the client binaries in a NB Server, apart from the dropdown menu entry? Apart for remote installations/upgrades, I don't understand the need for this.

[J_H_Is_gone]

For UNIX,

I have UNIX master, and if I install RS6000, Linux, Mac and Sloris client binaries on my master.....

I can open the java gui, go to properties, actions install UNIX clients and PUSH the upgrade to all my UNIX clients.

So upgrade by hand 2 or more hours, push from the gui (when it works) 5 minutes.

[Andy_Welburn]

Might as well by default have all possible O/S's in the drop-down irrespective of whether the client binaries are installed on the master or not!

In all honesty I don't see any advantage for this to be as it currently is.

[matt077]

ssh was only to see if the systems would talk

like he said the systems can ping so ruled out a connection problem