Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Automate adding Windows client to existing policy via script on client

Created: 29 Jul 2013 • Updated: 14 Aug 2013 | 3 comments
This issue has been solved. See solution.

Our Netbackup server runs on Unix, and backs up both Unix and Windows clients.  I know how to manually add a client to a policy using the console.  I also know that you can run scripts on the master server to add clients to a policy.

My question:  Is there a way to run script from the Windows client computer that will add the computer to an existing backup policy?  I would like to add this script into our imaging process to ensure that all new computers are automatically added to a policy.

Operating Systems:

Comments 3 CommentsJump to latest comment

Stuart Green's picture

With a UNIX master and Windows clients, I cannot think of a way there is within the software to send from the Client its details INTO a policy on the master.

Theoretically you include in your image putty and automate running a command that has been populated by client name, as part of the image build. This command could be run and executed on the UNIX master... although I would place some authentication mechanisms between the two.
http://stackoverflow.com/questions/6147203/automating-running-command-on-linux-from-windows-using-putty

Or just include the adding of the client into a backup policy as part of the server build standards.

Fire off some email via blat within the image build to remind the backup admin group to add this into a policy.

If clients are VM's then this can be fully included for backup as part of VIP.

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

SOLUTION
Marianne's picture

There are no commands included in client binaries that could be executed to update policies.

Policy commands are all in the admincmd folder and only exist in server or Windows Admin Console installation.

There are unfortunately limits to any kind of automation. Stuart's suggestions seems to be your best bet.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links