Veritas-bu

[Veritas-bu] SQL agent backups

2005-07-27 13:19:44
Subject: [Veritas-bu] SQL agent backups
From: pkeating AT bank-banque-canada DOT ca (Paul Keating)
Date: Wed, 27 Jul 2005 13:19:44 -0400
This is a multi-part message in MIME format.

------_=_NextPart_001_01C592CF.61E421E4
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Been looking into deploying SQL agent now, vs stopping DB's to back em
up cold.
=20
In previous environments I've worked with the Oracle Agents on machines
that were "borderline" on disk capacity, and the DB server spawned the
backup jobs, and look out if one failed cuz the fertilizer would hit the
ventilator......they had enough disk to run about 5 hours without a
backup to flush logs.
=20
In my current environment, we're implementing a couple SQL servers that
will have 100+ Gig DBs, so dumping to disk to backup is pretty much out
of the question due to disk space, but if I were to install SQL agents,
how would that affect my, otherwise busy, Netbackup environment?
=20
Can I still control, from the master, when jobs will start (I'm not
talking backup windows, but rather scheduling jobs)=20
Server initiated, vs client initiated backups, if you will.
I'm under the impression that the client starts the job, which I suppose
is true for ANY client, though "normal" backups are started when
directed by the master.
I guess I was under the impression that the backup schedul for SQL agent
had to be configured via the client, vs via the master.
=20
Also, if a SQL server agent job queues, will it happily sit in the queue
untill resources become available? as if it were a fileserver? or do
agent jobs have to get to tape FAST.
=20
Any input would be appreciated.
=20
Paul

------_=_NextPart_001_01C592CF.61E421E4
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>Been =
looking into=20
deploying SQL agent now, vs stopping DB's to back em up=20
cold.</FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>In =
previous=20
environments I've worked with the Oracle Agents on machines that were=20
"borderline" on disk capacity, and the DB server spawned the backup =
jobs, and=20
look out if one failed cuz the fertilizer would hit the =
ventilator......they had=20
enough disk to run about 5 hours without a backup to flush=20
logs.</FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>In my =
current=20
environment, we're implementing a couple SQL servers that will have 100+ =
Gig=20
DBs, so dumping to disk to backup is pretty much out of the question due =
to disk=20
space, but if I were to install SQL agents, how would that affect my, =
otherwise=20
busy, Netbackup environment?</FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>Can I =
still control,=20
from the master, when jobs will start (I'm not talking backup windows, =
but=20
rather scheduling jobs) </FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>Server =
initiated, vs=20
client initiated backups, if you will.</FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>I'm =
under the=20
impression that the client starts the job, which I suppose is true for =
ANY=20
client, though "normal" backups are started when directed by the=20
master.</FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>I =
guess I was under=20
the impression that the backup schedul for SQL agent had to be =
configured via=20
the client, vs via the master.</FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>Also, =
if a SQL=20
server agent job queues, will it happily sit in the queue untill =
resources=20
become available? as if it were a fileserver? or do agent jobs have to =
get to=20
tape FAST.</FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial size=3D2>Any =
input would be=20
appreciated.</FONT></SPAN></DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D367415916-27072005><FONT face=3DArial=20
size=3D2>Paul</FONT></SPAN></DIV></BODY></HTML>
=00
------_=_NextPart_001_01C592CF.61E421E4--

<Prev in Thread] Current Thread [Next in Thread>