Re: [Veritas-bu] Maximum number of policies
I'd be interested in this too. On Thu, 26 Jul 2007, Jon Bousselot wrote: Are the maximum numbers for everything else in NetBackup published somewhere? I'm curious. Even with less than 100 policies, the command line is sometimes the fastest way to get things done. * Justin Piszcz [EMAIL PROTECTED] [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 [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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 70 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, 1 policies, whatever. ;) --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 4:03 PM To: Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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: 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: AhI 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? -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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
Re: [Veritas-bu] Maximum number of policies
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. -Original Message- From: Curtis Preston [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 1:01 AM To: Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; DIVEN, BRIAN; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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 70 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, 1 policies, whatever. ;) --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 4:03 PM To: Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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: 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: AhI 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? -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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
Re: [Veritas-bu] Maximum number of policies
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. -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 3:56 AM To: DIVEN, BRIAN Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies On Tue, 24 Jul 2007, [EMAIL PROTECTED] wrote: 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. 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. This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
On Tue, 24 Jul 2007, [EMAIL PROTECTED] wrote: 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. 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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
I have experience with StorageTek, but never used HP. For the IBM library, you turn off NBU cleaning mgmt and let the library handle it. I'm not sure of their current alogrhytm - it used to be the number of feet of tape that passed the heads or if the drive reports errors. When a cleaning tape is ejected, you just throw a fresh one in. I've had stuck tapes, but don't recall a cleaning cartridge getting stuck. I don't have experience with LTO, but I know it is competitive with capacity performance, but I haven't heard much about reliability. The 3592 cartridges are guaranteed for 10 years so they get replaced when they fail and get frozen in NBU. The onsite tapes are appended to whereas the vaulted tapes are rewritten from the beginning when they expire and return. We beat up the 3592's pretty good ... They are 40 MB/Sec drives with 900 GB cartridges and we drive 6 of them steady for 4 days 24 hours/day for our NDMP backups alone. We've had 3 service calls in 2 years on these drives - but they are pricey. The 3590's are another story all together - we probably have a service call every 2-3 weeks on those drives. We have 26 3590's and 28 3592's. I'll let you know about 6.0 after I fully burn it in ... I'm still having fun trying to break it. -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 5:39 AM To: DIVEN, BRIAN Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies On Tue, 24 Jul 2007, [EMAIL PROTECTED] wrote: 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. 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. This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
We have 8 Clariion VTL's and have a retention period of a week for everything. We use In Line Tape copy for weekly and monthly backups for offside storage. We are looking to use SRDF to replicate these VTL's, but this may just take too long. Brian, what replication software are you using to send your data via dark fibre? Ethernet? Regards, Clem Kruger 'Plan, Plan, Plan - Train hard, expect the worst and you'll be surprised at how you grow and what one's team can achieve.' Telkom SA Ltd ITS Infrastructure Storage Management -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 24 July 2007 12:26 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: Re: [Veritas-bu] Maximum number of policies 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. -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 3:56 AM To: DIVEN, BRIAN Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies On Tue, 24 Jul 2007, [EMAIL PROTECTED] wrote: 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. 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. This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
We have fiber DWDM in place, so the drives appear as if they are locally attached fiber drives. I'm in the process of doing some BCP work which has different RPO/RTO than most things, so we are currently looking at options for replication. We are already replicating the mainframe environment, and will probably do the same in Open Systems since there haven't been any issues with that. From: Clem Kruger (C) [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 5:48 AM To: DIVEN, BRIAN; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: RE: [Veritas-bu] Maximum number of policies We have 8 Clariion VTL's and have a retention period of a week for everything. We use In Line Tape copy for weekly and monthly backups for offside storage. We are looking to use SRDF to replicate these VTL's, but this may just take too long. Brian, what replication software are you using to send your data via dark fibre? Ethernet? Regards, Clem Kruger 'Plan, Plan, Plan - Train hard, expect the worst and you'll be surprised at how you grow and what one's team can achieve.' Telkom SA Ltd ITS Infrastructure Storage Management -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 24 July 2007 12:26 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: Re: [Veritas-bu] Maximum number of policies 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. -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 3:56 AM To: DIVEN, BRIAN Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies On Tue, 24 Jul 2007, [EMAIL PROTECTED] wrote: 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. 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. This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail
Re: [Veritas-bu] Maximum number of policies
Having worked with Brian and crew a few years back, when it was just 3000 policies, I must say it worked great then. It was just as easy to manageas the 50 or so policies I inherited where I am working now, perhaps even easier because all the policies I have now were created with no plan in mind. Chuck Tipton [EMAIL PROTECTED] 7/23/2007 6:51 PM It works incredibly well for us. All management is command linescripted for failure analysis, reruns, web-based reports, etc. Thebiggest benefit for us is that each of our databases has it's own policyname, so we use this name to pass in parms to a single script ... Anexample policy name would be:UDB-Instance-Database-Online/Offline-DB/Log-Retention-StripesA single script will then parse that out and submit say a UDB onlinebackup 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 aboutstorage units, if you define a STU group, you can change what's in thegroup and leave the STU group the same.Reporting is extremely specific, and although there is up-frontscripting time, once you automate 100 policies, 200, 1000, or 5,000 justdoesn'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 ofcompliments after they leave. We've also had occasions to make changes,but we really like the way this runs. -Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED] On Behalf Of IanClementsSent: Monday, July 23, 2007 5:18 PMTo: Justin Piszcz; David RockCc: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Maximum number of policiesEmbrace the command line. It is your friend. I use it to create and manipulate polices all the time--for no otherreason than the same task undertaken in the GUI would take forever :)-Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED] On Behalf Of JustinPiszczSent: Monday, July 23, 2007 3:13 PMTo: David RockCc: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Maximum number of policiesOf course, just don't make a typo for 4k polices in your cmd line loop:)___Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu-- IMPORTANT NOTICE: The contents of this email and any attachments areconfidential and may also be privileged. If you are not the intendedrecipient, please notify the sender immediately and do not disclose thecontents to any other person, use it for any purpose, or store or copythe information in any medium. Thank you.___Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-buThis e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation.___Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
Takes a couple seconds with a little ad hoc command line scripting. At a previous job, we had 3000+ policies. One client per.Sometimes several policies per client. The scheduler realy didn't like it (this was in the 3.4 days), so we had a custom scripted scheduler that was called from cron. We also had a homebrewed laptop scheduler that backed up the 1000+ laptops per day. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: July 23, 2007 5:43 PM To: Meidal, Knut Cc: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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: 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. La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
Yeswe have a policy naming convention: SiteCode-BusinessUnit-ServiceTier-Dataset-Component For example, we might have a policy called: usto-core-std-exchange-app Which is a backup policy for the Exchange servers. It's a Standard tier backup, meaning it get's daily backups retained for 1 week (on site) and weekly backups retained for 30 days (sent off-site). Another policy: usto-dev-val-gnltst-db is a backup of the gnltst database that is done as a Value tier backup which is done weekly and retained for 6 weeks (off-site). (All database backups are done from snapshots. We don't use bpstart/bpend scripts to do the cold backupsthe DBA's have scripts to shut down and snapshot the databases.) The premium tier backups are daily fulls and all copies are sent off-site. -Original Message- From: Curtis Preston [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 11:01 PM To: Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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 70 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, 1 policies, whatever. ;) --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 4:03 PM To: Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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: 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: AhI 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? -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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
Re: [Veritas-bu] Maximum number of policies
In 5.0/5.1 MP5 there is a bug The major issue we saw with one policy for one client specially Windows FS that When a stream/drive backup fails for a Win client, it tend to pickup all the multi streams drives irrespective few were done successfully earlier Which tends to backup duplicate data and also consume extra SLA time To work around for this issue, we fixed policy per /drive letter, having all similar clients in it -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Tuesday, July 24, 2007 4:38 PM To: Curtis Preston; Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Yeswe have a policy naming convention: SiteCode-BusinessUnit-ServiceTier-Dataset-Component For example, we might have a policy called: usto-core-std-exchange-app Which is a backup policy for the Exchange servers. It's a Standard tier backup, meaning it get's daily backups retained for 1 week (on site) and weekly backups retained for 30 days (sent off-site). Another policy: usto-dev-val-gnltst-db is a backup of the gnltst database that is done as a Value tier backup which is done weekly and retained for 6 weeks (off-site). (All database backups are done from snapshots. We don't use bpstart/bpend scripts to do the cold backupsthe DBA's have scripts to shut down and snapshot the databases.) The premium tier backups are daily fulls and all copies are sent off-site. -Original Message- From: Curtis Preston [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 11:01 PM To: Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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 70 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, 1 policies, whatever. ;) --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 4:03 PM To: Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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: 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: AhI 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? -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 1,100 policies!! Regards Simon Weaver 3rd Line
Re: [Veritas-bu] Maximum number of policies
Wow, you've gone the opposite way (one policy per drive). Ouch! I've had the scenario you describe work just fine with multistreaming --without doing what you're doing. For example, if A, B, C, D were supposed to do a full, and then one of them failed, it would only re-run the one that failed. If it failed completely that night, and so needed to run a full the next day, it would only run a full on the filesystem that failed. I can see if you manually run the full via the GUI, it would run the entire thing. But if you want to re-run just one failed backup of one drive, just do that via the activity monitor. (Right click on which one failed and re-run it.) I believe that's been available since 5.1, maybe 5.0. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kohli, Vidit Sent: Tuesday, July 24, 2007 1:52 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies In 5.0/5.1 MP5 there is a bug The major issue we saw with one policy for one client specially Windows FS that When a stream/drive backup fails for a Win client, it tend to pickup all the multi streams drives irrespective few were done successfully earlier Which tends to backup duplicate data and also consume extra SLA time To work around for this issue, we fixed policy per /drive letter, having all similar clients in it -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Tuesday, July 24, 2007 4:38 PM To: Curtis Preston; Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Yeswe have a policy naming convention: SiteCode-BusinessUnit-ServiceTier-Dataset-Component For example, we might have a policy called: usto-core-std-exchange-app Which is a backup policy for the Exchange servers. It's a Standard tier backup, meaning it get's daily backups retained for 1 week (on site) and weekly backups retained for 30 days (sent off-site). Another policy: usto-dev-val-gnltst-db is a backup of the gnltst database that is done as a Value tier backup which is done weekly and retained for 6 weeks (off-site). (All database backups are done from snapshots. We don't use bpstart/bpend scripts to do the cold backupsthe DBA's have scripts to shut down and snapshot the databases.) The premium tier backups are daily fulls and all copies are sent off-site. -Original Message- From: Curtis Preston [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 11:01 PM To: Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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 70 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, 1 policies, whatever. ;) --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 4:03 PM To: Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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: 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: AhI 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? -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER
Re: [Veritas-bu] Maximum number of policies
That's true, but it won't work if it's outside of the backup window ... It will then fail with a status 196. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston Sent: Tuesday, July 24, 2007 4:54 PM To: Kohli, Vidit; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Wow, you've gone the opposite way (one policy per drive). Ouch! I've had the scenario you describe work just fine with multistreaming --without doing what you're doing. For example, if A, B, C, D were supposed to do a full, and then one of them failed, it would only re-run the one that failed. If it failed completely that night, and so needed to run a full the next day, it would only run a full on the filesystem that failed. I can see if you manually run the full via the GUI, it would run the entire thing. But if you want to re-run just one failed backup of one drive, just do that via the activity monitor. (Right click on which one failed and re-run it.) I believe that's been available since 5.1, maybe 5.0. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kohli, Vidit Sent: Tuesday, July 24, 2007 1:52 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies In 5.0/5.1 MP5 there is a bug The major issue we saw with one policy for one client specially Windows FS that When a stream/drive backup fails for a Win client, it tend to pickup all the multi streams drives irrespective few were done successfully earlier Which tends to backup duplicate data and also consume extra SLA time To work around for this issue, we fixed policy per /drive letter, having all similar clients in it -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Tuesday, July 24, 2007 4:38 PM To: Curtis Preston; Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Yeswe have a policy naming convention: SiteCode-BusinessUnit-ServiceTier-Dataset-Component For example, we might have a policy called: usto-core-std-exchange-app Which is a backup policy for the Exchange servers. It's a Standard tier backup, meaning it get's daily backups retained for 1 week (on site) and weekly backups retained for 30 days (sent off-site). Another policy: usto-dev-val-gnltst-db is a backup of the gnltst database that is done as a Value tier backup which is done weekly and retained for 6 weeks (off-site). (All database backups are done from snapshots. We don't use bpstart/bpend scripts to do the cold backupsthe DBA's have scripts to shut down and snapshot the databases.) The premium tier backups are daily fulls and all copies are sent off-site. -Original Message- From: Curtis Preston [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 11:01 PM To: Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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 70 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, 1 policies, whatever. ;) --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 4:03 PM To: Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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: 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: AhI 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? -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu
Re: [Veritas-bu] Maximum number of policies
You're saying if you manually re-run a backup via the activity monitor during the daytime, it will fail with a 196? I didn't realize that. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 3:16 PM To: Curtis Preston; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies That's true, but it won't work if it's outside of the backup window ... It will then fail with a status 196. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston Sent: Tuesday, July 24, 2007 4:54 PM To: Kohli, Vidit; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Wow, you've gone the opposite way (one policy per drive). Ouch! I've had the scenario you describe work just fine with multistreaming --without doing what you're doing. For example, if A, B, C, D were supposed to do a full, and then one of them failed, it would only re-run the one that failed. If it failed completely that night, and so needed to run a full the next day, it would only run a full on the filesystem that failed. I can see if you manually run the full via the GUI, it would run the entire thing. But if you want to re-run just one failed backup of one drive, just do that via the activity monitor. (Right click on which one failed and re-run it.) I believe that's been available since 5.1, maybe 5.0. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kohli, Vidit Sent: Tuesday, July 24, 2007 1:52 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies In 5.0/5.1 MP5 there is a bug The major issue we saw with one policy for one client specially Windows FS that When a stream/drive backup fails for a Win client, it tend to pickup all the multi streams drives irrespective few were done successfully earlier Which tends to backup duplicate data and also consume extra SLA time To work around for this issue, we fixed policy per /drive letter, having all similar clients in it -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Tuesday, July 24, 2007 4:38 PM To: Curtis Preston; Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Yeswe have a policy naming convention: SiteCode-BusinessUnit-ServiceTier-Dataset-Component For example, we might have a policy called: usto-core-std-exchange-app Which is a backup policy for the Exchange servers. It's a Standard tier backup, meaning it get's daily backups retained for 1 week (on site) and weekly backups retained for 30 days (sent off-site). Another policy: usto-dev-val-gnltst-db is a backup of the gnltst database that is done as a Value tier backup which is done weekly and retained for 6 weeks (off-site). (All database backups are done from snapshots. We don't use bpstart/bpend scripts to do the cold backupsthe DBA's have scripts to shut down and snapshot the databases.) The premium tier backups are daily fulls and all copies are sent off-site. -Original Message- From: Curtis Preston [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 11:01 PM To: Justin Piszcz; Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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 70 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, 1 policies, whatever. ;) --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 4:03 PM To: Liddle, Stuart Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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: I retract my statement. Some environments could have a good use for that many polices I suppose.. On Mon, 23 Jul
Re: [Veritas-bu] Maximum number of policies
* Curtis Preston [EMAIL PROTECTED] [2007-07-24 18:21]: You're saying if you manually re-run a backup via the activity monitor during the daytime, it will fail with a 196? I didn't realize that. That would make sense because re-running is functionally similar to rescheduling a job, which takes the windows into account. You _can_ manually submit a job from the policy listing and that would run without the 196 (unless something else caused it to fail and retry), but that would be the entire policy, not just the specific drive stream. -- David Rock [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
I learned something today! --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Rock Sent: Tuesday, July 24, 2007 3:44 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies * Curtis Preston [EMAIL PROTECTED] [2007-07-24 18:21]: You're saying if you manually re-run a backup via the activity monitor during the daytime, it will fail with a 196? I didn't realize that. That would make sense because re-running is functionally similar to rescheduling a job, which takes the windows into account. You _can_ manually submit a job from the policy listing and that would run without the 196 (unless something else caused it to fail and retry), but that would be the entire policy, not just the specific drive stream. -- David Rock [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
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: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
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:[EMAIL PROTECTED] Sent: Monday, 23 July 2007 4:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted
Re: [Veritas-bu] Maximum number of policies
Yeahwe 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:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 3:47 AM To: WEAVER, Simon (external); 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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:[EMAIL PROTECTED] Sent: Monday, 23 July 2007 4:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259
Re: [Veritas-bu] Maximum number of policies
yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified
Re: [Veritas-bu] Maximum number of policies
I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any
Re: [Veritas-bu] Maximum number of policies
Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete
Re: [Veritas-bu] Maximum number of policies
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. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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
Re: [Veritas-bu] Maximum number of policies
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: 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. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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
Re: [Veritas-bu] Maximum number of policies
* Justin Piszcz [EMAIL PROTECTED] [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 [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
On Mon, 23 Jul 2007, David Rock wrote: * Justin Piszcz [EMAIL PROTECTED] [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 [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Of course, just don't make a typo for 4k polices in your cmd line loop :) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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 :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 3:13 PM To: David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Of course, just don't make a typo for 4k polices in your cmd line loop :) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Clements Sent: Monday, July 23, 2007 5:18 PM To: Justin Piszcz; David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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 :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 3:13 PM To: David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Of course, just don't make a typo for 4k polices in your cmd line loop :) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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: AhI 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? -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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
Re: [Veritas-bu] Maximum number of policies
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, [EMAIL PROTECTED] wrote: 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. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Clements Sent: Monday, July 23, 2007 5:18 PM To: Justin Piszcz; David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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 :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 3:13 PM To: David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Of course, just don't make a typo for 4k polices in your cmd line loop :) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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: 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: AhI 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? -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 1:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Whoever has that many polices has some mental issues. On Mon, 23 Jul 2007, [EMAIL PROTECTED] wrote: I thought this pic would be appropriate for us ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, Stuart Sent: Monday, July 23, 2007 2:48 PM To: WEAVER, Simon (external); Liddle, Stuart; 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies yes just over 1100 policiesit'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:[EMAIL PROTECTED] Sent: Sunday, July 22, 2007 11:20 PM To: 'Liddle, Stuart'; 'Edson Noboru Yamada'; Veritas-bu@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: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 2:59 PM To: WEAVER, Simon (external); 'Edson Noboru Yamada'; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies Hi I have an NBU 5.1 installation with one master server (Solaris 9) and 6 media servers (RHEL4, Windows 2003). I´ve just
Re: [Veritas-bu] Maximum number of policies
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, [EMAIL PROTECTED] wrote: 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. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Clements Sent: Monday, July 23, 2007 5:18 PM To: Justin Piszcz; David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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 :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 3:13 PM To: David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Of course, just don't make a typo for 4k polices in your cmd line loop :) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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. -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 6:04 PM To: DIVEN, BRIAN Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Maximum number of policies 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, [EMAIL PROTECTED] wrote: 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. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Clements Sent: Monday, July 23, 2007 5:18 PM To: Justin Piszcz; David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies 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 :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, July 23, 2007 3:13 PM To: David Rock Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Maximum number of policies Of course, just don't make a typo for 4k polices in your cmd line loop :) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments
[Veritas-bu] Maximum number of policies
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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Friday, July 20, 2007 6:42 AM To: 'Edson Noboru Yamada'; Veritas-bu@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 Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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 -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: July 20, 2007 6:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
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 [EMAIL PROTECTED] 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 -- -Original Message- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Edson Noboru Yamada *Sent:* July 20, 2007 6:43 AM *To:* Veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Maximum number of policies 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 La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Maximum number of policies
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 @ www.backupcentral.com VP Data Protection, GlassHouse Technologies From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: Friday, July 20, 2007 11:05 AM Cc: Veritas-bu@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 [EMAIL PROTECTED] 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 -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edson Noboru Yamada Sent: July 20, 2007 6:43 AM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Maximum number of policies 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 La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
