Welcome! » Log In » Create A New Profile

Maximum number of policies

Posted by Anonymous 
Maximum number of policies
July 20, 2007 03:46AM
Hi

I have an NBU 5.1 installation with one master server (Solaris 9) and 6 media servers (RHEL4, Windows 2003).

I´ve just created the 101st policy. The problem I´m running into is that apparently the scheduler is simply ignoring
the backup window configured (it was supposed to start at 8pm but the job only is added to the queue around 2am).

My question is: NBU 5.1 may have some kind of 100 policies limitation? Has anyone here with more than 100 policies/classes in place?

Thank you
Maximum number of policies
July 20, 2007 06:43AM
Hi
Well I know of a site that had 120 policies, but never reported an issue. Although its alot, I am not personally aware of any recommendation that states what the limit should be.

Are you sure the frequency is right and the policy is enabled correctly ?

If at all possible, can you consolidate any of your existing policies and merge them ?

[i]Regards[/i]
[i]Simon Weaver
[b]3rd Line Technical Support
Windows Domain Administrator[/b][/i]
[i]EADS Astrium Limited, B23AA IM (DCS)[/i]
[i]Anchorage Road, Portsmouth, PO3 5PU[/i]
[i]Email: [/i][i]Simon.Weaver < at > Astrium.eads.net[/i] ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 20, 2007 07:01AM
Hi,

we are running NB 5.1 MP6 with around 1100 policies and over 1600 clients.  We have been having problems with the scheduler not starting things when they are supposed to start.  The one thing that is very important is to have the proper settings in the /etc/system file for shared memory.  If you don&#8217;t have this set correctly, you WILL have problems with the scheduler.

We had a case open with Symantec/Veritas about this and basically we were told that it would be best to upgrade to 6.x because the scheduler has been completely re-written and is much more efficient.  We hope to upgrade to 6.5 later this year.  In the mean time we have to figure out creative ways to deal with the problems of the scheduler getting bogged down.

I believe that you should not have problems with only 100 policies if you have your memory settings correct in /etc/system.

good luck.

--stuart

[b]From:[/b] veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto] [b]On Behalf Of [/b]WEAVER, Simon (external)
[b]Sent:[/b] Friday, July 20, 2007 6:42 AM
[b]To:[/b] 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
[b]Subject:[/b] Re: [Veritas-bu] Maximum number of policies

Hi

Well I know of a site that had 120 policies, but never reported an issue. Although its alot, I am not personally aware of any recommendation that states what the limit should be.

Are you sure the frequency is right and the policy is enabled correctly ?

If at all possible, can you consolidate any of your existing policies and merge them ?

[i]Regards[/i]
[i]Simon Weaver[/i][i]
[/i][b][i]3rd Line Technical Support[/i][/b][b][i]
[b]Windows Domain Administrator[/b][/i][/b]
[i]EADS Astrium Limited, B23AA IM (DCS)[/i]
[i]Anchorage Road[/i][i], Portsmouth, PO3 5PU[/i]
[i]Email: [/i][i]Simon.Weaver < at > Astrium.eads.net[/i] ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 20, 2007 07:11AM
sounds like the frequency is interfering.

if your frequency is set to 12 hours, adn the job last ran at 2pm, it doesn't matter that the window is set to open at 8pm, the job will not queue untill 2am.

Paul

