NetBackup Policies

[glenr98]

We are currently evaluating NetBackup 4.5. Our environment consists of approx 30 servers. I know that each server must be associated with a policy, but what is the recommended way to group servers together? We dont necessarily want to use the ALL_DRIVES option. Also we would like to maintain a degree of independance with schedules etc. Can anyone provide examples of existing policies?

Regards,

Glen

 

[birky]

Hi

We have just implemented DC 4.5 and we have around 70 clients.

We grouped the policies by naming them [hostname] apps , [hostname] home and [hostname] os.

So we have 3 policies for each client grouped into easy sections.

 

[johnny99]

We just implemented NBU 4.5 and until we get more used to the product we will use a policy for:

each SQL and Exchange server
all our internet servers (4)
all file servers
all user backups
all other win2K servers
all other NT servers

later we expect to group some of the SQL servers together and all 3 Exchange servers together.

/johnny

 

[bswip]

We have over 250 servers that we backup with different OS'. What we have done to segregate is to use the OS first and then the type (i.e. NT-Web, W2K-DC, AIX-Oracle, W2K_Sql, etc...) Each policy has the same class (Weekly_Full, Monthly_Full, Daily_Differential, etc...) In each policy, every class can have a different schedule.

This enables us to use vaulting by class (i.e. Weekly_Full, etc..)

You can fine tune and segregate your servers as much as you like, but remember you will have to manage them...

Netbackup is an excellent product but does require some very good planning. Don't try and implement a quick solution because you may regret this down the line.

 

[PGPhantom]

I agree with BSWIP - Carefully lay out what you want. What I did for our policies etc is that they are grouped by location, then evvironment e.g.

loc1_nt_servername_exch
loc1_nt_servername_sys
loc2_ux_servername_sys
loc2_ux_servername_orac
etc ...

Then in each policy there are multiple schedules - For each class type they are named the same as in...

sys_incr
sys_full
sys_mnth
orac_full_6
orac_full
orac_mnth
etc ...

As you can see - Everyone has their own methodology - It is what ever suits your environment - I just see policies etc as a convenient Administration tool - To make it easier for me.