I have recently been asked to produce a document recommending backup and
restore best practices in a new company.
They current use a very large backup script in a stored procedure (with
parameters) which is used across all servers that automates things to a large
degree. Whilst I can see the advantages of this I can see more bad than good.
This script is obviously scheduled within a job, this has many steps of
other operations.
Does anyone have any good references for the best backup procedures/ setup
that will help me come to some kind of decision?
e.g. For instance setup of the jobs/ setps, storage locations of files,
frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
sqlBackupDevices (or not), alerting etc etc.
I have many many books that I can look at, so I'm not looking for
information on how to do stuff, only Best Practice (or Functional)
recommendations
Thanks in advance.
--
Best Regards,
Mark BroadbentMark
http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1
--administaiting best practices
"Mark Broadbent" <nospam@.nospam.com> wrote in message
news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>I have recently been asked to produce a document recommending backup and
> restore best practices in a new company.
> They current use a very large backup script in a stored procedure (with
> parameters) which is used across all servers that automates things to a
> large
> degree. Whilst I can see the advantages of this I can see more bad than
> good.
> This script is obviously scheduled within a job, this has many steps of
> other operations.
> Does anyone have any good references for the best backup procedures/ setup
> that will help me come to some kind of decision?
> e.g. For instance setup of the jobs/ setps, storage locations of files,
> frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
> sqlBackupDevices (or not), alerting etc etc.
> I have many many books that I can look at, so I'm not looking for
> information on how to do stuff, only Best Practice (or Functional)
> recommendations
> Thanks in advance.
> --
> Best Regards,
> Mark Broadbent|||Had already found this URI, but am hoping for more detailed information (or
Microsoft recommend docs/ links).
Thanks anyway for your input.
--
Best Regards,
Mark Broadbent
"Uri Dimant" wrote:
> Mark
> http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1
> --administaiting best practices
>
>
>
> "Mark Broadbent" <nospam@.nospam.com> wrote in message
> news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
> >I have recently been asked to produce a document recommending backup and
> > restore best practices in a new company.
> >
> > They current use a very large backup script in a stored procedure (with
> > parameters) which is used across all servers that automates things to a
> > large
> > degree. Whilst I can see the advantages of this I can see more bad than
> > good.
> > This script is obviously scheduled within a job, this has many steps of
> > other operations.
> >
> > Does anyone have any good references for the best backup procedures/ setup
> > that will help me come to some kind of decision?
> >
> > e.g. For instance setup of the jobs/ setps, storage locations of files,
> > frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
> > sqlBackupDevices (or not), alerting etc etc.
> >
> > I have many many books that I can look at, so I'm not looking for
> > information on how to do stuff, only Best Practice (or Functional)
> > recommendations
> >
> > Thanks in advance.
> > --
> > Best Regards,
> >
> > Mark Broadbent
>
>|||The Operations Guide has some information as well. Not just
the backup and restore section but the Administrative tasks
and other areas in the section on Systems Administration:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops4.mspx
-Sue
On Wed, 27 Sep 2006 07:33:02 -0700, Mark Broadbent
<nospam@.nospam.com> wrote:
>Had already found this URI, but am hoping for more detailed information (or
>Microsoft recommend docs/ links).
>Thanks anyway for your input.