--
[quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 20, 2007 11:07AM
Thank you very much, guys. I feel a big relief knowing that people out there has more than 100 policies running.

The policy schedule is calendar based. I´m going to check deeper to see what´s going on.

Thanks again.
edson

On 7/20/07, [b]Paul Keating[/b] <pkeating < at > bank-banque-canada.ca ([email]pkeating < at > bank-banque-canada.ca[/email])> wrote: [quote] sounds like the frequency is interfering.

if your frequency is set to 12 hours, adn the job last ran at 2pm, it doesn&#39;t matter that the window is set to open at 8pm, the job will not queue untill 2am.

Paul

--
[quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 20, 2007 01:11PM
I&#8217;ve got customers with THOUSANDs of policies with no major ill effects.  In 6.0 I&#8217;d say there are no effects at all.  In pre-6.0, I&#8217;d say that there is some slowness getting all of the jobs running in a multi-thousand job environment (takes a while for the scheduler to read the config for that many policies), so we just moved the start window up a bit.  But post-6.0, I&#8217;ve got non worries.

---
W. Curtis Preston
Backup Blog < at > [url=http://www.backupcentral.com]www.backupcentral.com[/url]
VP Data Protection, GlassHouse Technologies

[b]From:[/b] veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto] [b]On Behalf Of [/b]Edson Noboru Yamada
[b]Sent:[/b] Friday, July 20, 2007 11:05 AM
[b]Cc:[/b] Veritas-bu < at > mailman.eng.auburn.edu
[b]Subject:[/b] Re: [Veritas-bu] Maximum number of policies

Thank you very much, guys. I feel a big relief knowing that people out there has more than 100 policies running.

The policy schedule is calendar based. I´m going to check deeper to see what´s going on.

Thanks again.
edson

On 7/20/07, [b]Paul Keating[/b] <pkeating < at > bank-banque-canada.ca ([email]pkeating < at > bank-banque-canada.ca[/email])> wrote:
sounds like the frequency is interfering.

if your frequency is set to 12 hours, adn the job last ran at 2pm, it doesn't matter that the window is set to open at 8pm, the job will not queue untill 2am.

Paul

-- [quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 22, 2007 11:24PM
[b][i]1,100 policies!!!!!![/i][/b]

[i]Regards[/i]
[i]Simon Weaver
[b]3rd Line Technical Support
Windows Domain Administrator[/b][/i]
[i]EADS Astrium Limited, B23AA IM (DCS)[/i]
[i]Anchorage Road, Portsmouth, PO3 5PU[/i]
[i]Email: [/i][i]Simon.Weaver < at > Astrium.eads.net[/i] ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 03:52AM
Just to add to Stuart&#8217;s comment, NB6 reads policies according to refresh rate and when policies change. These are done by nbpem.
You can also refresh manually, via command or restart of NB (not the best way to do this)

Some handy hints:

- For those who do not know there is a setting for policy refresh on the master, default is 10min I think ? (host properties/master/global attr)

- Manual refresh can be done via : nbpemreq -updatepolicies

- This touch file stops nbpem doing refreshes unless you issue the nbpemreq command : /usr/openv/netbackup/bin/[b]PolicyStrategy[/b]
[b] [/b]

[b]From:[/b] WEAVER, Simon (external) [mailto]
[b]Sent:[/b] Monday, 23 July 2007 4:20 PM
[b]To:[/b] 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
[b]Subject:[/b] Re: [Veritas-bu] Maximum number of policies

[i][b][i]1,100 policies!!!!!![/i][/b][/i]

[i]Regards[/i]
[i]Simon Weaver[/i][i]
[/i][b][i]3rd Line Technical Support[/i][/b][b][i]
[b]Windows Domain Administrator[/b][/i][/b]
[i]EADS Astrium Limited, B23AA IM (DCS)[/i]
[i]Anchorage Road[/i][i], Portsmouth, PO3 5PU[/i]
[i]Email: [/i][i]Simon.Weaver < at > Astrium.eads.net[/i] ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 12:47PM
Yeah&#8230;.we realize that NB 6.x is a total re-write of the scheduler&#8230;we can&#8217;t wait to upgrade.  But we have to wait for all of the clients that we backup to upgrade to 5.1 before we can upgrade the master/media servers to 6.x.

We are really looking forward to that problem being fixed.

--stuart

[b]From:[/b] Dominik Pietrzykowski [mailto]
[b]Sent:[/b] Monday, July 23, 2007 3:47 AM
[b]To:[/b] WEAVER, Simon (external); 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
[b]Subject:[/b] RE: [Veritas-bu] Maximum number of policies

Just to add to Stuart&#8217;s comment, NB6 reads policies according to refresh rate and when policies change. These are done by nbpem.
You can also refresh manually, via command or restart of NB (not the best way to do this)

Some handy hints:

- For those who do not know there is a setting for policy refresh on the master, default is 10min I think ? (host properties/master/global attr)

- Manual refresh can be done via : nbpemreq -updatepolicies

- This touch file stops nbpem doing refreshes unless you issue the nbpemreq command : /usr/openv/netbackup/bin/[b]PolicyStrategy[/b][b][/b]
[b] [/b]

[b]From:[/b] WEAVER, Simon (external) [mailto]
[b]Sent:[/b] Monday, 23 July 2007 4:20 PM
[b]To:[/b] 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
[b]Subject:[/b] Re: [Veritas-bu] Maximum number of policies

[i][b][i]1,100 policies!!!!!![/i][/b][/i]

[i]Regards[/i]
[i]Simon Weaver[/i][i]
[/i][b][i]3rd Line Technical Support[/i][/b][b][i]
[b]Windows Domain Administrator[/b][/i][/b]
[i]EADS Astrium Limited, B23AA IM (DCS)[/i]
[i]Anchorage Road[/i][i], Portsmouth, PO3 5PU[/i]
[i]Email: [/i][i]Simon.Weaver < at > Astrium.eads.net[/i] ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 12:51PM
yes just over 1100 policies&#8230;.it&#8217;s not quite 1 client per policy as Curtis Preston suggests.  What we have done is to have a policy for a given dataset.  For example, we have two exchange policies one has 13 exchange servers in it and the other has 10.  The reason we have two is because they are in different datacenters and we have a media server in each datacenter.

Most of our policies actually do have only one client per policy, but because we are creating policies by dataset, we will have some that have more than one client.

--stuart

[b]From:[/b] WEAVER, Simon (external) [mailto]
[b]Sent:[/b] Sunday, July 22, 2007 11:20 PM
[b]To:[/b] 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
[b]Subject:[/b] RE: [Veritas-bu] Maximum number of policies

[i][b][i]1,100 policies!!!!!![/i][/b][/i]

[i]Regards[/i]
[i]Simon Weaver[/i][i]
[/i][b][i]3rd Line Technical Support[/i][/b][b][i]
[b]Windows Domain Administrator[/b][/i][/b]
[i]EADS Astrium Limited, B23AA IM (DCS)[/i]
[i]Anchorage Road[/i][i], Portsmouth, PO3 5PU[/i]
[i]Email: [/i][i]Simon.Weaver < at > Astrium.eads.net[/i] ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 01:39PM
I thought this pic would be appropriate for us ...

[b]From:[/b] veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto] [b]On Behalf Of [/b]Liddle, Stuart
[b]Sent:[/b] Monday, July 23, 2007 2:48 PM
[b]To:[/b] WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
[b]Subject:[/b] Re: [Veritas-bu] Maximum number of policies

yes just over 1100 policies….it’s not quite 1 client per policy as Curtis Preston suggests. What we have done is to have a policy for a given dataset. For example, we have two exchange policies one has 13 exchange servers in it and the other has 10. The reason we have two is because they are in different datacenters and we have a media server in each datacenter.

Most of our policies actually do have only one client per policy, but because we are creating policies by dataset, we will have some that have more than one client.

--stuart

[b]From:[/b] WEAVER, Simon (external) [mailto]
[b]Sent:[/b] Sunday, July 22, 2007 11:20 PM
[b]To:[/b] 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
[b]Subject:[/b] RE: [Veritas-bu] Maximum number of policies

[i][b][i]1,100 policies!!!!!![/i][/b][/i]

[i]Regards[/i]
[i]Simon Weaver[/i][i]
[/i][b][i]3rd Line Technical Support[/i][/b][b][i]
[b]Windows Domain Administrator[/b][/i][/b]
[i]EADS Astrium Limited, B23AA IM (DCS)[/i]
[i]Anchorage Road[/i][i], Portsmouth, PO3 5PU[/i]
[i]Email: [/i][i]Simon.Weaver < at > Astrium.eads.net[/i] ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 01:53PM
Whoever has that many polices has some mental issues.

On Mon, 23 Jul 2007, briandiven < at > northwesternmutual.com wrote:

[quote]I thought this pic would be appropriate for us ...

________________________________

From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto] On Behalf Of Liddle, Stuart
Sent: Monday, July 23, 2007 2:48 PM
To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Maximum number of policies

yes just over 1100 policies....it's not quite 1 client per policy as Curtis Preston suggests. What we have done is to have a policy for a given dataset. For example, we have two exchange policies one has 13 exchange servers in it and the other has 10. The reason we have two is because they are in different datacenters and we have a media server in each datacenter.

Most of our policies actually do have only one client per policy, but because we are creating policies by dataset, we will have some that have more than one client.

--stuart

________________________________

From: WEAVER, Simon (external) [mailto]
Sent: Sunday, July 22, 2007 11:20 PM
To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Maximum number of policies

1,100 policies!!!!!!

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: Simon.Weaver < at > Astrium.eads.net <mailto:Simon.Weaver < at > Astrium.eads.net>

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 02:12PM
Well, it comes down to how you want to keep control of your environment, I
think.
It may be the right thing for certain environments.

Reporting success/failures is very efficient to do per policy, or 'data set'
as Stuart uses.

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 02:45PM
Perhaps, I just hope they never had to change a storage unit for all those
4,000+ polices :)

