Display date: master

显示标签为“master”的博文。显示所有博文

2012年3月11日星期日

Disaster Recovery rehearsal

Hi,
I am performing a disaster recovery reharsal for SQL
Server with various test cases on a Test Server. I want to
corrupt the Master Database( without deleting the .ldf)
Manually and then try to recover. Which is the best way to
do this? . also Any resources on Disaster Recovery
reharsals on SQL Servers are appreciated.
Regards
ChipHi
check out following articles about disaster recovery
http://www.sqljunkies.com/HowTo/F30B1E5F-F50F-40A8-96F2-476CEAD46C79.scuk
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;307775
Regards,
MD
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> Hi,
> I am performing a disaster recovery reharsal for SQL
> Server with various test cases on a Test Server. I want to
> corrupt the Master Database( without deleting the .ldf)
> Manually and then try to recover. Which is the best way to
> do this? . also Any resources on Disaster Recovery
> reharsals on SQL Servers are appreciated.
> Regards
> Chip|||Do you want it to go suspect or just cause a corruption in the master
database?
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> Hi,
> I am performing a disaster recovery reharsal for SQL
> Server with various test cases on a Test Server. I want to
> corrupt the Master Database( without deleting the .ldf)
> Manually and then try to recover. Which is the best way to
> do this? . also Any resources on Disaster Recovery
> reharsals on SQL Servers are appreciated.
> Regards
> Chip|||hi Tibor,
Thanks for the response. what should i do to go it to
suspect(without deleting .ldf) and how to cause a
corruption. Please suggest both ways so that I can have
two test cases in hand. :-)
Sincere Regards
Chip.
>--Original Message--
>Do you want it to go suspect or just cause a corruption
in the master
>database?
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Chip" <anonymous@.discussions.microsoft.com> wrote in
message
>news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
>> Hi,
>> I am performing a disaster recovery reharsal for SQL
>> Server with various test cases on a Test Server. I want
to
>> corrupt the Master Database( without deleting the .ldf)
>> Manually and then try to recover. Which is the best way
to
>> do this? . also Any resources on Disaster Recovery
>> reharsals on SQL Servers are appreciated.
>> Regards
>> Chip
>
>.
>|||Chip,
To make it corrupt, you can create a table and for the table hack some value
in the sysindexes table (IAM column, for instance). You need to figure out
how to do modifications against the systems tables as I don't want to put
that information in a public place.
As for suspect, read the source code for sp_resetstatus and reverse what it
does. It should work on the master database...
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:e98501c3f154$c22ad640$a301280a@.phx.gbl...
> hi Tibor,
> Thanks for the response. what should i do to go it to
> suspect(without deleting .ldf) and how to cause a
> corruption. Please suggest both ways so that I can have
> two test cases in hand. :-)
> Sincere Regards
> Chip.
> >--Original Message--
> >Do you want it to go suspect or just cause a corruption
> in the master
> >database?
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> >> Hi,
> >>
> >> I am performing a disaster recovery reharsal for SQL
> >> Server with various test cases on a Test Server. I want
> to
> >> corrupt the Master Database( without deleting the .ldf)
> >> Manually and then try to recover. Which is the best way
> to
> >> do this? . also Any resources on Disaster Recovery
> >> reharsals on SQL Servers are appreciated.
> >>
> >> Regards
> >>
> >> Chip
> >
> >
> >.
> >|||Poor me.
Not a expert dba to hack and crack :-(. If it is possible
to mail the procedure, I will be greatful. I need to
perform this at any cost and send the details to my boss
with step-by-step procedure :-(. Any resources pointing to
achieve this are highly appreciated.
Chip
chipsin007@.NOSPAM.yahoo.com
>--Original Message--
>Chip,
>To make it corrupt, you can create a table and for the
table hack some value
>in the sysindexes table (IAM column, for instance). You
need to figure out
>how to do modifications against the systems tables as I
don't want to put
>that information in a public place.
>As for suspect, read the source code for sp_resetstatus
and reverse what it
>does. It should work on the master database...
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Chip" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e98501c3f154$c22ad640$a301280a@.phx.gbl...
>> hi Tibor,
>> Thanks for the response. what should i do to go it to
>> suspect(without deleting .ldf) and how to cause a
>> corruption. Please suggest both ways so that I can have
>> two test cases in hand. :-)
>> Sincere Regards
>> Chip.
>> >--Original Message--
>> >Do you want it to go suspect or just cause a corruption
>> in the master
>> >database?
>> >
>> >--
>> >Tibor Karaszi, SQL Server MVP
>> >Archive at:
>> >http://groups.google.com/groups?
>> oi=djq&as_ugroup=microsoft.public.sqlserver
>> >
>> >
>> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
>> >> Hi,
>> >>
>> >> I am performing a disaster recovery reharsal for SQL
>> >> Server with various test cases on a Test Server. I
want
>> to
>> >> corrupt the Master Database( without deleting
the .ldf)
>> >> Manually and then try to recover. Which is the best
way
>> to
>> >> do this? . also Any resources on Disaster Recovery
>> >> reharsals on SQL Servers are appreciated.
>> >>
>> >> Regards
>> >>
>> >> Chip
>> >
>> >
>> >.
>> >
>
>.
>|||You won't, to my knowledge, find any such resources. And I don't have any
ready-made scripts as I always do them as I go along. On top for the first
one is sp_configure and the "allow updates" option. As for the second one,
you need to read the source code of sp_resetstatus and make appropriate
changes (the suspect status is in the status column if
master..sysdatabases). If this makes no sense to you, you really need to
bring someone in to do these things... :-)
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:e9d401c3f15c$1898d3e0$a301280a@.phx.gbl...
> Poor me.
> Not a expert dba to hack and crack :-(. If it is possible
> to mail the procedure, I will be greatful. I need to
> perform this at any cost and send the details to my boss
> with step-by-step procedure :-(. Any resources pointing to
> achieve this are highly appreciated.
> Chip
> chipsin007@.NOSPAM.yahoo.com
> >--Original Message--
> >Chip,
> >
> >To make it corrupt, you can create a table and for the
> table hack some value
> >in the sysindexes table (IAM column, for instance). You
> need to figure out
> >how to do modifications against the systems tables as I
> don't want to put
> >that information in a public place.
> >As for suspect, read the source code for sp_resetstatus
> and reverse what it
> >does. It should work on the master database...
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:e98501c3f154$c22ad640$a301280a@.phx.gbl...
> >> hi Tibor,
> >>
> >> Thanks for the response. what should i do to go it to
> >> suspect(without deleting .ldf) and how to cause a
> >> corruption. Please suggest both ways so that I can have
> >> two test cases in hand. :-)
> >>
> >> Sincere Regards
> >>
> >> Chip.
> >> >--Original Message--
> >> >Do you want it to go suspect or just cause a corruption
> >> in the master
> >> >database?
> >> >
> >> >--
> >> >Tibor Karaszi, SQL Server MVP
> >> >Archive at:
> >> >http://groups.google.com/groups?
> >> oi=djq&as_ugroup=microsoft.public.sqlserver
> >> >
> >> >
> >> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
> >> message
> >> >news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> >> >> Hi,
> >> >>
> >> >> I am performing a disaster recovery reharsal for SQL
> >> >> Server with various test cases on a Test Server. I
> want
> >> to
> >> >> corrupt the Master Database( without deleting
> the .ldf)
> >> >> Manually and then try to recover. Which is the best
> way
> >> to
> >> >> do this? . also Any resources on Disaster Recovery
> >> >> reharsals on SQL Servers are appreciated.
> >> >>
> >> >> Regards
> >> >>
> >> >> Chip
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||You can always change where SQL looks for the master.mdf file. That will
put you in a DR situation when you restart it. SQL will attempt to come
online and will not be able to start. It is also fixable by changing the
regkey back. I'd practice on a lab server until you are comfortable. USE
AT YOUR OWN RISK.
Christian Smith
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:e98501c3f154$c22ad640$a301280a@.phx.gbl...
> hi Tibor,
> Thanks for the response. what should i do to go it to
> suspect(without deleting .ldf) and how to cause a
> corruption. Please suggest both ways so that I can have
> two test cases in hand. :-)
> Sincere Regards
> Chip.
> >--Original Message--
> >Do you want it to go suspect or just cause a corruption
> in the master
> >database?
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> >> Hi,
> >>
> >> I am performing a disaster recovery reharsal for SQL
> >> Server with various test cases on a Test Server. I want
> to
> >> corrupt the Master Database( without deleting the .ldf)
> >> Manually and then try to recover. Which is the best way
> to
> >> do this? . also Any resources on Disaster Recovery
> >> reharsals on SQL Servers are appreciated.
> >>
> >> Regards
> >>
> >> Chip
> >
> >
> >.
> >

