Backup Central

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

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 ?



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 ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post

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’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


From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of WEAVER, Simon (external)
Sent: Friday, July 20, 2007 6:42 AM
To: 'Edson Noboru Yamada'; Veritas-bu < at > mailman.eng.auburn.edu
Subject: 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 ?





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

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

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, Paul Keating <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'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

I’ve got customers with THOUSANDs of policies with no major ill effects.  In 6.0 I’d say there are no effects at all.  In pre-6.0, I’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’ve got non worries.

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


From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of Edson Noboru Yamada
Sent: Friday, July 20, 2007 11:05 AM
Cc: Veritas-bu < at > mailman.eng.auburn.edu
Subject: 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, Paul Keating <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

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 ([email]Simon.Weaver < at > Astrium.eads.net[/email]) [quote]
________
Attached original message stripped from forum post

Just to add to Stuart’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/PolicyStrategy





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


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





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

Yeah….we realize that NB 6.x is a total re-write of the scheduler…we can’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


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



Just to add to Stuart’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/PolicyStrategy





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


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





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

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:simon.weaver < at > astrium.eads.net]
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


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





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

I thought this pic would be appropriate for us ...



From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] 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:simon.weaver < at > astrium.eads.net]
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


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





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

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:veritas-bu-bounces < at > mailman.eng.auburn.edu] 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:simon.weaver < at > astrium.eads.net]
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

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

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

* Justin Piszcz <jpiszcz < at > lucidpixels.com> [2007-07-23 17:43]:
Perhaps, I just hope they never had to change a storage unit for all those
4,000+ polices

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