On Mon, 23 Jul 2007, Meidal, Knut wrote:

[quote]Well, it comes down to how you want to keep control of your environment, I
think.
It may be the right thing for certain environments.

Reporting success/failures is very efficient to do per policy, or 'data set'
as Stuart uses.

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 02:53PM
* Justin Piszcz <jpiszcz < at > lucidpixels.com> [2007-07-23 17]:
[quote]Perhaps, I just hope they never had to change a storage unit for all those
4,000+ polices :)
[/quote]
Nah, that's what the commandline is for :-)

--
David Rock
david < at > graniteweb.com
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Maximum number of policies
July 23, 2007 03:14PM
On Mon, 23 Jul 2007, David Rock wrote:

[quote]* Justin Piszcz <jpiszcz < at > lucidpixels.com> [2007-07-23 17]:
[quote]Perhaps, I just hope they never had to change a storage unit for all those
4,000+ polices :)
[/quote]
Nah, that's what the commandline is for :-)

--
David Rock
david < at > graniteweb.com
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[/quote]
Of course, just don't make a typo for > 4k polices in your cmd line loop
:)
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Maximum number of policies
July 23, 2007 03:20PM
Embrace the command line. It is your friend.

I use it to create and manipulate polices all the time--for no other
reason than the same task undertaken
in the GUI would take forever :)

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 03:53PM
It works incredibly well for us. All management is command line
scripted for failure analysis, reruns, web-based reports, etc. The
biggest benefit for us is that each of our databases has it's own policy
name, so we use this name to pass in parms to a single script ... An
example policy name would be:

