We get away with this nice simple setup by driving all backups from Oracle's
crontab.  This is good for two reasons, one - nice simple policy setup.  The
other reason is that this allows the DBA's to do all their own scheduling. I
have 24x7 schedules and it's nice to keep the control with the DBA's.  If
they screw up, it's not my fault.
-m

-----Original Message-----
From: Wayne T Smith [mailto:WTSmith AT maine DOT edu]
Sent: Tuesday, November 18, 2003 10:23 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Backing up Thousands of Databases


Donaldson, Mark wrote, in part:
> We're nowhere as near the DB count you have but we do use one policy for
all
> our database backups.  I have multiple schedules within that policy that
> define different storage units.  We've decided on a consistent retention
> time so all the schedules have the same.  Multiple schedules are just to
> choose the storage unit.
> 
> I don't see any reason to create a policy for each DB or, for that matter,
> for each server.  

(...going on somewhat of a tangent ...)

But you need a template or shell script for each DB?

I've been confused by the NBU Oracle Admin Guide that says ...

: Because backup templates are stored on the server
: in a known location, server directed and scheduled
: backups will use the same copy of the template for
: each client in the policy client list.

since the templates (that we've created) are very specific to each DB. 
Have I missed something?    cheers, wayne

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