In most cases you can push it. I believe there are some limitations if you client has module installed, but if it is only client backup agent that is installed there should be no issue.

The big question now is, how? Where to find this function or button?

You need to create repository first. There is wizard for that available from NMC. I usually do push itself from CLI. The reason is, if you have NMC running outside backup server host (like I do), then to run this you are required to use nsrauth (no chance). However, when running nsrpush, I run it from backup server host and it works with oldauth pretty well. So, you NMC to create repository and from there is pretty much simple. I only wish I could push single binary patches that way (I just found bug on client side with 7.4.5 which I suspect won't be addressed by server side fix so I will have to update hundreds of clients manually or via script).

also need to ensure every client has enough tmp capacity for the networker kit, ran into this a lot, the annoying thing is that it removes the Kit/Package before it copies the kits across to begin the install, so the client ends up without any networker installed, and a tmp directory (i.e. /tmp) which is full......

so a few pre-req checks can save you more time in the long run when or if this occurs....

Message was edited by:
Craig Faller

Guy's Thanks. I guess this is all new to me. NMC don't ring a bell. But I asume I have to do something with nsrpush.

So this is the direction to follow or not?
Do you have a example of the rule I have to use in the CLI

Message was edited by:
Teovmy

NMC is the official GUI since 7.3.

If you do man nsrpush on Linux or UNIX you will find examples as well. If you use only Windows you can download command line reference guide for NetWorker from PowerLink documentation section for NetWorker.

I just found it. Thanks. I will give it a try

Hi Hrvoje,
Hope you are well.

I'm now using networker 7.5sp1... This feature was working fine in the version 7.4sp3 but now it's showing the message:
Upgrade initialization failed.
Unable to connect to server. Authentication failed or no valid authentication methods supported by both client and server

Is there any recommendation to start the troubleshooting?
Was changed something for ports of communication and things like that?

I have configured on firewalls these ports for backup services:
TCP src port: 1024-65535, dst port: 7937-16000
TCP src port: 1024-65535, dst port: 111-111
UDP src port: 1024-65535, dst port: 7937-16000
UDP src port: 1024-65535, dst port: 111-111

Thanks in advance!

To me it sounds as nsrauth issue. What I have seen is that if you use NMC which is not on the same host as server it requires NMC and server to use nsrauth to work when using GUI. If you call nsrpush from CLI on server than it works without nsrauth enabled.