Disaster Recovery rehearsal

Disaster Recovery question

Ive been doing a bit of digging lately about Restoring the Master db to a
box with another name and Im a bit confused. Near as I can tell this action
isn't supported. At least not by people in these types of forums. My
Disaster Recovery pobbibilities are very limited @. the moment. I don't have
a spare server. Probably won't have one anytime soon. Yes, yes, Ive brought
this up to everyone but got nowhere. The reply I got was if the server dies
we would resotre from backup over to the Reporting box. So now my question.
I take backups of the Master, MSDB, and user db's regularly. They are put
onto tape. But, since Master cant be restored to a box with another name,
what good is the backup of it for someone like in my scenario? That being
said, how would I ever get back my logins/ passwords, etc. I know I can get
the jobs from MSDB, but not the logins. All ideas appreciated.
--
sql2k sp3
TIA, ChrisRYou can restore master to another box. Just keep in mind that if you don't
have your app DB's in the exact same folders, you will have a bunch of
suspect DB's. Here, you can do one of two things:
1) Drop the suspect DB's and simply restore from backup. IOW, you've
restored master and the other DB's don't even exist (physically) on your
server yet. When master is restored, it thinks they're there (since they're
in the sysdatabases table) and it then marks them as suspect. Dropping them
sets the record straight and you can just restore them at that point.
2) Restore the app databases first. Make sure they are in the exact same
folders as on your original server. Now, restore master and everything is
in synch.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
Ive been doing a bit of digging lately about Restoring the Master db to a
box with another name and Im a bit confused. Near as I can tell this action
isn't supported. At least not by people in these types of forums. My
Disaster Recovery pobbibilities are very limited @. the moment. I don't have
a spare server. Probably won't have one anytime soon. Yes, yes, Ive brought
this up to everyone but got nowhere. The reply I got was if the server dies
we would resotre from backup over to the Reporting box. So now my question.
I take backups of the Master, MSDB, and user db's regularly. They are put
onto tape. But, since Master cant be restored to a box with another name,
what good is the backup of it for someone like in my scenario? That being
said, how would I ever get back my logins/ passwords, etc. I know I can get
the jobs from MSDB, but not the logins. All ideas appreciated.
sql2k sp3
TIA, ChrisR|||Tom I appreciate your reply. To clarify, you are referring to a box with
another name, correct? Ive made several attempts at this and have yet to do
it successfully. I restore it fine, but then the service doesnt start and
doesnt report an error either. Says it can be an internal Windows problem.
All the KB articles I can find on moving db's makes no reference to whether
or not the box has the same name.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> You can restore master to another box. Just keep in mind that if you
don't
> have your app DB's in the exact same folders, you will have a bunch of
> suspect DB's. Here, you can do one of two things:
> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
> restored master and the other DB's don't even exist (physically) on your
> server yet. When master is restored, it thinks they're there (since
they're
> in the sysdatabases table) and it then marks them as suspect. Dropping
them
> sets the record straight and you can just restore them at that point.
> 2) Restore the app databases first. Make sure they are in the exact
same
> folders as on your original server. Now, restore master and everything is
> in synch.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> Ive been doing a bit of digging lately about Restoring the Master db to a
> box with another name and Im a bit confused. Near as I can tell this
action
> isn't supported. At least not by people in these types of forums. My
> Disaster Recovery pobbibilities are very limited @. the moment. I don't
have
> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
brought
> this up to everyone but got nowhere. The reply I got was if the server
dies
> we would resotre from backup over to the Reporting box. So now my
question.
> I take backups of the Master, MSDB, and user db's regularly. They are put
> onto tape. But, since Master cant be restored to a box with another name,
> what good is the backup of it for someone like in my scenario? That being
> said, how would I ever get back my logins/ passwords, etc. I know I can
get
> the jobs from MSDB, but not the logins. All ideas appreciated.
>
> --
> sql2k sp3
> TIA, ChrisR
>|||That's odd. The only thing I'd be doing with respect to the name is
sp_dropserver <old name> and sp_addserver <new name., 'local'.
Can you post the SQL Server error log of the dysfunctional server? Have you
tried starting the SQL Server service from the command prompt? Check out
sqlservr.exe in the BOL for the details.
BTW, I've had no problems in DR rehearsals restoring master to another box.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
Tom I appreciate your reply. To clarify, you are referring to a box with
another name, correct? Ive made several attempts at this and have yet to do
it successfully. I restore it fine, but then the service doesnt start and
doesnt report an error either. Says it can be an internal Windows problem.
All the KB articles I can find on moving db's makes no reference to whether
or not the box has the same name.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> You can restore master to another box. Just keep in mind that if you
don't
> have your app DB's in the exact same folders, you will have a bunch of
> suspect DB's. Here, you can do one of two things:
> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
> restored master and the other DB's don't even exist (physically) on your
> server yet. When master is restored, it thinks they're there (since
they're
> in the sysdatabases table) and it then marks them as suspect. Dropping
them
> sets the record straight and you can just restore them at that point.
> 2) Restore the app databases first. Make sure they are in the exact
same
> folders as on your original server. Now, restore master and everything is
> in synch.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> Ive been doing a bit of digging lately about Restoring the Master db to a
> box with another name and Im a bit confused. Near as I can tell this
action
> isn't supported. At least not by people in these types of forums. My
> Disaster Recovery pobbibilities are very limited @. the moment. I don't
have
> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
brought
> this up to everyone but got nowhere. The reply I got was if the server
dies
> we would resotre from backup over to the Reporting box. So now my
question.
> I take backups of the Master, MSDB, and user db's regularly. They are put
> onto tape. But, since Master cant be restored to a box with another name,
> what good is the backup of it for someone like in my scenario? That being
> said, how would I ever get back my logins/ passwords, etc. I know I can
get
> the jobs from MSDB, but not the logins. All ideas appreciated.
>
> --
> sql2k sp3
> TIA, ChrisR
>|||The name does not prevent SQL Server from starting. Having a different path does, though. Hunt for
error messages in the error log file and in the event log. This will show you the root of the
problem(s).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.NoEmails.com> wrote in message news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
> Tom I appreciate your reply. To clarify, you are referring to a box with
> another name, correct? Ive made several attempts at this and have yet to do
> it successfully. I restore it fine, but then the service doesnt start and
> doesnt report an error either. Says it can be an internal Windows problem.
> All the KB articles I can find on moving db's makes no reference to whether
> or not the box has the same name.
>
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
>> You can restore master to another box. Just keep in mind that if you
> don't
>> have your app DB's in the exact same folders, you will have a bunch of
>> suspect DB's. Here, you can do one of two things:
>> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
>> restored master and the other DB's don't even exist (physically) on your
>> server yet. When master is restored, it thinks they're there (since
> they're
>> in the sysdatabases table) and it then marks them as suspect. Dropping
> them
>> sets the record straight and you can just restore them at that point.
>> 2) Restore the app databases first. Make sure they are in the exact
> same
>> folders as on your original server. Now, restore master and everything is
>> in synch.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
>> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
>> Ive been doing a bit of digging lately about Restoring the Master db to a
>> box with another name and Im a bit confused. Near as I can tell this
> action
>> isn't supported. At least not by people in these types of forums. My
>> Disaster Recovery pobbibilities are very limited @. the moment. I don't
> have
>> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
> brought
>> this up to everyone but got nowhere. The reply I got was if the server
> dies
>> we would resotre from backup over to the Reporting box. So now my
> question.
>> I take backups of the Master, MSDB, and user db's regularly. They are put
>> onto tape. But, since Master cant be restored to a box with another name,
>> what good is the backup of it for someone like in my scenario? That being
>> said, how would I ever get back my logins/ passwords, etc. I know I can
> get
>> the jobs from MSDB, but not the logins. All ideas appreciated.
>>
>> --
>> sql2k sp3
>> TIA, ChrisR
>>
>|||> The name does not prevent SQL Server from starting. Having a different
path does, though
Bingo! The Master, Model, and MSDB files must all be in the same path as
they were on the original Server. That was the problem.
Tom and Tibor, thank you both!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e0HZ#J3uEHA.1264@.TK2MSFTNGP12.phx.gbl...
> The name does not prevent SQL Server from starting. Having a different
path does, though. Hunt for
> error messages in the error log file and in the event log. This will show
you the root of the
> problem(s).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
> > Tom I appreciate your reply. To clarify, you are referring to a box with
> > another name, correct? Ive made several attempts at this and have yet to
do
> > it successfully. I restore it fine, but then the service doesnt start
and
> > doesnt report an error either. Says it can be an internal Windows
problem.
> > All the KB articles I can find on moving db's makes no reference to
whether
> > or not the box has the same name.
> >
> >
> >
> >
> > "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> > news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> >> You can restore master to another box. Just keep in mind that if you
> > don't
> >> have your app DB's in the exact same folders, you will have a bunch of
> >> suspect DB's. Here, you can do one of two things:
> >>
> >> 1) Drop the suspect DB's and simply restore from backup. IOW,
you've
> >> restored master and the other DB's don't even exist (physically) on
your
> >> server yet. When master is restored, it thinks they're there (since
> > they're
> >> in the sysdatabases table) and it then marks them as suspect. Dropping
> > them
> >> sets the record straight and you can just restore them at that point.
> >>
> >> 2) Restore the app databases first. Make sure they are in the exact
> > same
> >> folders as on your original server. Now, restore master and everything
is
> >> in synch.
> >>
> >> --
> >> Tom
> >>
> >> ---
> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> >> SQL Server MVP
> >> Columnist, SQL Server Professional
> >> Toronto, ON Canada
> >> www.pinnaclepublishing.com
> >>
> >>
> >> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> >> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> >> Ive been doing a bit of digging lately about Restoring the Master db to
a
> >> box with another name and Im a bit confused. Near as I can tell this
> > action
> >> isn't supported. At least not by people in these types of forums. My
> >> Disaster Recovery pobbibilities are very limited @. the moment. I don't
> > have
> >> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
> > brought
> >> this up to everyone but got nowhere. The reply I got was if the server
> > dies
> >> we would resotre from backup over to the Reporting box. So now my
> > question.
> >> I take backups of the Master, MSDB, and user db's regularly. They are
put
> >> onto tape. But, since Master cant be restored to a box with another
name,
> >> what good is the backup of it for someone like in my scenario? That
being
> >> said, how would I ever get back my logins/ passwords, etc. I know I can
> > get
> >> the jobs from MSDB, but not the logins. All ideas appreciated.
> >>
> >>
> >> --
> >> sql2k sp3
> >>
> >> TIA, ChrisR
> >>
> >>
> >
> >
>

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

