nsrdasv: The NetWorker client is set to an invalid host name.

not really much to go by is there?

Is the filesystem backup for this client working? As that is always a good giveaway if there is a valid client to start with, instead of a NW NMDA module backup configuration if you are new to this by the looks of all other questions you had?

If some config files on client end state the client name, is that the valid one? Or was the NW client wizard used?

I also assume we are dealing with DB2, as I believe "AIX DB" isn't really a thing is it?

You'd have to share some information of what you configured and how far you came, which might better explain why you might have run into the invalid hostname thingy.

So what steps from the NW NMDA module guide did you follow and where are you at at the moment?

hello . have you found a solution for this ? I am having the same issue as well .

thanks ! 

Hi @MightyDuck03 ,

We made some change in the host entry of client and backup server. FQDN and all. After that the issue got resolved

So you don't have dns? As fiddling around with hosts files shouldn't be (always) required.

But then again NW is also notorious for needing host entries in case one has a clear separation of backup and customer facing networks, especially in case clustering is involved (and especially if it is Windows), that NW needs to deal with the names of the cluster that might not be resolvable through the DNS used for backup. Then one must revert to using host file entries.

The focus on needing to have all aliases defined for a client in the config for a NW client, is something I don't understand, causing backups even to fail if an alias is missing (the dreaded "nothing to save" error).