Re: [Veritas-bu] Backing up multiple Oracle db's from a single host
> Is there a venue for requesting enhancements for NBU? Yes. Talk to your account manager. NetBackup Product Managers (PMs) are building (as on going process) a list of enhancements requests from customers, engineers (NetBackup developers), support - essentially various sources.Enhacement requests from this list feed into future releases of NetBackup. From: Jared Still To: VERITAS-BU@mailman.eng.auburn.edu Sent: Tuesday, May 5, 2009 1:34:55 PM Subject: Re: [Veritas-bu] Backing up multiple Oracle db's from a single host On Thu, Apr 30, 2009 at 2:23 PM, nellis wrote: I'd like to ask everyone; what works best for those of you backing up multiple Oracle db's from a single host. I have several Oracle 10g servers I backup. Each has anywhere from 1 to 20 db instances. I use a single policy and a common path & script name to backup the Oracle servers. This for me keeps the number of policies I have to manage down to a minimum. This highlights a long standing shortcoming of NBU - the inability to manually backup only one of the backup selection in policy directly from the admin console. Is there a venue for requesting enhancements for NBU? Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up multiple Oracle db's from a single host
On Thu, Apr 30, 2009 at 2:23 PM, nellis wrote: > > I'd like to ask everyone; what works best for those of you backing up > multiple Oracle db's from a single host. I have several Oracle 10g servers I > backup. Each has anywhere from 1 to 20 db instances. I use a single policy > and a common path & script name to backup the Oracle servers. This for me > keeps the number of policies I have to manage down to a minimum. > This highlights a long standing shortcoming of NBU - the inability to manually backup only one of the backup selection in policy directly from the admin console. Is there a venue for requesting enhancements for NBU? Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up multiple Oracle db's from a single host
One NBU policy per DB works best for us. You don't necessarily have to have multiple scripts, as long as your script "knows" what DB to backup and what policy/schedule to use. Having separate policies makes scheduling changes and reruns easier. It allows us to see exactly which DB is being backed up in the Admin Console. It also allows us to limit and adjust schedules to minimally affect performance (the "nnn" DBs on a client don't all start their backups at once). Cheers, Wayne nellis wrote, in part, on 2009-04-30 5:23 PM: > Hello everyone, first I'll go ahead and apologize for such a long post. > > I'd like to ask everyone; what works best for those of you backing up > multiple Oracle db's from a single host. I have several Oracle 10g servers I > backup. Each has anywhere from 1 to 20 db instances. I use a single policy > and a common path & script name to backup the Oracle servers. This for me > keeps the number of policies I have to manage down to a minimum. > > Our dba's have asked for one policy to be setup per DB. The reasoning behind > this is that they want the flexibility to restart a failed backup without the > restart initiating a backup of all DB's on servers. I told them that what > they should be doing on failed DB backups is from the "activity monitor", > right click on the failed Job ID and select restart. > > Here is where my lack of "in depth knowledge" of how NBU works with the > Oracle RMAN API when a single stream fails. > > They asked, how does NBU know to just restart the backup for the DB that > failed? The best "high level" reply I could come up with was that NBU tracks > which DB piece it's backing up in a log and when a restart is initiated, it's > able to request a backup of just the DB which that piece was associated with > via calls to the Oracle RMAN API. > > In other words, restarting a single failed Jod ID from "activity monitor" for > a backup stream associated with an Oracle backup does not mean that NBU looks > at the policy and executes the backup script specified in the backup > selection for all servers or just one server which is a member of that policy. > > Am I wrong? > How does a restart work with Oracle? > How do you backup Oracle servers which host multiple instances? > What are the advantages and disadvantages if any with one policy per instance? > > Having a policy for each to me sounds like a nightmare in more than one way > but I'd REALLY appreciate anyone's input here. > > Thanks in advance to everyone that replies! > > +-- > |This was sent by norman_el...@discovery.com via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +-- > > > ___ > 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] Backing up multiple Oracle db's from a single host
I went ahead and opened a case with Symantec. What they said was that restarting the Job ID from activity monitor "WOULD" restart the parent Job ID and in turn would rerun the backup for all clients which are a member of the policy as well as all scripts listed in the backup selection. They suggested, as was posted here, to create one script per db. When a backup of a single instance fails, someone from our NOC or a DBA would need to manually run the script associated with the DB that failed from the client side. It would be great if initiating a manual backup of a policy configured for a type other than Windows NT or Standard would present the option to choose an object from the backup selection field but that simply does not exist today. They also said that while the request for a policy for each DB could be done technically, it not always optimal. It really depends on many variables of course for each environment. So what works for one company may not be optimal for ours. They suggested that for our environment, because we have Oracle servers hosting upwards of 20 instances on a single host not to create a single policy for each db / script. If we did, it would most likely become an issue with scheduling. Schedules would over lap due to the window size and time required to backup each DB. That would then create an issue performance as each policy would spawn its own set of bp processes. So given the variables for our environment, the best practice is to run manual backups from the client side using the unique DB scripts the DBAs create. Again, thanks to all that replied! +-- |This was sent by norman_el...@discovery.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up multiple Oracle db's from a single host
I don't have anywhere near as many DB's as you but we do backup multiple DB's on a single host. I don't think that restarting a failed job from inside the GUI just restarts a backup on the failed DB. I think that will restart a backup of all the DB's covered by the policy. When we want granularity with regard to DB backups on the same server we have to break them into individual policies which use an RMAN script on the backend to actually run the backup. I tend to just copy the existing "catch all" policy to a new one and rename a new copy of the RMAN script which it calls to reflect the dayabase it's backing up. For example Solaris_OraTier2 with /usr/openv/netbackup/bin/rman_backup.sh was the setup for the catchall policy. Now I have Solaris_OraTier2_tst11510 calling usr/openv/netbackup/bin/rman_backup_tst11510.sh to backup a specific DB on that host. You'll also need separate /usr/openv/netbackup/bin/rman_oratab files for each backup of a specific DB. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Patrick Sent: Friday, May 01, 2009 4:04 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Backing up multiple Oracle db's from a single host I don't know the answer to your question, but I do have a suggestion. Why not have one script for each DB on the client in addition to the one your using now, and if a DB backup fails run that script from the client? This will keep your policy number down but allow the DBA to re-run individual backups if needed. Just a thought. Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of nellis Sent: 30 April 2009 22:23 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Backing up multiple Oracle db's from a single host Hello everyone, first I'll go ahead and apologize for such a long post. I'd like to ask everyone; what works best for those of you backing up multiple Oracle db's from a single host. I have several Oracle 10g servers I backup. Each has anywhere from 1 to 20 db instances. I use a single policy and a common path & script name to backup the Oracle servers. This for me keeps the number of policies I have to manage down to a minimum. Our dba's have asked for one policy to be setup per DB. The reasoning behind this is that they want the flexibility to restart a failed backup without the restart initiating a backup of all DB's on servers. I told them that what they should be doing on failed DB backups is from the "activity monitor", right click on the failed Job ID and select restart. Here is where my lack of "in depth knowledge" of how NBU works with the Oracle RMAN API when a single stream fails. They asked, how does NBU know to just restart the backup for the DB that failed? The best "high level" reply I could come up with was that NBU tracks which DB piece it's backing up in a log and when a restart is initiated, it's able to request a backup of just the DB which that piece was associated with via calls to the Oracle RMAN API. In other words, restarting a single failed Jod ID from "activity monitor" for a backup stream associated with an Oracle backup does not mean that NBU looks at the policy and executes the backup script specified in the backup selection for all servers or just one server which is a member of that policy. Am I wrong? How does a restart work with Oracle? How do you backup Oracle servers which host multiple instances? What are the advantages and disadvantages if any with one policy per instance? Having a policy for each to me sounds like a nightmare in more than one way but I'd REALLY appreciate anyone's input here. Thanks in advance to everyone that replies! +-- |This was sent by norman_el...@discovery.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] Backing up multiple Oracle db's from a single host
We use RMAN and the Netbackup agent to backup our Oracle instances, one
RMAN job per instance.
In our enviornment the DBA's schedule their jobs using cron or Maestro.
They start a script that runs the
backups. They may run multlple scripts on one host.
The backups are not scheduled by Netbackup. If the backup fails they
re-run their script.. Most of the
RMAN backup failures are a 6 error code, Netbackup does not know what
caused the error, the DBA looks at
the RMAN script log to find the problem, and re-runs the job if needed.
I am not sure what happens if there is a media write error, or a media
mount error. We don't get them very often.
Hope this helps.
--
Carl Stehman
Distributed Services
Pepcoholdings, Inc.
701 Ninth St NW
Washington DC 20068
202-331-6619
nellis
Sent by: veritas-bu-boun...@mailman.eng.auburn.edu
04/30/2009 08:36 PM
Please respond to
VERITAS-BU@mailman.eng.auburn.edu
To
VERITAS-BU@mailman.eng.auburn.edu
cc
Subject
[Veritas-bu] Backing up multiple Oracle db's from a single host
Hello everyone, first I'll go ahead and apologize for such a long post.
I'd like to ask everyone; what works best for those of you backing up
multiple Oracle db's from a single host. I have several Oracle 10g servers
I backup. Each has anywhere from 1 to 20 db instances. I use a single
policy and a common path & script name to backup the Oracle servers. This
for me keeps the number of policies I have to manage down to a minimum.
Our dba's have asked for one policy to be setup per DB. The reasoning
behind this is that they want the flexibility to restart a failed backup
without the restart initiating a backup of all DB's on servers. I told
them that what they should be doing on failed DB backups is from the
"activity monitor", right click on the failed Job ID and select restart.
Here is where my lack of "in depth knowledge" of how NBU works with the
Oracle RMAN API when a single stream fails.
They asked, how does NBU know to just restart the backup for the DB that
failed? The best "high level" reply I could come up with was that NBU
tracks which DB piece it's backing up in a log and when a restart is
initiated, it's able to request a backup of just the DB which that piece
was associated with via calls to the Oracle RMAN API.
In other words, restarting a single failed Jod ID from "activity monitor"
for a backup stream associated with an Oracle backup does not mean that
NBU looks at the policy and executes the backup script specified in the
backup selection for all servers or just one server which is a member of
that policy.
Am I wrong?
How does a restart work with Oracle?
How do you backup Oracle servers which host multiple instances?
What are the advantages and disadvantages if any with one policy per
instance?
Having a policy for each to me sounds like a nightmare in more than one
way but I'd REALLY appreciate anyone's input here.
Thanks in advance to everyone that replies!
+--
|This was sent by norman_el...@discovery.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
intended solely for the use of the person(s) to which it is addressed. If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies. PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication. PHI will not accept any liability in respect of such
communications.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up multiple Oracle db's from a single host
I don't know the answer to your question, but I do have a suggestion. Why not have one script for each DB on the client in addition to the one your using now, and if a DB backup fails run that script from the client? This will keep your policy number down but allow the DBA to re-run individual backups if needed. Just a thought. Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of nellis Sent: 30 April 2009 22:23 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Backing up multiple Oracle db's from a single host Hello everyone, first I'll go ahead and apologize for such a long post. I'd like to ask everyone; what works best for those of you backing up multiple Oracle db's from a single host. I have several Oracle 10g servers I backup. Each has anywhere from 1 to 20 db instances. I use a single policy and a common path & script name to backup the Oracle servers. This for me keeps the number of policies I have to manage down to a minimum. Our dba's have asked for one policy to be setup per DB. The reasoning behind this is that they want the flexibility to restart a failed backup without the restart initiating a backup of all DB's on servers. I told them that what they should be doing on failed DB backups is from the "activity monitor", right click on the failed Job ID and select restart. Here is where my lack of "in depth knowledge" of how NBU works with the Oracle RMAN API when a single stream fails. They asked, how does NBU know to just restart the backup for the DB that failed? The best "high level" reply I could come up with was that NBU tracks which DB piece it's backing up in a log and when a restart is initiated, it's able to request a backup of just the DB which that piece was associated with via calls to the Oracle RMAN API. In other words, restarting a single failed Jod ID from "activity monitor" for a backup stream associated with an Oracle backup does not mean that NBU looks at the policy and executes the backup script specified in the backup selection for all servers or just one server which is a member of that policy. Am I wrong? How does a restart work with Oracle? How do you backup Oracle servers which host multiple instances? What are the advantages and disadvantages if any with one policy per instance? Having a policy for each to me sounds like a nightmare in more than one way but I'd REALLY appreciate anyone's input here. Thanks in advance to everyone that replies! +-- |This was sent by norman_el...@discovery.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] Backing up multiple Oracle db's from a single host
Hello everyone, first I'll go ahead and apologize for such a long post. I'd like to ask everyone; what works best for those of you backing up multiple Oracle db's from a single host. I have several Oracle 10g servers I backup. Each has anywhere from 1 to 20 db instances. I use a single policy and a common path & script name to backup the Oracle servers. This for me keeps the number of policies I have to manage down to a minimum. Our dba's have asked for one policy to be setup per DB. The reasoning behind this is that they want the flexibility to restart a failed backup without the restart initiating a backup of all DB's on servers. I told them that what they should be doing on failed DB backups is from the "activity monitor", right click on the failed Job ID and select restart. Here is where my lack of "in depth knowledge" of how NBU works with the Oracle RMAN API when a single stream fails. They asked, how does NBU know to just restart the backup for the DB that failed? The best "high level" reply I could come up with was that NBU tracks which DB piece it's backing up in a log and when a restart is initiated, it's able to request a backup of just the DB which that piece was associated with via calls to the Oracle RMAN API. In other words, restarting a single failed Jod ID from "activity monitor" for a backup stream associated with an Oracle backup does not mean that NBU looks at the policy and executes the backup script specified in the backup selection for all servers or just one server which is a member of that policy. Am I wrong? How does a restart work with Oracle? How do you backup Oracle servers which host multiple instances? What are the advantages and disadvantages if any with one policy per instance? Having a policy for each to me sounds like a nightmare in more than one way but I'd REALLY appreciate anyone's input here. Thanks in advance to everyone that replies! +-- |This was sent by norman_el...@discovery.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
