Re: DR procedure per smallbizserver.net

Hi Marina,

I have read and re-read and re-read the documents. I am talking about your
two seperate documents. the one document is called "How to backup and
restore your SBS server" - specifically the Disaster Restore of your server
document. The second document is entitled "How do I move my server to new
hardware" and this one deals with the issue of placeholders and loopback
adaptors.

My question is how do thse two documents integrate with one another, ie in
the case of a full Disaster recovery, at what point do I do "insert" the
process for installing loopback adaptors as placeholders etc into the DR
document?

Thanks once again for your time and patience.

Kind regards,

Andrew


"Marina Roos [SBS-MVP]" <marina@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OAYRYcBWFHA.3216@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Andrew,
>
> Did you actually read the document on the site? It does mention to install
> loopback adapters, to disable the old nics, to configure the loopback
> adapter, than change the mobo, boot in dr mode and install the new nic
> drivers etcetera. If you are not able to do the loopback part before
> changing the mobo, you will always end up with a boot in dr mode (as that
> is
> the quickest) and have to remove the old adapters and install the new
> adapters.
>
> --
> Regards,
>
> Marina Roos
> Microsoft SBS-MVP
> One of the Magical M&M's
> www.smallbizserver.net
> Take part in SBS forum:
> http://www.smallbizserver.net/Default.aspx?tabid=53
>
> "Andrew Gericke" <amgerick@xxxxxxxxxx> schreef in bericht
> news:uVRJG4AWFHA.2740@xxxxxxxxxxxxxxxxxxxxxxx
>> Thanks Marina,
>>
>> Am I then understanding that where the NIC's are different in the new
>> server, a DR is not actually possible? Or is there a way in safe mode of
>> adding back the LAN Network connection, the TCP/IP services and bindings
>> manually?
>>
>> My apologies for the probably stupid questions, but I really want to
>> fully
>> understand this whole DR scenario, and be 100% prepared for next time
> (hope
>> it never happens tho).
>>
>> Thanks and kind regards,
>>
>> Andrew
>>
>> "Marina Roos [SBS-MVP]" <marina@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message
>> news:%2386uxtAWFHA.2420@xxxxxxxxxxxxxxxxxxxxxxx
>> > Hi Andrew,
>> >
>> > If you haven't been able to use the loopback method, there is no way of
>> > transferring the config of the nics.
>> >
>> > --
>> > Regards,
>> >
>> > Marina Roos
>> > Microsoft SBS-MVP
>> > One of the Magical M&M's
>> > www.smallbizserver.net
>> > Take part in SBS forum:
>> > http://www.smallbizserver.net/Default.aspx?tabid=53
>> >
>> > "Andrew Gericke" <amgerick@xxxxxxxxxx> schreef in bericht
>> > news:O0rXIbAWFHA.3840@xxxxxxxxxxxxxxxxxxxxxxx
>> >> ok this all seems to link in to the fact that the hardware is
> different,
>> >> particularly the NIC's. So now my question becomes one of, how do you
> do
>> >> a
>> >> DR when the NIC's in particular are a different make etc, and where
>> > because
>> >> of the complete failure of the "old" server one would not have had the
>> >> opportunity to install loopback adaptors to hold the NIC settings. So
> now
>> >> after booting into safe mode after the DR, it installs the new drivers
>> >> for
>> >> the new NIC's but hides the old NIC's. Fine, one can remove the old
> nics
>> > by
>> >> following the Magical M&M's article on this topic, but how do you
> migrate
>> >> the config and bindings of the old nic's to the new?
>> >>
>> >> Thanks
>> >>
>> >> Andrew
>> >> "Andrew Gericke" <amgerick@xxxxxxxxxx> wrote in message
>> >> news:e7GRQDAWFHA.3532@xxxxxxxxxxxxxxxxxxxxxxx
>> >> > Hi,
>> >> >
>> >> > Just found something else, and very relevant to the problem, but do
> not
>> >> > know how to resolve it.
>> >> >
>> >> > While the NIC is visible under device manager, under "Network
>> > Connections"
>> >> > of control panel, there is nothing, not a single entry, and if I
> select
>> >> > Advanced... Advanced Settings, there is nothing either. Obviously
> since
>> > I
>> >> > no longer have a Local Area Connection, this is what is causing the
>> >> > huge
>> >> > speed/logon problem on booting to normal mode. How do I recreate the
>> > Local
>> >> > Area connection?
>> >> >
>> >> > Thanks
>> >> >
>> >> > Andrew
>> >> >
>> >> >
>> >> > "Andrew Gericke" <amgerick@xxxxxxxxxx> wrote in message
>> >> > news:uhZ$YJ%23VFHA.2928@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >> Hi Marina
>> >> >>
>> >> >> Thanks for that email. I am sure your advice is 100% correct here.
>> > After
>> >> >> approximately 8 hours, the server logon screen has now appeared and
> I
>> > can
>> >> >> type in the password etc. However, if I look at device manager
>> >> >> (admittedly, I must have missed this the first time around and
>> >> >> didnt
>> >> >> check device manager as such, only allowed the system to install
>> >> >> all
>> > the
>> >> >> new device drivers, being new hardware), the current and new NIC is
>> >> >> listed as "Intel.... Network Connection #2".
>> >> >>
>> >> >> I suspect thus that the system still thinks there is another
>> >> >> network
>> >> >> connection somewhere, and has all the bindings messed up. Since the
>> >> >> old
>> >> >> NIC is not in this test server, the control panel is not now
>> >> >> showing
>> >> >> Network connection #1. How can I find this hidden device, remove it
>> >> >> and
>> >> >> fix all the bindings?
>> >> >>
>> >> >> Any advice much appreciated.
>> >> >>
>> >> >> Kind regards,
>> >> >>
>> >> >> Andrew
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Marina Roos [SBS-MVP]" <marina@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> >> >> in
>> >> >> message news:%23QgEza6VFHA.2684@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >>> Hi Andrew,
>> >> >>>
>> >> >>> Did you read that article completely? Did you check device
> management
>> >> >>> after
>> >> >>> the first boot, checked for hidden devices, checked the network
>> >> >>> config
>> >> >>> etcetera? When booting takes such a long time, it almost always
>> >> >>> points
>> >> >>> to
>> >> >>> the network settings that got messed up a bit.
>> >> >>>
>> >> >>> --
>> >> >>> Regards,
>> >> >>>
>> >> >>> Marina Roos
>> >> >>> Microsoft SBS-MVP
>> >> >>> One of the Magical M&M's
>> >> >>> www.smallbizserver.net
>> >> >>> Take part in SBS forum:
>> >> >>> http://www.smallbizserver.net/Default.aspx?tabid=53
>> >> >>>
>> >> >>> "Andrew Gericke" <amgerick@xxxxxxxxxx> schreef in bericht
>> >> >>> news:OXUO1Y4VFHA.1148@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >>>> Hi
>> >> >>>>
>> >> >>>> We recently lost the system partition off the drive of our
> SBS2003.
>> >> >>>> Fortunately we were able to recover the partition using a
> partition
>> >> >>> utility
>> >> >>>> app. However, before we did we tried to do a restore from our
>> >> >>>> backups
>> >> >>>> (having used ArcServe exclusively up to that point), but
>> >> >>>> concluded
>> > that
>> >> >>>> because of our method of backup we were completely ill prepared
> for
>> >> >>>> a
>> >> >>>> DR
>> >> >>>> situation.
>> >> >>>>
>> >> >>>> I have in the last two days decided to follow the backup and DR
>> >> >>>> procedure
>> >> >>>> from the smallbizserver.net website. The whole DR seems to have
>> > worked
>> >> >>> fine,
>> >> >>>> right up to the last sentence. The last sentence says that the
>> > machine
>> >> >>> might
>> >> >>>> take some time to come up after booting to normal mode the first
>> >> >>>> time
>> >> >>> (this
>> >> >>>> after first booting to safe mode to allow the installation of all
>> >> >>>> the
>> >> >>>> new
>> >> >>>> device drivers - new hardware for this test). Fine, I allowed the
>> >> >>>> machine
>> >> >>> to
>> >> >>>> just sit on the dialoge "preparing network connections" through
> the
>> >> >>>> night,
>> >> >>>> and sure enough, trhis morning I was on the logon screen. however
>> > after
>> >> >>>> logging on I noticed from services that the Exchange store and
>> > various
>> >> >>> other
>> >> >>>> services had not started. So I figured I would just do another
>> > reboot.
>> >> >>>> Now
>> >> >>> I
>> >> >>>> am sitting with the "preparing network connections" message on
>> >> >>>> the
>> >> >>>> screen
>> >> >>>> again, and it has been there for the last hour. What am I doing
>> > wrong,
>> >> >>> since
>> >> >>>> I can't imagine that everytime I reboot I have to wait 3 or 4
> hours
>> >> >>>> before
>> >> >>> I
>> >> >>>> can logon after doing a DR?
>> >> >>>>
>> >> >>>> Also, the procedure for the DR says "do not select the hive
>> > containing
>> >> >>>> you
>> >> >>>> exchange server backup". When does the exchange store (priv and
> pub)
>> >> >>>> get
>> >> >>>> restored then? Do I still need to go and do a restore of the
> store's
>> >> >>>> once
>> >> >>> I
>> >> >>>> get this machine to boot, or has that happened through the file
>> > restore
>> >> >>>> process?
>> >> >>>>
>> >> >>>> Thanks for the help
>> >> >>>>
>> >> >>>> Andrew
>> >> >>>>
>> >> >>>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>


