Today we are going through, how to use Networker client push features
Use the software distribution feature, Client Push, to update the NetWorker and module software on NetWorker hosts in the datazone from the NetWorker server. By using this feature, you do not need to log in to each host and manually uninstall the old NetWorker software version and install the new NetWorker software version.
You cannot use Client Push to update a clustered host, an NMM 2.4.x or earlier client, aYou cannot use Client Push to update a clustered host, an NMM 2.4.x or earlier client, aNetWorker server, an EMC License Manager server, a Console server, a PowerSnap client,or an OS-X client.
There are two different scenarios to consider when preparing the software repository toupdate the NetWorker software by using Client Push:
1. The NetWorker server is the same operating system as the target hosts
2. The NetWorker server and target host operating systems differ
The NetWorker server is the same operating system as the target hosts:
When the target hosts are the same operating system as the server, extract each software
packages to the Media Kit Location. The Media Kit Location must reside on a file system
that is local to the NetWorker server.
The NetWorker server and target host operating systems differ:
When the operating system of the target hosts differs from the NetWorker server, for
example, when a Windows NetWorker server updates a UNIX client, you must configure a
proxy host to store the cross-platform packages.
Here I am only go with The NetWorker server is the same operating system as the target hosts.
Procedure:
4. On the Welcome to the Software Administration Wizard window, click Next.
5. On the Select Operation window:
a. Select Add or remove products from my software repository.
b. Click Next.
6. On the Software Repository Operations window:
a. Select Add software products to the repository.
b. Click Next.
7. On the Create Software Repository window:
a. Click Yes.
b. Click Next.
8. If this is the first time you are creating the repository, specify the Repository location,
and click Next .
The default location differs on Windows and UNIX:
Windows: NetWorker_install_dir\repository
UNIX: /nsr/repository
9. On the Select platform type window:
a. Select the platform type of the software to add to the repository.
b. Click Next.
10. On the Add software products to repository window:
a. Click Yes .
b. Click Next.
11. On the Media Kit Location window:
a. Specify the path to the Media Kit location.
As per Unix admin I received path “/data/depot/networker/LINUX/x86_64lgto/linux_x86_64.v8113/”
b. Click Next.
12. The Select Products window contains a list of detected software packages in the
repository:
a. Select the products to add to the repository.
b. Click Next.
Inventorying the target hosts for installed products:
Before you can update the NetWorker software on a host, you must inventory the host to
determine the installed versions of NetWorker software.
After Configure all these things you can go ahead with upgrade:
Procedure:
1. Start the Software Administration Wizard and click Next.
2. Select Upgrade the software on my NetWorker clients, and click Next.
3. Select the option By Client, will upgrade on the clients that you select, and click Next.
4. Select the appropriate hosts, and click Next
5. In Product available for upgrade select the client again and click next
6. The Monitor Activity window appears and provides the status of upgrade job in the
top table and the status of each client upgrade operation in the bottom window, for
the selected upgrade job. When the upgrade job contains many clients, the job might
take awhile to complete.
Upgraded client successfully: - As per above process we are able to upgrade Linux client from server client push features.
Use the software distribution feature, Client Push, to update the NetWorker and module software on NetWorker hosts in the datazone from the NetWorker server. By using this feature, you do not need to log in to each host and manually uninstall the old NetWorker software version and install the new NetWorker software version.
You cannot use Client Push to update a clustered host, an NMM 2.4.x or earlier client, aYou cannot use Client Push to update a clustered host, an NMM 2.4.x or earlier client, aNetWorker server, an EMC License Manager server, a Console server, a PowerSnap client,or an OS-X client.
There are two different scenarios to consider when preparing the software repository toupdate the NetWorker software by using Client Push:
1. The NetWorker server is the same operating system as the target hosts
2. The NetWorker server and target host operating systems differ
The NetWorker server is the same operating system as the target hosts:
When the target hosts are the same operating system as the server, extract each software
packages to the Media Kit Location. The Media Kit Location must reside on a file system
that is local to the NetWorker server.
The NetWorker server and target host operating systems differ:
When the operating system of the target hosts differs from the NetWorker server, for
example, when a Windows NetWorker server updates a UNIX client, you must configure a
proxy host to store the cross-platform packages.
Here I am only go with The NetWorker server is the same operating system as the target hosts.
Procedure:
- Login to the NMC console with a user that is both an NMC administrator and a member of the Application administrators user group on the NetWorker server.
- Connect to the NetWorker server in NMC.
- In the Configuration menu >>>Select Configuration tab as below and, select Software Administration Wizard.
4. On the Welcome to the Software Administration Wizard window, click Next.
5. On the Select Operation window:
a. Select Add or remove products from my software repository.
b. Click Next.
6. On the Software Repository Operations window:
a. Select Add software products to the repository.
b. Click Next.
7. On the Create Software Repository window:
a. Click Yes.
b. Click Next.
8. If this is the first time you are creating the repository, specify the Repository location,
and click Next .
The default location differs on Windows and UNIX:
Windows: NetWorker_install_dir\repository
UNIX: /nsr/repository
9. On the Select platform type window:
a. Select the platform type of the software to add to the repository.
b. Click Next.
10. On the Add software products to repository window:
a. Click Yes .
b. Click Next.
11. On the Media Kit Location window:
a. Specify the path to the Media Kit location.
As per Unix admin I received path “/data/depot/networker/LINUX/x86_64lgto/linux_x86_64.v8113/”
b. Click Next.
12. The Select Products window contains a list of detected software packages in the
repository:
a. Select the products to add to the repository.
b. Click Next.
Inventorying the target hosts for installed products:
Before you can update the NetWorker software on a host, you must inventory the host to
determine the installed versions of NetWorker software.
After Configure all these things you can go ahead with upgrade:
Procedure:
1. Start the Software Administration Wizard and click Next.
2. Select Upgrade the software on my NetWorker clients, and click Next.
3. Select the option By Client, will upgrade on the clients that you select, and click Next.
4. Select the appropriate hosts, and click Next
5. In Product available for upgrade select the client again and click next
6. The Monitor Activity window appears and provides the status of upgrade job in the
top table and the status of each client upgrade operation in the bottom window, for
the selected upgrade job. When the upgrade job contains many clients, the job might
take awhile to complete.
Upgraded client successfully: - As per above process we are able to upgrade Linux client from server client push features.
