I don't care what it looks like as long as it is documented and it can
be manipulated.  It could be an xml file for all I care.  How it looks
is not as important as being able to do the export/manipulation/import
of a policy or group of policies.  We had something like that at my last
job, but we scripted it ourselves and we had to make it conform to a
strict set of rules that we defined up front.  Plus it was limited in
what we could do with it (no calendar-based policies for example).  And
the way we made it work was using a set of the NBU CLI's underneath.

If we can get something like that to work in a limited fashion, then why
can't Symantec get something that is full-blown, feature-full,
documented script or program to do the same kind of thing?

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of A Darren
Dunham
Sent: Thursday, April 10, 2008 4:57 PM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Auburn vs Netbackup forums- Was:
sniff...bpgpisgone from 6.5

On Thu, Apr 10, 2008 at 06:30:55PM -0400, Stuart Liddle wrote:
> I (and others) are looking for something that will Export a policy or
> policies to something like a csv file.  Then manipulate that file if
> necessary and Import back into the system.  You know, tweak the
storage
> unit here and the schedule there...  If you can do it for one policy,
> then you can easily use it to make new ones or move them from one
system
> to another or make bulk changes.  

How would you want it to look?  

Right now there's a single text file for all the simple items in the
policy (backup type, Pool, STU, ...), there's a single file for the
clients, there's a single file for the include list, and then there's a
directory with files for each schedule.

The only one of those that seems incredibly cryptic is the "Calendar"
file within the schedule (assuming you're using Calendar backups).  The
others have pretty good variable names.

I don't think having a single CSV would be nice to work with due to the
multiple client, backuplist, and schedules possible in a policy.  If you
do that, you end up with something like the output of 'bpdbjobs
-all_columns' and parsing it becomes very difficult.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu