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...
>
>