bootstrap saved despite skip

Sorry to say but as far as I'm aware - that's what it's supposed to do now in v7.3.x. Check the knowledgebase support note 57733 or the man page for savegrp: states that if the Networker server is not a member/client of the group you're running, it will save the bootstrap every time.

I believe Networker used to do this back in v6.x.x, but was changed in v7.2(I think).. and now obviously changed back in v7.3.x.

You could try adding a new client entry for your server to the savegroup, which saves something small like a log file - make sure this client entry uses the same schedule as the other systems in the group and that should stop it from saving the bootstrap when all the other clients in the group skip.

We're currently running v7.2.2 and the bootstrap isn't saved on skipped groups.

HTH,
John

The Server is a member of both groups. So 57733 doesn't match.
group F: level=full on Sa, level=skip other days
group 1: level=1 on Di-Fr, level=skip other days
NW saves bootstrap twice per day.

Hmmm.. If it's just a single server environment, then you could possibly disable autostart in your savegroups, and then just schedule the savegrp commands from cron/at/etc to run on the correct day.

It's a bit of a dodgy work-around, but at least the bootstrap isn't backed up multiple times. Apart from that, I think you're going to need to get support involved and probably have an RFE raised for this to get a permanent fix.

Skip applies to data - bootstrap is special data set to which this doesn't apply probably. Without checking your resources it is hard to say why it works they it works for you (what you are tying should however should work) so the best bet is to have it opened with your support.

I do not agree that this should be handled as RFE as there is no document showing any change in 7.3.x from previous versions and unless this is a resource configuration issue - previous versions used to handle this differently (7.1.x for example). EMC can't claim RFE once proved there is a difference with how it works with previous versions (unless documented).

Did you get this fixed and is the a Bug fix, since I am running 7.3.2.Build.364 and get the same problem. I never had it with 7.2.x (I think).

Thanks