Policies...

[mccalia1]

Hi All,

I'm looking to see how other people have configured their Policies. At the moment, I have configured the policies by type of server e.g SQL, DATA, DOMINO, ORACLE etc.

How many policies do you have in your environment?

Is there any recommened way of defining them, or is it just based on what the business requirements are?

 

[lenski]

my life is a pain because I have to have a differant policy for each Lotus Domino server I cover. But even if I did not have to do it because of the needs of Notes I would have to do it because of the schedules so I have 96 policies.

 

[mrjazz]

A few thoughts on that:

If you have a hetereogenous set of clients (for example Windows/Unix) then you should seperate them into different policies (and use different volume pools!).
If you have applications running on a client where you use special database agents (rman for Oracle for example) then you should put those clients in an own policy.
If you have different needs for retention periods (for example do you have a development environment where you don't have to keep the data as long as in your production env).
If you have clients that can be backuped at different times (during the day, early evening, only during nighttime) then you have to create different policies.
If people want to make user initiated backups/archives you could think of put those schedules into seperate policies.

That is only a beginning for making a proper planning.

But it all depends on the size of your environment (questions like how many tape drives, storage units do you have and so on...).

You should definitely think about a policy design which is long-lasting because the re-definition is a hassle (even though it is not a complicated job) if you have to.

HTH

mrjazz

 

[JayKoonz]

We have a seperate policy for each client with the client-name as the policy-name. There may be additional policys for some clients such as clientname-DB (for the SQL servers), and the oracle database clients have a bunch of clientname-Hinstancename (Hot backup of instance), clientname-Linstancename (Log file backup of instance). Some oracle clients have 6 databases so there can be a bunch of policys for each of them.
We found having seperate policys for each client make reporting and figuring out what didn't work alot easier.

 

[day88]

Y dont you put all clients which have the same retention period, file list, schedule into one policy and configured multistreaming, etc...?
If you have too many clients, then just seperate into two or three polices, it better than one client name one policy.

Troubleshooting is the same to me... just look at the failed policy and then check the Netbackup report

To me, the lesser polices will be easier to manage.



day88

 

[Stumpr]

I start the policyname with the platform type -
UNIX-
WIN-
SQL-
ORA-
VLT-
I also have a volume pool named after the media server that "owns" the media.

Bob Stump
Incorrigible punster -- Do not incorrige