Disaster Recovery question

Ive been doing a bit of digging lately about Restoring the Master db to a
box with another name and Im a bit confused. Near as I can tell this action
isn't supported. At least not by people in these types of forums. My
Disaster Recovery pobbibilities are very limited @. the moment. I don't have
a spare server. Probably won't have one anytime soon. Yes, yes, Ive brought
this up to everyone but got nowhere. The reply I got was if the server dies
we would resotre from backup over to the Reporting box. So now my question.
I take backups of the Master, MSDB, and user db's regularly. They are put
onto tape. But, since Master cant be restored to a box with another name,
what good is the backup of it for someone like in my scenario? That being
said, how would I ever get back my logins/ passwords, etc. I know I can get
the jobs from MSDB, but not the logins. All ideas appreciated.
sql2k sp3
TIA, ChrisR
You can restore master to another box. Just keep in mind that if you don't
have your app DB's in the exact same folders, you will have a bunch of
suspect DB's. Here, you can do one of two things:
1) Drop the suspect DB's and simply restore from backup. IOW, you've
restored master and the other DB's don't even exist (physically) on your
server yet. When master is restored, it thinks they're there (since they're
in the sysdatabases table) and it then marks them as suspect. Dropping them
sets the record straight and you can just restore them at that point.
2) Restore the app databases first. Make sure they are in the exact same
folders as on your original server. Now, restore master and everything is
in synch.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
Ive been doing a bit of digging lately about Restoring the Master db to a
box with another name and Im a bit confused. Near as I can tell this action
isn't supported. At least not by people in these types of forums. My
Disaster Recovery pobbibilities are very limited @. the moment. I don't have
a spare server. Probably won't have one anytime soon. Yes, yes, Ive brought
this up to everyone but got nowhere. The reply I got was if the server dies
we would resotre from backup over to the Reporting box. So now my question.
I take backups of the Master, MSDB, and user db's regularly. They are put
onto tape. But, since Master cant be restored to a box with another name,
what good is the backup of it for someone like in my scenario? That being
said, how would I ever get back my logins/ passwords, etc. I know I can get
the jobs from MSDB, but not the logins. All ideas appreciated.
sql2k sp3
TIA, ChrisR
|||Tom I appreciate your reply. To clarify, you are referring to a box with
another name, correct? Ive made several attempts at this and have yet to do
it successfully. I restore it fine, but then the service doesnt start and
doesnt report an error either. Says it can be an internal Windows problem.
All the KB articles I can find on moving db's makes no reference to whether
or not the box has the same name.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> You can restore master to another box. Just keep in mind that if you
don't
> have your app DB's in the exact same folders, you will have a bunch of
> suspect DB's. Here, you can do one of two things:
> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
> restored master and the other DB's don't even exist (physically) on your
> server yet. When master is restored, it thinks they're there (since
they're
> in the sysdatabases table) and it then marks them as suspect. Dropping
them
> sets the record straight and you can just restore them at that point.
> 2) Restore the app databases first. Make sure they are in the exact
same
> folders as on your original server. Now, restore master and everything is
> in synch.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> Ive been doing a bit of digging lately about Restoring the Master db to a
> box with another name and Im a bit confused. Near as I can tell this
action
> isn't supported. At least not by people in these types of forums. My
> Disaster Recovery pobbibilities are very limited @. the moment. I don't
have
> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
brought
> this up to everyone but got nowhere. The reply I got was if the server
dies
> we would resotre from backup over to the Reporting box. So now my
question.
> I take backups of the Master, MSDB, and user db's regularly. They are put
> onto tape. But, since Master cant be restored to a box with another name,
> what good is the backup of it for someone like in my scenario? That being
> said, how would I ever get back my logins/ passwords, etc. I know I can
get
> the jobs from MSDB, but not the logins. All ideas appreciated.
>
> --
> sql2k sp3
> TIA, ChrisR
>
|||That's odd. The only thing I'd be doing with respect to the name is
sp_dropserver <old name> and sp_addserver <new name., 'local'.
Can you post the SQL Server error log of the dysfunctional server? Have you
tried starting the SQL Server service from the command prompt? Check out
sqlservr.exe in the BOL for the details.
BTW, I've had no problems in DR rehearsals restoring master to another box.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
Tom I appreciate your reply. To clarify, you are referring to a box with
another name, correct? Ive made several attempts at this and have yet to do
it successfully. I restore it fine, but then the service doesnt start and
doesnt report an error either. Says it can be an internal Windows problem.
All the KB articles I can find on moving db's makes no reference to whether
or not the box has the same name.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> You can restore master to another box. Just keep in mind that if you
don't
> have your app DB's in the exact same folders, you will have a bunch of
> suspect DB's. Here, you can do one of two things:
> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
> restored master and the other DB's don't even exist (physically) on your
> server yet. When master is restored, it thinks they're there (since
they're
> in the sysdatabases table) and it then marks them as suspect. Dropping
them
> sets the record straight and you can just restore them at that point.
> 2) Restore the app databases first. Make sure they are in the exact
same
> folders as on your original server. Now, restore master and everything is
> in synch.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> Ive been doing a bit of digging lately about Restoring the Master db to a
> box with another name and Im a bit confused. Near as I can tell this
action
> isn't supported. At least not by people in these types of forums. My
> Disaster Recovery pobbibilities are very limited @. the moment. I don't
have
> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
brought
> this up to everyone but got nowhere. The reply I got was if the server
dies
> we would resotre from backup over to the Reporting box. So now my
question.
> I take backups of the Master, MSDB, and user db's regularly. They are put
> onto tape. But, since Master cant be restored to a box with another name,
> what good is the backup of it for someone like in my scenario? That being
> said, how would I ever get back my logins/ passwords, etc. I know I can
get
> the jobs from MSDB, but not the logins. All ideas appreciated.
>
> --
> sql2k sp3
> TIA, ChrisR
>
|||The name does not prevent SQL Server from starting. Having a different path does, though. Hunt for
error messages in the error log file and in the event log. This will show you the root of the
problem(s).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.NoEmails.com> wrote in message news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
> Tom I appreciate your reply. To clarify, you are referring to a box with
> another name, correct? Ive made several attempts at this and have yet to do
> it successfully. I restore it fine, but then the service doesnt start and
> doesnt report an error either. Says it can be an internal Windows problem.
> All the KB articles I can find on moving db's makes no reference to whether
> or not the box has the same name.
>
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> don't
> they're
> them
> same
> action
> have
> brought
> dies
> question.
> get
>
|||> The name does not prevent SQL Server from starting. Having a different
path does, though
Bingo! The Master, Model, and MSDB files must all be in the same path as
they were on the original Server. That was the problem.
Tom and Tibor, thank you both!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e0HZ#J3uEHA.1264@.TK2MSFTNGP12.phx.gbl...
> The name does not prevent SQL Server from starting. Having a different
path does, though. Hunt for
> error messages in the error log file and in the event log. This will show
you the root of the
> problem(s).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
do[vbcol=seagreen]
and[vbcol=seagreen]
problem.[vbcol=seagreen]
whether[vbcol=seagreen]
you've[vbcol=seagreen]
your[vbcol=seagreen]
is[vbcol=seagreen]
a[vbcol=seagreen]
put[vbcol=seagreen]
name,[vbcol=seagreen]
being
>

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

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

