Holiday Wish List for NetWorker

NetWorker really does need a much more granular security model. Last year I outlined a theoretical change that could be made:

http://nsrd.info/blog/2009/11/18/enhancing-networker-security-a-theoretical-architecture/

I agree with Preston. I think it's logical the way Microsft does AD policies. If you specify a setting specificly on a client that belongs to a OU, the specific setting you put on the client will overwrite. Then again, you have a setting on the OU that you can use that says, No Owerwrite.

I've had many situations where sucha a design would had benefitted our environment. All our clients have default schedule and get the schedule from the group. It would be so nice, if other than default schedule was configured on client, that schedule would overwrite the group schedule.

Johannes

Another thing to put on the wish list:

I wish the “NetWorker Software distribution feature” as it’s called in the admin guide would be made so it fulfills its name and become a true software DISTRIBUTION feature, not just software UPDATE feature.

It shouldn’t be so hard. e.g. most anti virus software has this kind of feature. NetWorker should be able to list up servers (possible NetWorker clients) on the network and push the correct package after successfully sending admin logon credentials to that client.

I use silent install scripts to distribute the clients. But that has its drawbacks.

Johannes

ooh, I'm called Preston now ;-)

Boris,

as said, the schedule. Many many times I've wanted to say I want this default policy, but I want client x to be slightly different.

I'd like to see NetWorker on the Mac integrate with Time Machine, much like the module for Microsoft Applications currently integrates with Microsoft's Backup tool.