Problem/BUG creating Clients with command NSRADMIN (Windows)

It is a bit vague what now exactly leads to an error in what situation? You seem to suggest the order in which you create both client definitions matters?

Can you state exactly how you create what client definition for the same client? So both exact nsradmin statements?

Dunno if it might be something related to NW server on Windows, but as we only run linux based NW servers or NW NVE, we don't have any experience (anymore) with Windows based NW servers ourselves? But showing what you actually do, might shed a bit more light on that? Also you have to take into account that certain settings of a client, if you create multiple client definitions for the same client, are kept the same for all client definitions of that client, while other settings can be set differently for each definition. Up until nw18.2 also the client parallelism needed to be set high enough, even to accommodate using a higher PSS amount of streams, as otherwise the backup would simply fail. So from NW18.2 onwards PSS also has become better implemented...

A side note also, you are aware that NW19.3 is going out of standard support on June 30th? Also you'd be ignoring various DSA's wrg to various security vulnerabilities by still running NW19.3. Ourselves, we are waiting for nw19.7.0.4 to be released as it addresses various recent reported DSA's. Wouldn't wanna have to update again and again for yet another CVE to be addressed for already known vulnerabilities...

What nw19.3 version do you even have? The latest nw19.3.0.6 was already from Sept. 2021. There will be no fixes for nw19.3, so you'd have to go to a higher version anyways rather sooner than later to remain supported. Assuming you have a support contract?

Hi Barry,

This works: (both clients are created)

nsradmin create type: NSR Client; name:Server1.domain.com; aliases:Server1,Server1.domain.com; comment:DC1 AD; Directive:Directive2; Protection group list:Group1; save set:DC=domain,DC=com; Parallelism:6; Priority:10; backup command:nsradsave.exe

nsradmin create type: NSR Client; name:Server1.domain.com; aliases:Server1,Server1.domain.com; comment:DC1; Directive:Directive2; Protection group list:Group2; save set:All; Parallelism:6; Priority:10; Parallel save streams per save set:Enabled

This doesn't work: (getting the error for the AD backup client - second command)

nsradmin create type: NSR Client; name:Server1.domain.com; aliases:Server1,Server1.domain.com; comment:DC1; Directive:Directive2; Protection group list:Group2; save set:All; Parallelism:6; Priority:10; Parallel save streams per save set:Enabled

nsradmin create type: NSR Client; name:Server1.domain.com; aliases:Server1,Server1.domain.com; comment:DC1 AD; Directive:Directive2; Protection group list:Group1; save set:DC=domain,DC=com; Parallelism:6; Priority:10; backup command:nsradsave.exe

Enabling "Parallel save streams per save set" is a global setting for a client. So if you en- or disable it for one client definition, it will be propagated to all of its client definitions for that one client.

On a NW 19.5.0.6 server I see that if I have a client with three client definitions, in this case two for MSSQL backups and one for regular filesystem backup, that if I enable the option "Parallel save streams per save set" for the filesystem backup, that the option then is enabled for all three definitions. If I do the same for one of the two MSSQL backup definitions, then I get the same error. I even had it once, playing around with it that it was only enabled for the filesystem backup client definition and not for the MSSQL backup definitions, something that should even be possible as it is a global setting, just like the client parallelism.

BTW, you don't need to define the alias each and every time when creating definitions with nsradmin, as it will pick that up already from an existing client as it is a global client definition setting.

Haven't tested if nw19.7.0.3 shows the same behavior wrg to enabling "Parallel save streams per save set".

So it indeed is a bug as if and when it should not be enabled for client definitions that do not support it, then it also should not be enabled globally for the client through another client definition that would allow it... it is either/or. can't both be correct.

Thanks make sense. Thanks for your insight!

Ps. where did you find the EOL info?

Ps2. I added the Alias because that was ANOTHER bug I discovered, nsradmin would occasionally assign the wrong alias (the alias from the previous client it created).

It's here for anyone that needs it

https://supportkb.dell.com/attachment/ka06P000000sbpXQAQ/EMCSoftwareReleaseandEndofServiceLifeNotifications_pkb_en_US_1.xlsx

yep, as stated underneath "Service life" on https://www.dell.com/support/home/en-us/product-support/product/networker/overview.