Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Export/Import NetBackup policies

Created: 31 Aug 2009 | 4 comments
John_Nardello's picture
13 Agree
1 Disagree
+12 14 Votes
Login to vote

I'd like to see the ability to export and import backup policies. The dump ideally would be to a human-readable text format of some kind by default, although the choice of csv, html (for user-visible web-site posting), or pdf would be nice touches. =) 

The export needs to contain all information for the policy including STU, SLP, schedules, defined clients, file selections, etc. - everything you'd need to recreate it exactly.

The import command should have options to : 

  •      Overwrite the existing policy of the same name.
  •      Import with a different policy name (i.e. exported "TEST_POLICY", import it as "TEST_POLICY2").
  •      Import and set as disabled (so you can modify it further before it goes active).
  •      A verbose option, that lists all differences between any existing policy and the policy file being imported.
  •      A "trial run" import option, so that combined with the verbose option you can see exactly what would be changed if you actually imported the policy file. No actual changes would be made though. Could also be handy for regular spot-checks of policies to make sure they're still set to their user-approved configurations.

Benefits would include the ability to reset policies back to known-working pre-change configurations, easy bundling of a configuration to send to support, simplify the setup or upkeep of your DR site, or yearly Auditing reports. It would also make it easy to set up a baseline policy that gets used for all newly created policies of that type - just rename it on import, add in clients, and you're done.

Comments

Filip Mayy Hasa's picture
14
Sep
2009
0 Votes 0
Login to vote

export

 Hello,

 i am working on "export" tools. 

 Tool use bpplist command.  I export this to HTML. I use perl for it.

 How do you want import this to netbackup? Which command?

 How about other things? like volume pools, lifecycle policies and so on.
Thanks 

stanleym's picture
06
Jan
2010
0 Votes 0
Login to vote

Ideal for bulk-creation of policies.

You have my vote!

I am currently working on a script to create policies for our VMWare/VCB backups.

I would like this script to run every day before the start of the backup window so I can be sure we only run 1 backup per datastore simultaneously. However, at the moment it takes 5:30 hours just to create 151 schedules.

Having a way to generate a file with all the desired policies and schedules and then importing it should vastly accelerate this process.

Filip Hasa's picture
08
Jan
2010
0 Votes 0
Login to vote

What is your steps to create

What is your steps to create schedulke? Which command do you use? It takes really long time.

Thanks

stanleym's picture
11
Jan
2010
0 Votes 0
Login to vote

These are the commands I use

These are the commands I use to create a complete policy with calendar-based scheduling:

bppolicynew <LOC>-<TIME>-VCB-<STORE> -sameas VCB-Template-<LOC> -M %MASTER%

bpplsched <LOC>-<TIME>-VCB-<STORE> -add Diff -st INCR -M %MASTER%
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Mon 1 -rl 3 -mpxmax 8 -cal 2 -1 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Mon 2 -rl 3 -mpxmax 8 -cal 2 -1 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Mon 3 -rl 3 -mpxmax 8 -cal 2 -1 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Mon 4 -rl 3 -mpxmax 8 -cal 2 -1 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Mon 5 -rl 3 -mpxmax 8 -cal 2 -1 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Tue 1 -rl 3 -mpxmax 8 -cal 2 -2 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Tue 2 -rl 3 -mpxmax 8 -cal 2 -2 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Tue 3 -rl 3 -mpxmax 8 -cal 2 -2 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Tue 4 -rl 3 -mpxmax 8 -cal 2 -2 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Tue 5 -rl 3 -mpxmax 8 -cal 2 -2 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Wed 1 -rl 3 -mpxmax 8 -cal 2 -3 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Wed 2 -rl 3 -mpxmax 8 -cal 2 -3 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Wed 3 -rl 3 -mpxmax 8 -cal 2 -3 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Wed 4 -rl 3 -mpxmax 8 -cal 2 -3 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Wed 5 -rl 3 -mpxmax 8 -cal 2 -3 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Thu 1 -rl 3 -mpxmax 8 -cal 2 -4 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Thu 2 -rl 3 -mpxmax 8 -cal 2 -4 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Thu 3 -rl 3 -mpxmax 8 -cal 2 -4 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Thu 4 -rl 3 -mpxmax 8 -cal 2 -4 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Thu 5 -rl 3 -mpxmax 8 -cal 2 -4 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Fri 1 -rl 3 -mpxmax 8 -cal 2 -5 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Fri 2 -rl 3 -mpxmax 8 -cal 2 -5 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Fri 3 -rl 3 -mpxmax 8 -cal 2 -5 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Fri 4 -rl 3 -mpxmax 8 -cal 2 -5 75600 32400
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Diff -st INCR -M %MASTER% -weekday Fri 5 -rl 3 -mpxmax 8 -cal 2 -5 75600 32400

bpplsched <LOC>-<TIME>-VCB-<STORE> -add Full -st FULL -M %MASTER%
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Full -st FULL -M %MASTER% -weekday Sat 1 -rl 3 -mpxmax 8 -cal 2 -6 75600 118800
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Full -st FULL -M %MASTER% -weekday Sat 2 -rl 3 -mpxmax 8 -cal 2 -6 75600 118800
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Full -st FULL -M %MASTER% -weekday Sat 3 -rl 3 -mpxmax 8 -cal 2 -6 75600 118800
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Full -st FULL -M %MASTER% -weekday Sat 4 -rl 3 -mpxmax 8 -cal 2 -6 75600 118800
bpplschedrep <LOC>-<TIME>-VCB-<STORE> Full -st FULL -M %MASTER% -weekday Sat 5 -rl 3 -mpxmax 8 -cal 2 -6 75600 118800

bpplclients <LOC>-<TIME>-VCB-<STORE> -M %MASTER% -add <HOST> PC-x64 Windows2003

The bppolicynew and bpplsched commands take approx 2.5 secs, the bpplschedrep commands take approx 4.3 secs and the bpplclients commands take approx 3 secs to complete.

So, 3*2.5 + 30*4.3 = approx 136 seconds to create the policy + 3 secs per client.

The problem is that to build a calendar-based schedule I need to run a bpplschedrep command for each week of the month for each day of the week. AFAIK there is no way to say "run on all Saturdays" or "run on all Mondays".

When using frequency-based scheduling I would only need 6 bpplschedrep commands (3*2.5 + 6*4.3 = approx 33 secs) but we do not use frequency-based scheduling in our setup.