.

Relevant Pages

  • Re: DR procedure per smallbizserver.net
    ... It does mention to install ... loopback adapters, to disable the old nics, to configure the loopback ... >> transferring the config of the nics. ...
    (microsoft.public.windows.server.sbs)
  • Re: Replace LAN NIC on SBS 2003 R2
    ... Loopback really doesn't save anything, ... and don't forget to run the CEICW when you're done. ... remove the NICs, if you can, or disable them in the BIOS if they're built in. ... Disabling the on-board nics in BIOS is optional, ...
    (microsoft.public.windows.server.sbs)
  • Re: From 2 NICs to 1
    ... in there checking device manager. ... I had lost both NICs a few weeks back ... If it's the external I'd just uninstall it, shutdown, install the new. ... configure loopback to same IP as real. ...
    (microsoft.public.windows.server.sbs)
  • Re: whoops - two new NICs
    ... "Steve LLG" schreef in bericht ... >> You will need more reboots as you will want to take those 2 old nics out ... Work the loopback way. ... >> Microsoft SBS-MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: Current IP is 127.0
    ... Paul G. Tobey [eMVP] wrote: ... but I don't feel like that sequence is what I'd ... Sure there can be more adapters, but in this case there's only one ... so the current IP shouldn't be the loopback device. ...
    (microsoft.public.dotnet.framework.compactframework)
Loading