UDB-Instance-Database-Online/Offline-DB/Log-Retention-Stripes

A single script will then parse that out and submit say a UDB online
backup for the database with a 30 day retention and since it is large,
maybe run it in 2 stipes.

And yes, you can cmd line script changes, but for the comment about
storage units, if you define a STU group, you can change what's in the
group and leave the STU group the same.

Reporting is extremely specific, and although there is up-front
scripting time, once you automate 100 policies, 200, 1000, or 5,000 just
doesn't matter.

We've been doing this for 4 years now and although called crazy by many,
people that have come in and seen our shop end up sending us a lot of
compliments after they leave. We've also had occasions to make changes,
but we really like the way this runs.

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 03:59PM
Ah....I see.

So, Justin, you have some "special" insight about everyone's backup
environment and business requirements that allows you to come up with a
blanket statement like that?

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 04:01PM
I retract my statement. Some environments could have a good use for that
many polices I suppose..

On Mon, 23 Jul 2007, Liddle, Stuart wrote:

[quote]Ah....I see.

So, Justin, you have some "special" insight about everyone's backup
environment and business requirements that allows you to come up with a
blanket statement like that?

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 04:04PM
For example utilize include/exclude lists on the lists or find _some_ way
to group the clients together, no?

On Mon, 23 Jul 2007, Justin Piszcz wrote:

[quote]I retract my statement. Some environments could have a good use for that
many polices I suppose..

On Mon, 23 Jul 2007, Liddle, Stuart wrote:

[quote]Ah....I see.

So, Justin, you have some "special" insight about everyone's backup
environment and business requirements that allows you to come up with a
blanket statement like that?

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 04:04PM
Bright future in consulting, looks like.
Maybe Curtis is hiring...

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 04:05PM
Have you had any issues with NBU6.0 with that many polices? That does make
a lot of sense for reporting purposes.. I just wonder how stable is it
under 6.0MP4? Any issues?

On Mon, 23 Jul 2007, briandiven < at > northwesternmutual.com wrote:

[quote]It works incredibly well for us. All management is command line
scripted for failure analysis, reruns, web-based reports, etc. The
biggest benefit for us is that each of our databases has it's own policy
name, so we use this name to pass in parms to a single script ... An
example policy name would be:

UDB-Instance-Database-Online/Offline-DB/Log-Retention-Stripes

A single script will then parse that out and submit say a UDB online
backup for the database with a 30 day retention and since it is large,
maybe run it in 2 stipes.

And yes, you can cmd line script changes, but for the comment about
storage units, if you define a STU group, you can change what's in the
group and leave the STU group the same.

Reporting is extremely specific, and although there is up-front
scripting time, once you automate 100 policies, 200, 1000, or 5,000 just
doesn't matter.

