We are running SQL Server 2000 Standard Edition
Every night, I want to take a backup of our production database and
restore it to another database that is used for reporting/DR
purposes.
My thinking was as follows:
(1) Setup a job on the source (production) to create the backup to a
named file
(2) Setup a job on the destination (DR) sometime later to restore the
backup
Is this the best way to do this?
Perhaps I could create 1 job to do both?Hi
Do you want to do that on dayly,weekly period?
Take a look at WITH MOVE option in the BOL
"PromisedOyster" <PromisedOyster@.hotmail.com> wrote in message
news:1173960621.133170.194740@.l77g2000hsb.googlegroups.com...
> We are running SQL Server 2000 Standard Edition
> Every night, I want to take a backup of our production database and
> restore it to another database that is used for reporting/DR
> purposes.
> My thinking was as follows:
> (1) Setup a job on the source (production) to create the backup to a
> named file
> (2) Setup a job on the destination (DR) sometime later to restore the
> backup
> Is this the best way to do this?
> Perhaps I could create 1 job to do both?
>|||Hello,
If your database size is not huge you could do the way you mentioned. If the
database is really big take a look into the LOGSHIPPING option.
In SQL 2000 standard you may need to manually configure logshipping. take a
look into the below URL:-
http://www.sqlmag.com/Article/Artic...rver_23231.html
Thanks
Hari
"PromisedOyster" <PromisedOyster@.hotmail.com> wrote in message
news:1173960621.133170.194740@.l77g2000hsb.googlegroups.com...
> We are running SQL Server 2000 Standard Edition
> Every night, I want to take a backup of our production database and
> restore it to another database that is used for reporting/DR
> purposes.
> My thinking was as follows:
> (1) Setup a job on the source (production) to create the backup to a
> named file
> (2) Setup a job on the destination (DR) sometime later to restore the
> backup
> Is this the best way to do this?
> Perhaps I could create 1 job to do both?
>
Showing posts with label andrestore. Show all posts
Showing posts with label andrestore. Show all posts
Wednesday, March 7, 2012
Backup and restore to another database
We are running SQL Server 2000 Standard Edition
Every night, I want to take a backup of our production database and
restore it to another database that is used for reporting/DR
purposes.
My thinking was as follows:
(1) Setup a job on the source (production) to create the backup to a
named file
(2) Setup a job on the destination (DR) sometime later to restore the
backup
Is this the best way to do this?
Perhaps I could create 1 job to do both?
Hi
Do you want to do that on dayly,weekly period?
Take a look at WITH MOVE option in the BOL
"PromisedOyster" <PromisedOyster@.hotmail.com> wrote in message
news:1173960621.133170.194740@.l77g2000hsb.googlegr oups.com...
> We are running SQL Server 2000 Standard Edition
> Every night, I want to take a backup of our production database and
> restore it to another database that is used for reporting/DR
> purposes.
> My thinking was as follows:
> (1) Setup a job on the source (production) to create the backup to a
> named file
> (2) Setup a job on the destination (DR) sometime later to restore the
> backup
> Is this the best way to do this?
> Perhaps I could create 1 job to do both?
>
|||Hello,
If your database size is not huge you could do the way you mentioned. If the
database is really big take a look into the LOGSHIPPING option.
In SQL 2000 standard you may need to manually configure logshipping. take a
look into the below URL:-
http://www.sqlmag.com/Article/ArticleID/23231/sql_server_23231.html
Thanks
Hari
"PromisedOyster" <PromisedOyster@.hotmail.com> wrote in message
news:1173960621.133170.194740@.l77g2000hsb.googlegr oups.com...
> We are running SQL Server 2000 Standard Edition
> Every night, I want to take a backup of our production database and
> restore it to another database that is used for reporting/DR
> purposes.
> My thinking was as follows:
> (1) Setup a job on the source (production) to create the backup to a
> named file
> (2) Setup a job on the destination (DR) sometime later to restore the
> backup
> Is this the best way to do this?
> Perhaps I could create 1 job to do both?
>
Every night, I want to take a backup of our production database and
restore it to another database that is used for reporting/DR
purposes.
My thinking was as follows:
(1) Setup a job on the source (production) to create the backup to a
named file
(2) Setup a job on the destination (DR) sometime later to restore the
backup
Is this the best way to do this?
Perhaps I could create 1 job to do both?
Hi
Do you want to do that on dayly,weekly period?
Take a look at WITH MOVE option in the BOL
"PromisedOyster" <PromisedOyster@.hotmail.com> wrote in message
news:1173960621.133170.194740@.l77g2000hsb.googlegr oups.com...
> We are running SQL Server 2000 Standard Edition
> Every night, I want to take a backup of our production database and
> restore it to another database that is used for reporting/DR
> purposes.
> My thinking was as follows:
> (1) Setup a job on the source (production) to create the backup to a
> named file
> (2) Setup a job on the destination (DR) sometime later to restore the
> backup
> Is this the best way to do this?
> Perhaps I could create 1 job to do both?
>
|||Hello,
If your database size is not huge you could do the way you mentioned. If the
database is really big take a look into the LOGSHIPPING option.
In SQL 2000 standard you may need to manually configure logshipping. take a
look into the below URL:-
http://www.sqlmag.com/Article/ArticleID/23231/sql_server_23231.html
Thanks
Hari
"PromisedOyster" <PromisedOyster@.hotmail.com> wrote in message
news:1173960621.133170.194740@.l77g2000hsb.googlegr oups.com...
> We are running SQL Server 2000 Standard Edition
> Every night, I want to take a backup of our production database and
> restore it to another database that is used for reporting/DR
> purposes.
> My thinking was as follows:
> (1) Setup a job on the source (production) to create the backup to a
> named file
> (2) Setup a job on the destination (DR) sometime later to restore the
> backup
> Is this the best way to do this?
> Perhaps I could create 1 job to do both?
>
Saturday, February 25, 2012
Backup and Restore best practices
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
Mark
http://vyaskn.tripod.com/sql_server_...ices.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_...ices.htm#Step1
> --administaiting best practices
>
>
>
> "Mark Broadbent" <nospam@.nospam.com> wrote in message
> news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>
>
|||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/pro...n/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.
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
Mark
http://vyaskn.tripod.com/sql_server_...ices.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_...ices.htm#Step1
> --administaiting best practices
>
>
>
> "Mark Broadbent" <nospam@.nospam.com> wrote in message
> news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>
>
|||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/pro...n/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.
Backup and Restore best practices
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 larg
e
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_serve...r />
.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
> [url]http://vyaskn.tripod.com/ sql_server_administration_best_practices
.htm#Step1[/url
]
> --administaiting best practices
>
>
>
> "Mark Broadbent" <nospam@.nospam.com> wrote in message
> news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>
>|||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/pr...in/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.
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 larg
e
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_serve...r />
.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
> [url]http://vyaskn.tripod.com/ sql_server_administration_best_practices
.htm#Step1[/url
]
> --administaiting best practices
>
>
>
> "Mark Broadbent" <nospam@.nospam.com> wrote in message
> news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>
>|||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/pr...in/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.
Subscribe to:
Posts (Atom)