Hi Simon,
If there are multiple SAN media servers, have you looked into SSO and/or
unrestricted media sharing?
http://www.symantec.com/connect/forums/can-we-assign-medias-multiple-media-s
ervers
One other option I can see until there is a better solution is to try and
start spacing the backups out:
Group A: 9pm
Group B: 9:30pm
Group C: 10:00pm
You also have the option of limiting it on the master server the maximum
simultaneous jobs *per client* if you did that, there would be at least N
number (your choosing) of jobs running on a per-client basis. Between
changing the schedule or changing the maximum simultaneous jobs per client,
I would try that first and then look into the options mentioned
earlier/after.
Would that be possible to alleviate some of the headache for the FULL/INCR?
I know for archive logs (re-do) you need to keep the drives available 24/7.
"But I believe because the policies are using its own SAN media server as a
storage unit, it's only backing up itself, therefore a tape is assigned to
that policy."
I would check the unrestricted media sharing/look at SSO and see if that
could possibly apply to your environment, I've not used those options
myself, but they be work taking a look at.
Justin.
> -----Original Message-----
> From: Simon Weaver [mailto:Simon.Weaver AT iscl DOT net]
> Sent: Wednesday, December 18, 2013 3:56 PM
> To: Justin Piszcz
> Cc: VERITAS-BU AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] SAP backups / Online / Redo
>
> Hi Justin
> In specific it's SAP jobs.
>
> As mentioned over 60 policies start from 9pm but each one is a SAN media
> server and each client in its own policy. So I have 10 SAP jobs each using
a
> tape drive from library.
>
> This means other jobs end up queued.
>
> I can run thousands ok jobs... But jobs will queue if no drives are
available to
> do the backups on.
>
> Backups using same volume pool. But I believe because the policies are
using
> its own SAN media server as a storage unit, it's only backing up itself,
> therefore a tape is assigned to that policy.
>
> I'd like to find out why I could not group multiple SAP backups together.
> These jobs Justin run a command script, and they start the parent & child
> jobs.
>
> S.
>
> > On 18 Dec 2013, at 20:05, "Justin Piszcz" <jpiszcz AT lucidpixels DOT com>
wrote:
> >
> > Hi Simon,
> >
> > Some comments:
> > 1. How many jobs are too many? 500 concurrent jobs? 1000 concurrent
> jobs?
> > 2000 concurrent jobs? With a UNIX master, if properly spec'd out-- I've
> > seen it handle 1000-1500 jobs without a problem.
> > 2. Have you considered moving the platform to Linux or adding additional
> > Windows media servers to help cope with the load?
> > 3. Are all of the backups using the same volume pool?
> > 4. "All LTO4 drives are maxed out" -- the drives themselves are full,
(tape
> > loaded, ok), but did you also mean they are maxed out throughput-wise as
> > well? Are you achieving 90MiB/s (if already compressed) data to each
one?
> > If not, have you considered increasing the multiplexing?
> > 5. If there are a bunch of single-stream host jobs, I'm assuming you are
> > *disallowing* multiple streams, otherwise that would seem to get out of
> > control quickly?
> >
> > The background I have is with Oracle, not SAP though, so my comments
> revolve
> > around those types of backups.
> >
> > Justin.
> >
> >> -----Original Message-----
> >> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-
> >> bounces AT mailman.eng.auburn DOT edu] On Behalf Of Simon Weaver
> >> Sent: Wednesday, December 18, 2013 2:54 PM
> >> To: VERITAS-BU AT mailman.eng.auburn DOT edu
> >> Subject: [Veritas-bu] SAP backups / Online / Redo
> >>
> >> All
> >> I've been trying to troubleshoot performance and backup issues at an
> >> environment where all LTO4 drives are maxed out with these type of jobs
> >> and causing many others to queue or run at an incorrect time.
> >>
> >> There are close to around 60 policies where we have online, off-line,
and
> >> redo log backups.
> >>
> >> In each policy there was only a single client listed. A lot of these
> > policies are
> >> sand media servers therefore they backup themselves.
> >>
> >> The problem is we have too many jobs running concurrently and due to
> the
> >> vast amount of data on the servers, there is insufficient resources
> > available
> >> for NBU to resume the queued jobs.
> >>
> >> I would be interested to know if anyone else has a large environment of
> >> SAP/Oracle backups and what they do backups, because presently these
> >> jobs I can shaming 98% of our resources and our windows phone service I
> >> currently struggling to get backed up.
> >>
> >> This separate tape drive all these will be in place, but I want to
enquire
> > if
> >> there is anything that could be done to may be group the SAP online
> > backups
> >> into one policy.
> >>
> >> But I'm also interested to hear of any ideas or methods that you may be
> >> using now.
> >>
> >> Thanks
> >> Si
> >> _______________________________________________
> >> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> >> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
> >
> >
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