Disaster Recovery question

Ive been doing a bit of digging lately about Restoring the Master db to a
box with another name and Im a bit confused. Near as I can tell this action
isn't supported. At least not by people in these types of forums. My
Disaster Recovery pobbibilities are very limited @. the moment. I don't have
a spare server. Probably won't have one anytime soon. Yes, yes, Ive brought
this up to everyone but got nowhere. The reply I got was if the server dies
we would resotre from backup over to the Reporting box. So now my question.
I take backups of the Master, MSDB, and user db's regularly. They are put
onto tape. But, since Master cant be restored to a box with another name,
what good is the backup of it for someone like in my scenario? That being
said, how would I ever get back my logins/ passwords, etc. I know I can get
the jobs from MSDB, but not the logins. All ideas appreciated.
sql2k sp3
TIA, ChrisRYou can restore master to another box. Just keep in mind that if you don't
have your app DB's in the exact same folders, you will have a bunch of
suspect DB's. Here, you can do one of two things:
1) Drop the suspect DB's and simply restore from backup. IOW, you've
restored master and the other DB's don't even exist (physically) on your
server yet. When master is restored, it thinks they're there (since they're
in the sysdatabases table) and it then marks them as suspect. Dropping them
sets the record straight and you can just restore them at that point.
2) Restore the app databases first. Make sure they are in the exact same
folders as on your original server. Now, restore master and everything is
in synch.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
Ive been doing a bit of digging lately about Restoring the Master db to a
box with another name and Im a bit confused. Near as I can tell this action
isn't supported. At least not by people in these types of forums. My
Disaster Recovery pobbibilities are very limited @. the moment. I don't have
a spare server. Probably won't have one anytime soon. Yes, yes, Ive brought
this up to everyone but got nowhere. The reply I got was if the server dies
we would resotre from backup over to the Reporting box. So now my question.
I take backups of the Master, MSDB, and user db's regularly. They are put
onto tape. But, since Master cant be restored to a box with another name,
what good is the backup of it for someone like in my scenario? That being
said, how would I ever get back my logins/ passwords, etc. I know I can get
the jobs from MSDB, but not the logins. All ideas appreciated.
sql2k sp3
TIA, ChrisR|||Tom I appreciate your reply. To clarify, you are referring to a box with
another name, correct? Ive made several attempts at this and have yet to do
it successfully. I restore it fine, but then the service doesnt start and
doesnt report an error either. Says it can be an internal Windows problem.
All the KB articles I can find on moving db's makes no reference to whether
or not the box has the same name.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> You can restore master to another box. Just keep in mind that if you
don't
> have your app DB's in the exact same folders, you will have a bunch of
> suspect DB's. Here, you can do one of two things:
> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
> restored master and the other DB's don't even exist (physically) on your
> server yet. When master is restored, it thinks they're there (since
they're
> in the sysdatabases table) and it then marks them as suspect. Dropping
them
> sets the record straight and you can just restore them at that point.
> 2) Restore the app databases first. Make sure they are in the exact
same
> folders as on your original server. Now, restore master and everything is
> in synch.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> Ive been doing a bit of digging lately about Restoring the Master db to a
> box with another name and Im a bit confused. Near as I can tell this
action
> isn't supported. At least not by people in these types of forums. My
> Disaster Recovery pobbibilities are very limited @. the moment. I don't
have
> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
brought
> this up to everyone but got nowhere. The reply I got was if the server
dies
> we would resotre from backup over to the Reporting box. So now my
question.
> I take backups of the Master, MSDB, and user db's regularly. They are put
> onto tape. But, since Master cant be restored to a box with another name,
> what good is the backup of it for someone like in my scenario? That being
> said, how would I ever get back my logins/ passwords, etc. I know I can
get
> the jobs from MSDB, but not the logins. All ideas appreciated.
>
> --
> sql2k sp3
> TIA, ChrisR
>|||That's odd. The only thing I'd be doing with respect to the name is
sp_dropserver <old name> and sp_addserver <new name., 'local'.
Can you post the SQL Server error log of the dysfunctional server? Have you
tried starting the SQL Server service from the command prompt? Check out
sqlservr.exe in the BOL for the details.
BTW, I've had no problems in DR rehearsals restoring master to another box.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
Tom I appreciate your reply. To clarify, you are referring to a box with
another name, correct? Ive made several attempts at this and have yet to do
it successfully. I restore it fine, but then the service doesnt start and
doesnt report an error either. Says it can be an internal Windows problem.
All the KB articles I can find on moving db's makes no reference to whether
or not the box has the same name.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> You can restore master to another box. Just keep in mind that if you
don't
> have your app DB's in the exact same folders, you will have a bunch of
> suspect DB's. Here, you can do one of two things:
> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
> restored master and the other DB's don't even exist (physically) on your
> server yet. When master is restored, it thinks they're there (since
they're
> in the sysdatabases table) and it then marks them as suspect. Dropping
them
> sets the record straight and you can just restore them at that point.
> 2) Restore the app databases first. Make sure they are in the exact
same
> folders as on your original server. Now, restore master and everything is
> in synch.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> Ive been doing a bit of digging lately about Restoring the Master db to a
> box with another name and Im a bit confused. Near as I can tell this
action
> isn't supported. At least not by people in these types of forums. My
> Disaster Recovery pobbibilities are very limited @. the moment. I don't
have
> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
brought
> this up to everyone but got nowhere. The reply I got was if the server
dies
> we would resotre from backup over to the Reporting box. So now my
question.
> I take backups of the Master, MSDB, and user db's regularly. They are put
> onto tape. But, since Master cant be restored to a box with another name,
> what good is the backup of it for someone like in my scenario? That being
> said, how would I ever get back my logins/ passwords, etc. I know I can
get
> the jobs from MSDB, but not the logins. All ideas appreciated.
>
> --
> sql2k sp3
> TIA, ChrisR
>|||The name does not prevent SQL Server from starting. Having a different path
does, though. Hunt for
error messages in the error log file and in the event log. This will show yo
u the root of the
problem(s).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.NoEmails.com> wrote in message news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl
..
> Tom I appreciate your reply. To clarify, you are referring to a box with
> another name, correct? Ive made several attempts at this and have yet to d
o
> it successfully. I restore it fine, but then the service doesnt start and
> doesnt report an error either. Says it can be an internal Windows problem.
> All the KB articles I can find on moving db's makes no reference to whethe
r
> or not the box has the same name.
>
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> don't
> they're
> them
> same
> action
> have
> brought
> dies
> question.
> get
>|||> The name does not prevent SQL Server from starting. Having a different
path does, though
Bingo! The Master, Model, and MSDB files must all be in the same path as
they were on the original Server. That was the problem.
Tom and Tibor, thank you both!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e0HZ#J3uEHA.1264@.TK2MSFTNGP12.phx.gbl...
> The name does not prevent SQL Server from starting. Having a different
path does, though. Hunt for
> error messages in the error log file and in the event log. This will show
you the root of the
> problem(s).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
do[vbcol=seagreen]
and[vbcol=seagreen]
problem.[vbcol=seagreen]
whether[vbcol=seagreen]
you've[vbcol=seagreen]
your[vbcol=seagreen]
is[vbcol=seagreen]
a[vbcol=seagreen]
put[vbcol=seagreen]
name,[vbcol=seagreen]
being[vbcol=seagreen]
>

