2.4K Posts

June 7th, 2018 09:00

According to the error message nothing seems to be worng with the resource itself - it is the fact that you cannot assign the same client/save set combination more than once to the same group.

155 Posts

June 8th, 2018 03:00

NetWorker checks for clients having same saveset in a same group. This has been around with NW 8.2 onwards. Why would you want to have multiple instance of clients having same saveset in a given group?

1 Rookie

 • 

45 Posts

June 11th, 2018 06:00

Hello Suraj

it is not the intention to add a client with the same but with a different save set! The issue is, that we are not able to create the second instance even if we use a different save set!

Regards

Christian

June 11th, 2018 12:00

Hi cbernet,

as far as I remember if one save set contains "all", no other save set (even with a different save set (e.g. only "/etc/hosts"). Did you try to renaim "all" to a different save set?

Regards

Michael

2.4K Posts

June 11th, 2018 15:00

Your method looks a bit weird to me as you never define the save set - you always update and then your create a new instance.

I think that in this case NW might always use 'all' by default.

I would run the program as follows:

...

create type: nsr client; name:abc; save set xyz

update ...

...

but never use create ... in the end.

155 Posts

June 12th, 2018 07:00

Michael Said it right, if you have a single client with All saveset specified, it will exclude the second client instance in that group:

excludes.png


So may be change the line which says update save set: All and try it again. Keep exclusive savesets.

No Events found!

Top