Veritas-bu

[Veritas-bu] SQL agent backups

2005-07-27 22:40:27
Subject: [Veritas-bu] SQL agent backups
From: Dean <dean.deano AT gmail DOT com> (Dean)
Date: Thu, 28 Jul 2005 12:40:27 +1000
------=_Part_281_15020672.1122518427488
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 7/28/05, Paul Keating <pkeating AT bank-banque-canada DOT ca> wrote:=20
>=20
> Can I still control, from the master, when jobs will start (I'm not=20
> talking backup windows, but rather scheduling jobs)=20
>=20
 Yes. Normal NBU scheduling can be used.

 Server initiated, vs client initiated backups, if you will.
> I'm under the impression that the client starts the job, which I suppose=
=20
> is true for ANY client, though "normal" backups are started when directed=
 by=20
> the master.
>=20
 You use the NBU client on the SQL server to generate a backup script, and=
=20
save it somewhere on the client. That script can then be triggered either=
=20
through the NBU client GUI, or possibly through SQL Server somehow (I don't=
=20
know). But it can also be called by a policy being triggered by the NBU=20
master. In the policy definition, you don't specify a list of files or=20
databases to backup, but you instead specify the backup script location on=
=20
the client.

 I guess I was under the impression that the backup schedul for SQL agent=
=20
> had to be configured via the client, vs via the master.
>=20
 See above. The first bit - generating the script - is done on the client.=
=20
The policy is managed from the master, just like any other kind of backup=
=20
(except there's no file list).

>  Also, if a SQL server agent job queues, will it happily sit in the queue=
=20
> untill resources become available? as if it were a fileserver? or do agen=
t=20
> jobs have to get to tape FAST.
>=20
 They queue fine. Although I've only worked with relatively quiet SQL=20
servers.

  Any input would be appreciated.
>  Paul
>

------=_Part_281_15020672.1122518427488
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div><span class=3D"gmail_quote">On 7/28/05, <b class=3D"gmail_sendername">=
Paul Keating</b> &lt;<a href=3D"mailto:pkeating AT bank-banque-canada DOT 
ca">pkea=
ting AT bank-banque-canada DOT ca</a>&gt; wrote:</span>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><span><font face=3D"Arial" size=3D"2">Can I still control, from the ma=
ster, when jobs will start (I'm not talking backup windows, but rather sche=
duling jobs) </font></span></div></blockquote>
<div>&nbsp;</div>
<div>Yes. Normal NBU scheduling can be used.</div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><span><font face=3D"Arial" size=3D"2">Server initiated, vs client init=
iated backups, if you will.</font></span></div>
<div><span><font face=3D"Arial" size=3D"2">I'm under the impression that th=
e client starts the job, which I suppose is true for ANY client, though &qu=
ot;normal&quot; backups are started when directed by the master.</font></sp=
an>
</div></blockquote>
<div>&nbsp;</div>
<div>You use the NBU client on the SQL server to generate a backup script, =
and save it somewhere on the client. That script can then be triggered eith=
er through the NBU client GUI, or possibly through SQL Server somehow (I do=
n't know). But it can also be called by a policy being triggered by the NBU=
 master. In the policy definition, you don't specify a list of files or dat=
abases to backup, but you instead specify the backup script location on the=
 client.
</div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><span><font face=3D"Arial" size=3D"2">I guess I was under the impressi=
on that the backup schedul for SQL agent had to be configured via the clien=
t, vs via the master.</font></span></div></blockquote>
<div>&nbsp;</div>
<div>See above. The first bit - generating the script - is done on the clie=
nt. The policy is managed from the master, just like any other kind of back=
up (except there's no file list).</div>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>&nbsp;</div>
<div><span><font face=3D"Arial" size=3D"2">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.</fo=
nt>
</span></div></blockquote>
<div>&nbsp;</div>
<div>They queue fine. Although I've only worked with relatively quiet SQL s=
ervers.</div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>&nbsp;</div>
<div><span><font face=3D"Arial" size=3D"2">Any input would be appreciated.<=
/font></span></div><span class=3D"sg">
<div><span><font face=3D"Arial" size=3D"2"></font></span>&nbsp;</div>
<div><span><font face=3D"Arial" size=3D"2">Paul</font></span></div></span><=
/blockquote></div><br>

------=_Part_281_15020672.1122518427488--

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