Disaster Recovery Process - Cannot restore Master

Hello All,

I have a production SQL 2005 sp1 server running on Windows 2003. The SQL server was upgraded from SQL 2000.

In SQL 2000 our disaster recovery plan consisted of making daily backups of all system databases and user databases.

If we did have a system failure, we would copy those databases to a different physical server, Open SQL in single user mode and restore master.We would then restart the SQL service in normal mode and continue restoring the system databases then the user databases.

Now with SQL 2005, I am testing this process by attempting to restore all of the databases into our rebuild DEV server.I have SQL 2005 installed and patched to the same level as the production SQL server (9.0.2047).I can start SQL 2005 in single user mode, open SQL Server Management Studio, browse to master, right click master, click tasks ->restore ->Database.I choose “From Device” and add the BAK file from last nights backups.I select Master as the restore to database, put a check in the backup set to restore and press ok.Below is the error that I am getting:

“Restore failed for Server ‘SERVERNAME’ – System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing 'master' database. (Microsoft.SqlServer.Smo)

Do I have a real error, or am I going about the process incorrectly for SQL 2005?

Here is the SQL Script that my actions are producing:

RESTORE DATABASE [master] FROMDISK = N'D:\ProductionSQLBackupforDEV\ \MSSQL\BACKUP\master\master_backup_200605110020.bak' WITHFILE = 1,NOUNLOAD,STATS = 10