We've been doing this for 4 years now and although called crazy by many,
people that have come in and seen our shop end up sending us a lot of
compliments after they leave. We've also had occasions to make changes,
but we really like the way this runs.

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 04:07PM
These are great benefits, what are the downsides of so many polices that
you have found in the four years using that configuration?

On Mon, 23 Jul 2007, briandiven < at > northwesternmutual.com wrote:

[quote]It works incredibly well for us. All management is command line
scripted for failure analysis, reruns, web-based reports, etc. The
biggest benefit for us is that each of our databases has it's own policy
name, so we use this name to pass in parms to a single script ... An
example policy name would be:

UDB-Instance-Database-Online/Offline-DB/Log-Retention-Stripes

A single script will then parse that out and submit say a UDB online
backup for the database with a 30 day retention and since it is large,
maybe run it in 2 stipes.

And yes, you can cmd line script changes, but for the comment about
storage units, if you define a STU group, you can change what's in the
group and leave the STU group the same.

Reporting is extremely specific, and although there is up-front
scripting time, once you automate 100 policies, 200, 1000, or 5,000 just
doesn't matter.

We've been doing this for 4 years now and although called crazy by many,
people that have come in and seen our shop end up sending us a lot of
compliments after they leave. We've also had occasions to make changes,
but we really like the way this runs.

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 04:16PM
Not yet ... We split our prod & test environment in half and are running
the test environment under 6.0 MP4 planning for a production upgrade on
8/11 and back to a single master. We copied all 4,000+ policies over so
that it will have to process them all. NBPEM takes about 20 minutes to
sort it all out when we first start NBU, but after that everything
starts right on the minute. Under 5.1 there was always a 30-40 minute
delay, so if we wanted something to start at 10 PM, we'd schedule it for
9:30 PM.

