What's the best method for preparing for a SQL Server2K disaster? Is backing
up master, msdb and model as well as the logins and user databases enough?
Is it better to restore master and msdb or re-create the logins and jobs
(assuming they were scripted out).
Looking for other perspectives.
Thanks
Ron
Ron hi,
Check this article and you will find some ideas
http://support.microsoft.com/default...b;en-us;307775
HTH
Andreas
"Ron" wrote:
> What's the best method for preparing for a SQL Server2K disaster? Is backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>
|||Thanks - that shows good "How to" for the details. However I was looking for
more of an overview, bigger picture for DR.
Thanks.
Ron
"Andreas Mavrogenis" wrote:
[vbcol=seagreen]
> Ron hi,
> Check this article and you will find some ideas
> http://support.microsoft.com/default...b;en-us;307775
> HTH
> Andreas
> "Ron" wrote:
|||MASTER, MSDB and user database backup if fine.. this include most of the
things.. other then this, keep on taking registry backup of server nad
doucment your configuration setting of SQL Server.
You should do some dummy test for restoration of databases and validate what
backup policy you have for point in time recovery of user databases.
"Ron" wrote:
[vbcol=seagreen]
> Thanks - that shows good "How to" for the details. However I was looking for
> more of an overview, bigger picture for DR.
> Thanks.
> Ron
> "Andreas Mavrogenis" wrote:
|||If a brand new box is to replace the fail server, prepare the disk drive
mappings, processor, RAM, etc.
Other things include SQL server configuration, startup parameters, memory
configuration, scripted replications, and more.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
> What's the best method for preparing for a SQL Server2K disaster? Is
> backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>
|||Hi,
As writen, you must have a documented disaster recovery plan, in order to
perform these actions step-by-step, avoiding to forget something.
Also, if you have another machine, the ideal is to have it on another site
if applicable with all nesecary network routes.
A disaster plan is a subject to discuss because you have many-many option
according to your needs.
Following, for a well designed and documented DRP, in SQL 2000, consider
having a new machine, with SQL 2000 and try to enable log shipping
http://support.microsoft.com/default...b;en-us;323135
Finally, you can check this article for common FAQs on log shipping
http://support.microsoft.com/default...b;en-us;314515
HTH
Andreas
"Richard Ding" wrote:
> If a brand new box is to replace the fail server, prepare the disk drive
> mappings, processor, RAM, etc.
> Other things include SQL server configuration, startup parameters, memory
> configuration, scripted replications, and more.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
>
>
2012年3月11日星期日
Disaster Recovery question
What's the best method for preparing for a SQL Server2K disaster? Is backing
up master, msdb and model as well as the logins and user databases enough?
Is it better to restore master and msdb or re-create the logins and jobs
(assuming they were scripted out).
Looking for other perspectives.
Thanks
RonRon hi,
Check this article and you will find some ideas
http://support.microsoft.com/default.aspx?scid=kb;en-us;307775
HTH
Andreas
"Ron" wrote:
> What's the best method for preparing for a SQL Server2K disaster? Is backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>|||Thanks - that shows good "How to" for the details. However I was looking for
more of an overview, bigger picture for DR.
Thanks.
Ron
"Andreas Mavrogenis" wrote:
> Ron hi,
> Check this article and you will find some ideas
> http://support.microsoft.com/default.aspx?scid=kb;en-us;307775
> HTH
> Andreas
> "Ron" wrote:
> > What's the best method for preparing for a SQL Server2K disaster? Is backing
> > up master, msdb and model as well as the logins and user databases enough?
> >
> > Is it better to restore master and msdb or re-create the logins and jobs
> > (assuming they were scripted out).
> >
> > Looking for other perspectives.
> >
> > Thanks
> >
> > Ron
> >
> >|||MASTER, MSDB and user database backup if fine.. this include most of the
things.. other then this, keep on taking registry backup of server nad
doucment your configuration setting of SQL Server.
You should do some dummy test for restoration of databases and validate what
backup policy you have for point in time recovery of user databases.
"Ron" wrote:
> Thanks - that shows good "How to" for the details. However I was looking for
> more of an overview, bigger picture for DR.
> Thanks.
> Ron
> "Andreas Mavrogenis" wrote:
> > Ron hi,
> > Check this article and you will find some ideas
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;307775
> >
> > HTH
> > Andreas
> >
> > "Ron" wrote:
> >
> > > What's the best method for preparing for a SQL Server2K disaster? Is backing
> > > up master, msdb and model as well as the logins and user databases enough?
> > >
> > > Is it better to restore master and msdb or re-create the logins and jobs
> > > (assuming they were scripted out).
> > >
> > > Looking for other perspectives.
> > >
> > > Thanks
> > >
> > > Ron
> > >
> > >|||If a brand new box is to replace the fail server, prepare the disk drive
mappings, processor, RAM, etc.
Other things include SQL server configuration, startup parameters, memory
configuration, scripted replications, and more.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
> What's the best method for preparing for a SQL Server2K disaster? Is
> backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>|||Hi,
As writen, you must have a documented disaster recovery plan, in order to
perform these actions step-by-step, avoiding to forget something.
Also, if you have another machine, the ideal is to have it on another site
if applicable with all nesecary network routes.
A disaster plan is a subject to discuss because you have many-many option
according to your needs.
Following, for a well designed and documented DRP, in SQL 2000, consider
having a new machine, with SQL 2000 and try to enable log shipping
http://support.microsoft.com/default.aspx?scid=kb;en-us;323135
Finally, you can check this article for common FAQs on log shipping
http://support.microsoft.com/default.aspx?scid=kb;en-us;314515
HTH
Andreas
"Richard Ding" wrote:
> If a brand new box is to replace the fail server, prepare the disk drive
> mappings, processor, RAM, etc.
> Other things include SQL server configuration, startup parameters, memory
> configuration, scripted replications, and more.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
> > What's the best method for preparing for a SQL Server2K disaster? Is
> > backing
> > up master, msdb and model as well as the logins and user databases enough?
> >
> > Is it better to restore master and msdb or re-create the logins and jobs
> > (assuming they were scripted out).
> >
> > Looking for other perspectives.
> >
> > Thanks
> >
> > Ron
> >
> >
>
>
up master, msdb and model as well as the logins and user databases enough?
Is it better to restore master and msdb or re-create the logins and jobs
(assuming they were scripted out).
Looking for other perspectives.
Thanks
RonRon hi,
Check this article and you will find some ideas
http://support.microsoft.com/default.aspx?scid=kb;en-us;307775
HTH
Andreas
"Ron" wrote:
> What's the best method for preparing for a SQL Server2K disaster? Is backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>|||Thanks - that shows good "How to" for the details. However I was looking for
more of an overview, bigger picture for DR.
Thanks.
Ron
"Andreas Mavrogenis" wrote:
> Ron hi,
> Check this article and you will find some ideas
> http://support.microsoft.com/default.aspx?scid=kb;en-us;307775
> HTH
> Andreas
> "Ron" wrote:
> > What's the best method for preparing for a SQL Server2K disaster? Is backing
> > up master, msdb and model as well as the logins and user databases enough?
> >
> > Is it better to restore master and msdb or re-create the logins and jobs
> > (assuming they were scripted out).
> >
> > Looking for other perspectives.
> >
> > Thanks
> >
> > Ron
> >
> >|||MASTER, MSDB and user database backup if fine.. this include most of the
things.. other then this, keep on taking registry backup of server nad
doucment your configuration setting of SQL Server.
You should do some dummy test for restoration of databases and validate what
backup policy you have for point in time recovery of user databases.
"Ron" wrote:
> Thanks - that shows good "How to" for the details. However I was looking for
> more of an overview, bigger picture for DR.
> Thanks.
> Ron
> "Andreas Mavrogenis" wrote:
> > Ron hi,
> > Check this article and you will find some ideas
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;307775
> >
> > HTH
> > Andreas
> >
> > "Ron" wrote:
> >
> > > What's the best method for preparing for a SQL Server2K disaster? Is backing
> > > up master, msdb and model as well as the logins and user databases enough?
> > >
> > > Is it better to restore master and msdb or re-create the logins and jobs
> > > (assuming they were scripted out).
> > >
> > > Looking for other perspectives.
> > >
> > > Thanks
> > >
> > > Ron
> > >
> > >|||If a brand new box is to replace the fail server, prepare the disk drive
mappings, processor, RAM, etc.
Other things include SQL server configuration, startup parameters, memory
configuration, scripted replications, and more.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
> What's the best method for preparing for a SQL Server2K disaster? Is
> backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>|||Hi,
As writen, you must have a documented disaster recovery plan, in order to
perform these actions step-by-step, avoiding to forget something.
Also, if you have another machine, the ideal is to have it on another site
if applicable with all nesecary network routes.
A disaster plan is a subject to discuss because you have many-many option
according to your needs.
Following, for a well designed and documented DRP, in SQL 2000, consider
having a new machine, with SQL 2000 and try to enable log shipping
http://support.microsoft.com/default.aspx?scid=kb;en-us;323135
Finally, you can check this article for common FAQs on log shipping
http://support.microsoft.com/default.aspx?scid=kb;en-us;314515
HTH
Andreas
"Richard Ding" wrote:
> If a brand new box is to replace the fail server, prepare the disk drive
> mappings, processor, RAM, etc.
> Other things include SQL server configuration, startup parameters, memory
> configuration, scripted replications, and more.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
> > What's the best method for preparing for a SQL Server2K disaster? Is
> > backing
> > up master, msdb and model as well as the logins and user databases enough?
> >
> > Is it better to restore master and msdb or re-create the logins and jobs
> > (assuming they were scripted out).
> >
> > Looking for other perspectives.
> >
> > Thanks
> >
> > Ron
> >
> >
>
>
Disaster Recovery question
What's the best method for preparing for a SQL Server2K disaster? Is backin
g
up master, msdb and model as well as the logins and user databases enough?
Is it better to restore master and msdb or re-create the logins and jobs
(assuming they were scripted out).
Looking for other perspectives.
Thanks
RonRon hi,
Check this article and you will find some ideas
http://support.microsoft.com/defaul...kb;en-us;307775
HTH
Andreas
"Ron" wrote:
> What's the best method for preparing for a SQL Server2K disaster? Is back
ing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>|||Thanks - that shows good "How to" for the details. However I was looking fo
r
more of an overview, bigger picture for DR.
Thanks.
Ron
"Andreas Mavrogenis" wrote:
[vbcol=seagreen]
> Ron hi,
> Check this article and you will find some ideas
> http://support.microsoft.com/defaul...kb;en-us;307775
> HTH
> Andreas
> "Ron" wrote:
>|||MASTER, MSDB and user database backup if fine.. this include most of the
things.. other then this, keep on taking registry backup of server nad
doucment your configuration setting of SQL Server.
You should do some dummy test for restoration of databases and validate what
backup policy you have for point in time recovery of user databases.
"Ron" wrote:
[vbcol=seagreen]
> Thanks - that shows good "How to" for the details. However I was looking
for
> more of an overview, bigger picture for DR.
> Thanks.
> Ron
> "Andreas Mavrogenis" wrote:
>|||If a brand new box is to replace the fail server, prepare the disk drive
mappings, processor, RAM, etc.
Other things include SQL server configuration, startup parameters, memory
configuration, scripted replications, and more.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
> What's the best method for preparing for a SQL Server2K disaster? Is
> backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>|||Hi,
As writen, you must have a documented disaster recovery plan, in order to
perform these actions step-by-step, avoiding to forget something.
Also, if you have another machine, the ideal is to have it on another site
if applicable with all nesecary network routes.
A disaster plan is a subject to discuss because you have many-many option
according to your needs.
Following, for a well designed and documented DRP, in SQL 2000, consider
having a new machine, with SQL 2000 and try to enable log shipping
http://support.microsoft.com/defaul...kb;en-us;323135
Finally, you can check this article for common FAQs on log shipping
http://support.microsoft.com/defaul...kb;en-us;314515
HTH
Andreas
"Richard Ding" wrote:
> If a brand new box is to replace the fail server, prepare the disk drive
> mappings, processor, RAM, etc.
> Other things include SQL server configuration, startup parameters, memory
> configuration, scripted replications, and more.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
>
>
g
up master, msdb and model as well as the logins and user databases enough?
Is it better to restore master and msdb or re-create the logins and jobs
(assuming they were scripted out).
Looking for other perspectives.
Thanks
RonRon hi,
Check this article and you will find some ideas
http://support.microsoft.com/defaul...kb;en-us;307775
HTH
Andreas
"Ron" wrote:
> What's the best method for preparing for a SQL Server2K disaster? Is back
ing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>|||Thanks - that shows good "How to" for the details. However I was looking fo
r
more of an overview, bigger picture for DR.
Thanks.
Ron
"Andreas Mavrogenis" wrote:
[vbcol=seagreen]
> Ron hi,
> Check this article and you will find some ideas
> http://support.microsoft.com/defaul...kb;en-us;307775
> HTH
> Andreas
> "Ron" wrote:
>|||MASTER, MSDB and user database backup if fine.. this include most of the
things.. other then this, keep on taking registry backup of server nad
doucment your configuration setting of SQL Server.
You should do some dummy test for restoration of databases and validate what
backup policy you have for point in time recovery of user databases.
"Ron" wrote:
[vbcol=seagreen]
> Thanks - that shows good "How to" for the details. However I was looking
for
> more of an overview, bigger picture for DR.
> Thanks.
> Ron
> "Andreas Mavrogenis" wrote:
>|||If a brand new box is to replace the fail server, prepare the disk drive
mappings, processor, RAM, etc.
Other things include SQL server configuration, startup parameters, memory
configuration, scripted replications, and more.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
> What's the best method for preparing for a SQL Server2K disaster? Is
> backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>|||Hi,
As writen, you must have a documented disaster recovery plan, in order to
perform these actions step-by-step, avoiding to forget something.
Also, if you have another machine, the ideal is to have it on another site
if applicable with all nesecary network routes.
A disaster plan is a subject to discuss because you have many-many option
according to your needs.
Following, for a well designed and documented DRP, in SQL 2000, consider
having a new machine, with SQL 2000 and try to enable log shipping
http://support.microsoft.com/defaul...kb;en-us;323135
Finally, you can check this article for common FAQs on log shipping
http://support.microsoft.com/defaul...kb;en-us;314515
HTH
Andreas
"Richard Ding" wrote:
> If a brand new box is to replace the fail server, prepare the disk drive
> mappings, processor, RAM, etc.
> Other things include SQL server configuration, startup parameters, memory
> configuration, scripted replications, and more.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
>
>
Disaster Recovery Plan
Hello,
I have a question regarding SQL Server disaster recovery plan.
Lets say I backup quite regularily master, msdb, model and my
databases.
Is it enough to recover everything in case of dissaster? (I am
concerned about the SQL logins and users).
Lets say I have SQL login that maps to a Windows domain user.
Lets say the AD has to be restored.
After my SQL restauration (master, msdb, my databases) the logins in
SQL Server will they be OK?
Also another question regarding the backup.
A database full backup does not truncate the log.
I guess the log knows via a LSN mechanism that the full backup took
place and when the database full backup is restored followed by a Log
restauration from the LOG backup only the new (after the full backup)
will be restored.
Please confirm.
Any input is highly appreciated.
CarlyHi Carly
"Carly" wrote:
> Hello,
> I have a question regarding SQL Server disaster recovery plan.
> Lets say I backup quite regularily master, msdb, model and my
> databases.
> Is it enough to recover everything in case of dissaster? (I am
> concerned about the SQL logins and users).
> Lets say I have SQL login that maps to a Windows domain user.
> Lets say the AD has to be restored.
> After my SQL restauration (master, msdb, my databases) the logins in
> SQL Server will they be OK?
Restoring the Master database will restore the logins, so long as the
machine/domain are the same as the original server you should be ok. You may
also want to periodically script the recreating of the logins as a fall back
see http://support.microsoft.com/default.aspx/kb/246133/
> Also another question regarding the backup.
> A database full backup does not truncate the log.
> I guess the log knows via a LSN mechanism that the full backup took
> place and when the database full backup is restored followed by a Log
> restauration from the LOG backup only the new (after the full backup)
> will be restored.
> Please confirm.
Information on transaction log backups can be found at
http://msdn2.microsoft.com/en-us/library/aa173551(SQL.80).aspx
If you recover to a point in time only the committed transactions up to that
point in time will be recovered
http://msdn2.microsoft.com/en-us/library/aa196441(SQL.80).aspx#
For disaster recovery you will need to have a checklist of what the
requirements are for your scenario and how you fulfill them, and the
process(es) you need to recover from it. Once you have listed these for all
your possible scenarios, you should test them.
> Any input is highly appreciated.
> Carly
>
HTH
John
I have a question regarding SQL Server disaster recovery plan.
Lets say I backup quite regularily master, msdb, model and my
databases.
Is it enough to recover everything in case of dissaster? (I am
concerned about the SQL logins and users).
Lets say I have SQL login that maps to a Windows domain user.
Lets say the AD has to be restored.
After my SQL restauration (master, msdb, my databases) the logins in
SQL Server will they be OK?
Also another question regarding the backup.
A database full backup does not truncate the log.
I guess the log knows via a LSN mechanism that the full backup took
place and when the database full backup is restored followed by a Log
restauration from the LOG backup only the new (after the full backup)
will be restored.
Please confirm.
Any input is highly appreciated.
CarlyHi Carly
"Carly" wrote:
> Hello,
> I have a question regarding SQL Server disaster recovery plan.
> Lets say I backup quite regularily master, msdb, model and my
> databases.
> Is it enough to recover everything in case of dissaster? (I am
> concerned about the SQL logins and users).
> Lets say I have SQL login that maps to a Windows domain user.
> Lets say the AD has to be restored.
> After my SQL restauration (master, msdb, my databases) the logins in
> SQL Server will they be OK?
Restoring the Master database will restore the logins, so long as the
machine/domain are the same as the original server you should be ok. You may
also want to periodically script the recreating of the logins as a fall back
see http://support.microsoft.com/default.aspx/kb/246133/
> Also another question regarding the backup.
> A database full backup does not truncate the log.
> I guess the log knows via a LSN mechanism that the full backup took
> place and when the database full backup is restored followed by a Log
> restauration from the LOG backup only the new (after the full backup)
> will be restored.
> Please confirm.
Information on transaction log backups can be found at
http://msdn2.microsoft.com/en-us/library/aa173551(SQL.80).aspx
If you recover to a point in time only the committed transactions up to that
point in time will be recovered
http://msdn2.microsoft.com/en-us/library/aa196441(SQL.80).aspx#
For disaster recovery you will need to have a checklist of what the
requirements are for your scenario and how you fulfill them, and the
process(es) you need to recover from it. Once you have listed these for all
your possible scenarios, you should test them.
> Any input is highly appreciated.
> Carly
>
HTH
John
Disaster Recovery Plan
Hello,
I have a question regarding SQL Server disaster recovery plan.
Lets say I backup quite regularily master, msdb, model and my
databases.
Is it enough to recover everything in case of dissaster? (I am
concerned about the SQL logins and users).
Lets say I have SQL login that maps to a Windows domain user.
Lets say the AD has to be restored.
After my SQL restauration (master, msdb, my databases) the logins in
SQL Server will they be OK?
Also another question regarding the backup.
A database full backup does not truncate the log.
I guess the log knows via a LSN mechanism that the full backup took
place and when the database full backup is restored followed by a Log
restauration from the LOG backup only the new (after the full backup)
will be restored.
Please confirm.
Any input is highly appreciated.
Carly
Hi Carly
"Carly" wrote:
> Hello,
> I have a question regarding SQL Server disaster recovery plan.
> Lets say I backup quite regularily master, msdb, model and my
> databases.
> Is it enough to recover everything in case of dissaster? (I am
> concerned about the SQL logins and users).
> Lets say I have SQL login that maps to a Windows domain user.
> Lets say the AD has to be restored.
> After my SQL restauration (master, msdb, my databases) the logins in
> SQL Server will they be OK?
Restoring the Master database will restore the logins, so long as the
machine/domain are the same as the original server you should be ok. You may
also want to periodically script the recreating of the logins as a fall back
see http://support.microsoft.com/default.aspx/kb/246133/
> Also another question regarding the backup.
> A database full backup does not truncate the log.
> I guess the log knows via a LSN mechanism that the full backup took
> place and when the database full backup is restored followed by a Log
> restauration from the LOG backup only the new (after the full backup)
> will be restored.
> Please confirm.
Information on transaction log backups can be found at
http://msdn2.microsoft.com/en-us/library/aa173551(SQL.80).aspx
If you recover to a point in time only the committed transactions up to that
point in time will be recovered
http://msdn2.microsoft.com/en-us/library/aa196441(SQL.80).aspx#
For disaster recovery you will need to have a checklist of what the
requirements are for your scenario and how you fulfill them, and the
process(es) you need to recover from it. Once you have listed these for all
your possible scenarios, you should test them.
> Any input is highly appreciated.
> Carly
>
HTH
John
I have a question regarding SQL Server disaster recovery plan.
Lets say I backup quite regularily master, msdb, model and my
databases.
Is it enough to recover everything in case of dissaster? (I am
concerned about the SQL logins and users).
Lets say I have SQL login that maps to a Windows domain user.
Lets say the AD has to be restored.
After my SQL restauration (master, msdb, my databases) the logins in
SQL Server will they be OK?
Also another question regarding the backup.
A database full backup does not truncate the log.
I guess the log knows via a LSN mechanism that the full backup took
place and when the database full backup is restored followed by a Log
restauration from the LOG backup only the new (after the full backup)
will be restored.
Please confirm.
Any input is highly appreciated.
Carly
Hi Carly
"Carly" wrote:
> Hello,
> I have a question regarding SQL Server disaster recovery plan.
> Lets say I backup quite regularily master, msdb, model and my
> databases.
> Is it enough to recover everything in case of dissaster? (I am
> concerned about the SQL logins and users).
> Lets say I have SQL login that maps to a Windows domain user.
> Lets say the AD has to be restored.
> After my SQL restauration (master, msdb, my databases) the logins in
> SQL Server will they be OK?
Restoring the Master database will restore the logins, so long as the
machine/domain are the same as the original server you should be ok. You may
also want to periodically script the recreating of the logins as a fall back
see http://support.microsoft.com/default.aspx/kb/246133/
> Also another question regarding the backup.
> A database full backup does not truncate the log.
> I guess the log knows via a LSN mechanism that the full backup took
> place and when the database full backup is restored followed by a Log
> restauration from the LOG backup only the new (after the full backup)
> will be restored.
> Please confirm.
Information on transaction log backups can be found at
http://msdn2.microsoft.com/en-us/library/aa173551(SQL.80).aspx
If you recover to a point in time only the committed transactions up to that
point in time will be recovered
http://msdn2.microsoft.com/en-us/library/aa196441(SQL.80).aspx#
For disaster recovery you will need to have a checklist of what the
requirements are for your scenario and how you fulfill them, and the
process(es) you need to recover from it. Once you have listed these for all
your possible scenarios, you should test them.
> Any input is highly appreciated.
> Carly
>
HTH
John
Disaster Recovery Plan
Hello,
I have a question regarding SQL Server disaster recovery plan.
Lets say I backup quite regularily master, msdb, model and my
databases.
Is it enough to recover everything in case of dissaster? (I am
concerned about the SQL logins and users).
Lets say I have SQL login that maps to a Windows domain user.
Lets say the AD has to be restored.
After my SQL restauration (master, msdb, my databases) the logins in
SQL Server will they be OK?
Also another question regarding the backup.
A database full backup does not truncate the log.
I guess the log knows via a LSN mechanism that the full backup took
place and when the database full backup is restored followed by a Log
restauration from the LOG backup only the new (after the full backup)
will be restored.
Please confirm.
Any input is highly appreciated.
CarlyHi Carly
"Carly" wrote:
> Hello,
> I have a question regarding SQL Server disaster recovery plan.
> Lets say I backup quite regularily master, msdb, model and my
> databases.
> Is it enough to recover everything in case of dissaster? (I am
> concerned about the SQL logins and users).
> Lets say I have SQL login that maps to a Windows domain user.
> Lets say the AD has to be restored.
> After my SQL restauration (master, msdb, my databases) the logins in
> SQL Server will they be OK?
Restoring the Master database will restore the logins, so long as the
machine/domain are the same as the original server you should be ok. You may
also want to periodically script the recreating of the logins as a fall back
see http://support.microsoft.com/default.aspx/kb/246133/
> Also another question regarding the backup.
> A database full backup does not truncate the log.
> I guess the log knows via a LSN mechanism that the full backup took
> place and when the database full backup is restored followed by a Log
> restauration from the LOG backup only the new (after the full backup)
> will be restored.
> Please confirm.
Information on transaction log backups can be found at
http://msdn2.microsoft.com/en-us/library/aa173551(SQL.80).aspx
If you recover to a point in time only the committed transactions up to that
point in time will be recovered
http://msdn2.microsoft.com/en-us/library/aa196441(SQL.80).aspx#
For disaster recovery you will need to have a checklist of what the
requirements are for your scenario and how you fulfill them, and the
process(es) you need to recover from it. Once you have listed these for all
your possible scenarios, you should test them.
> Any input is highly appreciated.
> Carly
>
HTH
John
I have a question regarding SQL Server disaster recovery plan.
Lets say I backup quite regularily master, msdb, model and my
databases.
Is it enough to recover everything in case of dissaster? (I am
concerned about the SQL logins and users).
Lets say I have SQL login that maps to a Windows domain user.
Lets say the AD has to be restored.
After my SQL restauration (master, msdb, my databases) the logins in
SQL Server will they be OK?
Also another question regarding the backup.
A database full backup does not truncate the log.
I guess the log knows via a LSN mechanism that the full backup took
place and when the database full backup is restored followed by a Log
restauration from the LOG backup only the new (after the full backup)
will be restored.
Please confirm.
Any input is highly appreciated.
CarlyHi Carly
"Carly" wrote:
> Hello,
> I have a question regarding SQL Server disaster recovery plan.
> Lets say I backup quite regularily master, msdb, model and my
> databases.
> Is it enough to recover everything in case of dissaster? (I am
> concerned about the SQL logins and users).
> Lets say I have SQL login that maps to a Windows domain user.
> Lets say the AD has to be restored.
> After my SQL restauration (master, msdb, my databases) the logins in
> SQL Server will they be OK?
Restoring the Master database will restore the logins, so long as the
machine/domain are the same as the original server you should be ok. You may
also want to periodically script the recreating of the logins as a fall back
see http://support.microsoft.com/default.aspx/kb/246133/
> Also another question regarding the backup.
> A database full backup does not truncate the log.
> I guess the log knows via a LSN mechanism that the full backup took
> place and when the database full backup is restored followed by a Log
> restauration from the LOG backup only the new (after the full backup)
> will be restored.
> Please confirm.
Information on transaction log backups can be found at
http://msdn2.microsoft.com/en-us/library/aa173551(SQL.80).aspx
If you recover to a point in time only the committed transactions up to that
point in time will be recovered
http://msdn2.microsoft.com/en-us/library/aa196441(SQL.80).aspx#
For disaster recovery you will need to have a checklist of what the
requirements are for your scenario and how you fulfill them, and the
process(es) you need to recover from it. Once you have listed these for all
your possible scenarios, you should test them.
> Any input is highly appreciated.
> Carly
>
HTH
John
2012年3月8日星期四
Disaster Recovery
What order should I restore databases in when I am doing a disaster
recovery? By databases I mean:
Master
Model
Msdb
All Other DatabasesHi
Correct. Just go through the processes on how to restore master DB in BOL.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike Johnson" <mj@.microsoft.com> wrote in message
news:udr74rL$EHA.1300@.TK2MSFTNGP14.phx.gbl...
> What order should I restore databases in when I am doing a disaster
> recovery? By databases I mean:
> Master
> Model
> Msdb
> All Other Databases
>
recovery? By databases I mean:
Master
Model
Msdb
All Other DatabasesHi
Correct. Just go through the processes on how to restore master DB in BOL.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike Johnson" <mj@.microsoft.com> wrote in message
news:udr74rL$EHA.1300@.TK2MSFTNGP14.phx.gbl...
> What order should I restore databases in when I am doing a disaster
> recovery? By databases I mean:
> Master
> Model
> Msdb
> All Other Databases
>
订阅：
博文 (Atom)