Also, all of our databases, system and user, are stored in a different directory than c:\program files\mssql……We have moved them to D:\directory.

If I need to re evaluate our “Backup” Procedures to be able to perform these actions please let me know.

Thank you for any assistance you can provide.

Keith

Does anyone have any ideas on this problem?

Can the master database from SQL2005 on server1 be restored to SQL2005 on server2?

If so, how do you do it?

If not, how do you recover from a disaster where you are forced to restore from backups?

Thank you,

Keith

|||

Did you try the WITH REPLACE option?

That should work.

|||

Thank you,

That was exactly what I was looking for.

Keith

Disaster Recovery Process - Cannot restore Master

Hello All,

I have a production SQL 2005 sp1 server running on Windows 2003. The SQL server was upgraded from SQL 2000.

In SQL 2000 our disaster recovery plan consisted of making daily backups of all system databases and user databases.

“Restore failed for Server ‘SERVERNAME’ – System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing 'master' database. (Microsoft.SqlServer.Smo)

Do I have a real error, or am I going about the process incorrectly for SQL 2005?

Here is the SQL Script that my actions are producing:

RESTORE DATABASE [master] FROMDISK = N'D:\ProductionSQLBackupforDEV\ \MSSQL\BACKUP\master\master_backup_200605110020.bak' WITHFILE = 1,NOUNLOAD,STATS = 10