The other thing that was nice about this many policies is that we have
some servers with a lot of databases on them, and firing them all up at
once would cause timeouts (status 54's) due to too many open
connections. We have a script that runs daily that automatically adds
new policies when a database is created. We also have a stagger script
that will adjust the start time of the database backups so they don't
all fire at once.

________
Attached original message stripped from forum post
Maximum number of policies
July 23, 2007 11:06PM
If you have a policy naming convention (and you'd better for that many policies), configuring things like exclude lists is no more difficult with 700000 than with 7. I'd actually argue that it's the other way around.

I blogged about this a while back, and was surprised at the positive support I got:

http://www.backupcentral.com/content/view/51/47/

For exclude lists, I use a script anyway, as I like to push out a standard from the master, so 10 policies, 10000 policies, whatever. ;)

---
W. Curtis Preston
Backup Blog < at > www.backupcentral.com
VP Data Protection, GlassHouse Technologies

________
Attached original message stripped from forum post
Maximum number of policies
July 24, 2007 01:53AM
For those of you that are seriously interested, here is the actual format taking advantage of policy and schedule names that made our life easier. I should also state that we stood up extremely well to 5 audits over the past 4 years (BCP/vaulting audit, internal audit regarding records retention, backup audit, internal SOX, and external SOX audit).

Policy name example:

Sybase-alderaan-PDS_SY24-model-DB ... Which tells me this is a sybase DB on physical host alderaan on database server PDS_SY24 for the model database instance and that this policy is a DB backup (vs. a log).

Our audit requirements are for 30 and 90 day retentions and we send all databases less than 25 GB to a D2D pool. To accomplish this, we use the schedule name.

Schedule name example (There are 2 automatic backup schedules and 4 application backup schedules per policy):

Automatic Backup Name: PDS_SY24+model+30day+DB+tape+1 and PDS_SY24+model+90day+DB+tape+1 ... Which tells me database/instance, the retention, that it's a DB backup, destined for tape with 1 stripe.

The key here is that we have a single script to maintain for the whole environment, because it has all of the information to parse. The DB team is required to keep a table of all databases and whether they are active or not and how big they are. We activate/deactive/create policies based on their table and the script determines whether they should go to disk or tape based on the size.

Application Backup Name: There are 4 of them, 30day-tape, 30day-disk, 90day-tape, and 90day-disk.

I would also add that rerunning failed backups is one thing, but what about a backup that never runs? It doesn't show up on a failed rerun script. Part of the summary reports show databases that haven't had a backup in "X" number of days so we catch those too. Now the onus of the audit is on the database teams to keep their table current and it is a very well documented, specific, and verifiable process. I wrote my own SLA's at a 95% backup success rate and 100% restore success rate and haven't missed them for 2 years now.

________
Attached original message stripped from forum post
Maximum number of policies
July 24, 2007 01:58AM
On Tue, 24 Jul 2007, briandiven < at > northwesternmutual.com wrote:

[quote]For those of you that are seriously interested, here is the actual format taking advantage of policy and schedule names that made our life easier. I should also state that we stood up extremely well to 5 audits over the past 4 years (BCP/vaulting audit, internal audit regarding records retention, backup audit, internal SOX, and external SOX audit).

Policy name example:

Sybase-alderaan-PDS_SY24-model-DB ... Which tells me this is a sybase DB on physical host alderaan on database server PDS_SY24 for the model database instance and that this policy is a DB backup (vs. a log).

Our audit requirements are for 30 and 90 day retentions and we send all databases less than 25 GB to a D2D pool. To accomplish this, we use the schedule name.

Schedule name example (There are 2 automatic backup schedules and 4 application backup schedules per policy):

Automatic Backup Name: PDS_SY24+model+30day+DB+tape+1 and PDS_SY24+model+90day+DB+tape+1 ... Which tells me database/instance, the retention, that it's a DB backup, destined for tape with 1 stripe.

The key here is that we have a single script to maintain for the whole environment, because it has all of the information to parse. The DB team is required to keep a table of all databases and whether they are active or not and how big they are. We activate/deactive/create policies based on their table and the script determines whether they should go to disk or tape based on the size.

Application Backup Name: There are 4 of them, 30day-tape, 30day-disk, 90day-tape, and 90day-disk.

I would also add that rerunning failed backups is one thing, but what about a backup that never runs? It doesn't show up on a failed rerun script. Part of the summary reports show databases that haven't had a backup in "X" number of days so we catch those too. Now the onus of the audit is on the database teams to keep their table current and it is a very well documented, specific, and verifiable process. I wrote my own SLA's at a 95% backup success rate and 100% restore success rate and haven't missed them for 2 years now.
[/quote]
How often do you perform restores? What types of tape medium do you
use? What robots are in use?

I find 100% restoration rate very nice; however, how do you achieve
that, I assume you have two copies of most pieces of data as mentioned
above 30/90 days?

Justin.

_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Maximum number of policies
July 24, 2007 03:30AM
We get around 6-8 restore requests/day. And yes, I take advantage of
Inline Tape Copy and have a copy available across dark fiber at a
separate campus and the other copy vaulted 90 miles away. If we have
time, I rerun (or dupe) any status 84's we get. I'm using IBM for tape
- 3590's and 3592's in a 3494 ATL, but just brought in a TS3500 which is
supported behind a VTL. The 3592's are reliable beyond any tape drive I
have seen in my life - however the 3590's are about on par with any
other technology.

________
Attached original message stripped from forum post
Maximum number of policies
July 24, 2007 03:40AM
On Tue, 24 Jul 2007, briandiven < at > northwesternmutual.com wrote:

[quote]We get around 6-8 restore requests/day. And yes, I take advantage of
Inline Tape Copy and have a copy available across dark fiber at a
separate campus and the other copy vaulted 90 miles away. If we have
time, I rerun (or dupe) any status 84's we get. I'm using IBM for tape
- 3590's and 3592's in a 3494 ATL, but just brought in a TS3500 which is
supported behind a VTL. The 3592's are reliable beyond any tape drive I
have seen in my life - however the 3590's are about on par with any
other technology.
[/quote]
Have you used other vendor tape drives such as HP or StorageTek? I have
been hearing a lot of good things regarding IBM LTO tape drives. I do
have another question for you as well. What are your cleaning cycles
set to? How often do you clean your tape drives? What types of
cleaning tapes do you use? Do you (or anyone else on this list) who
uses L700s ever have cleaning tapes get 'stuck' in the tape drives when
you have NetBackup either schedule a cleaning or clean the drivee
manually?

Furthermore, how long do you use your tapes for? Do you base this
estimate on total number of mounts? When you write to your tapes, do
you fill them up from beginning to end or mount them multiple times?

You seem to have a pretty rock solid environment, I assume you're
running NetBackup 6.0MP4 currently? Have you run into any other weird
bugs with that (and all of the policies) vs. 5.1MP4 besides the ones you
mentioned yesterday?

Justin.

_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Sorry, only registered users may post in this forum.

Click here to login