Also, all of our databases, system and user, are stored in a different directory than c:\program files\mssql……We have moved them to D:\directory.

If I need to re evaluate our “Backup” Procedures to be able to perform these actions please let me know.

Thank you for any assistance you can provide.

Keith

Does anyone have any ideas on this problem?

Can the master database from SQL2005 on server1 be restored to SQL2005 on server2?

If so, how do you do it?

If not, how do you recover from a disaster where you are forced to restore from backups?

Thank you,

Keith

|||

Did you try the WITH REPLACE option?

That should work.

|||

Thank you,

That was exactly what I was looking for.

Keith

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

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

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

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
>

2012年2月19日星期日

disable publishing and distribution error

Ok, which database are you creating sysmergepublications and
sysmergesubscriptions in ?
I've created sysmergesubscriptions in distribution , master , msdb ...
I still receive an error when I run
use master
exec sp_dropdistributor @.no_checks = 1
go
I receive :
Msg 208, Level 16, State 1, Procedure sp_MSmergepublishdb, Line 103
Invalid object name 'dbo.sysmergesubscriptions'.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%233PUslE$GHA.896@.TK2MSFTNGP03.phx.gbl...
> create table sysmergepublications
> (
> publisher sysname,
> publisher_db sysname,
> name sysname,
> description nvarchar(510),
> retention int,
> publication_type tinyint,
> pubid uniqueidentifier,
> designmasterid uniqueidentifier,
> parentid uniqueidentifier,
> sync_mode tinyint,
> allow_push int,
> allow_pull int,
> allow_anonymous int,
> centralized_conflicts int,
> status tinyint,
> snapshot_ready tinyint,
> enabled_for_internet bit,
> dynamic_filters bit,
> snapshot_in_defaultfolder bit,
> alt_snapshot_folder nvarchar(510),
> pre_snapshot_script nvarchar(510),
> post_snapshot_script nvarchar(510),
> compress_snapshot bit,
> ftp_address sysname,
> ftp_port int,
> ftp_subdirectory nvarchar(510),
> ftp_login sysname,
> ftp_password nvarchar(1048),
> conflict_retention int,
> keep_before_values int,
> allow_subscription_copy bit,
> allow_synctoalternate bit,
> validate_subscriber_info nvarchar(1000),
> ad_guidname sysname,
> backward_comp_level int,
> max_concurrent_merge int,
> max_concurrent_dynamic_snapshots int,
> use_partition_groups smallint,
> dynamic_filters_function_list nvarchar(1000),
> partition_id_eval_proc sysname,
> publication_number smallint,
> replicate_ddl int,
> allow_subscriber_initiated_snapshot bit,
> distributor sysname,
> snapshot_jobid binary(16),
> allow_web_synchronization bit,
> web_synchronization_url nvarchar(1000),
> allow_partition_realignment bit,
> retention_period_unit tinyint,
> decentralized_conflicts int,
> generation_leveling_threshold int,
> automatic_reinitialization_policy bit
> )
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "John A Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
> news:%23exvteE$GHA.4196@.TK2MSFTNGP03.phx.gbl...
>
Publication database. Check which databases are published for merge
replication and put it there.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John A Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:uyEq9AQBHHA.4672@.TK2MSFTNGP02.phx.gbl...
> Ok, which database are you creating sysmergepublications and
> sysmergesubscriptions in ?
> I've created sysmergesubscriptions in distribution , master , msdb ...
> I still receive an error when I run
> use master
> exec sp_dropdistributor @.no_checks = 1
> go
> I receive :
> Msg 208, Level 16, State 1, Procedure sp_MSmergepublishdb, Line 103
> Invalid object name 'dbo.sysmergesubscriptions'.
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%233PUslE$GHA.896@.TK2MSFTNGP03.phx.gbl...
>
|||My database is no longer being published for replication because I used
exec sp_replicationdboption 'databasename','merge publish',false
Nonetheless, I added a dbo.sysmergesubscriptions table to this database and
ran
use master
exec sp_dropdistributor @.no_checks = 1
go
but I still receive the error :
Msg 208, Level 16, State 1, Procedure sp_MSmergepublishdb, Line 103
Invalid object name 'dbo.sysmergesubscriptions'.
Could it be because I need to add dbo.sysmergesubscriptions as a system
object ? How do I do this ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eZifFJQBHHA.2304@.TK2MSFTNGP02.phx.gbl...
> Publication database. Check which databases are published for merge
> replication and put it there.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "John A Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
> news:uyEq9AQBHHA.4672@.TK2MSFTNGP02.phx.gbl...
>
|||these are the lines around 103
if not exists (select * from dbo.sysmergesubscriptions
where UPPER(subscriber_server) =
UPPER(publishingservername()) and db_name = db_name() and subid <> pubid)
begin
select @.ignore_merge_metadata = 1
end
It is complaining about the database you are running the command in. Is the
table there? Does it have the owner dbo?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John A Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:ePkGbNQBHHA.1220@.TK2MSFTNGP04.phx.gbl...
> My database is no longer being published for replication because I used
> exec sp_replicationdboption 'databasename','merge publish',false
> Nonetheless, I added a dbo.sysmergesubscriptions table to this database
> and ran
> use master
> exec sp_dropdistributor @.no_checks = 1
> go
> but I still receive the error :
> Msg 208, Level 16, State 1, Procedure sp_MSmergepublishdb, Line 103
> Invalid object name 'dbo.sysmergesubscriptions'.
> Could it be because I need to add dbo.sysmergesubscriptions as a system
> object ? How do I do this ?
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eZifFJQBHHA.2304@.TK2MSFTNGP02.phx.gbl...
>

订阅：博文 (Atom)

2012年3月11日星期日

Disaster Recovery rehearsal

Disaster Recovery rehearsal

Disaster Recovery question

Disaster Recovery question

Disaster Recovery question

Disaster Recovery question

Disaster Recovery question

Disaster Recovery question

Disaster Recovery Process - Cannot restore Master

Disaster Recovery Process - Cannot restore Master

Disaster Recovery Plan

Disaster Recovery Plan

Disaster Recovery Plan

2012年3月8日星期四

Disaster Recovery

2012年2月19日星期日

disable publishing and distribution error

Display date

Blog Archive

About Me