Re: Complete fail over - with little or no manual changes?

Tech-Archive recommends: Fix windows errors by optimizing your registry

I mentioned Storage Craft's Shadow Protect in my first reply, and was assuming the second server would be a clone of the first, with a second license.

Probably neither license should be OEM.

Still, downtime would be as much as 30 minutes while the last known snap shot was transferred.

Leythos did not say what the clients are, or what their method of connection would be. If RWW, the public dns servers would solve that problem. If an entirely new/different site, he may be envisioning a second set of workstations as well.

Leythos, can your offer more details on the need/intent?

--
Larry
"Cris Hanna (SBS-MVP)" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:%231DqgtLyIHA.2184@xxxxxxxxxxxxxxxxxxxxxxx
It still couldn't be SBS. Even with same internal name, etc. it would have a differnt SID so, work stations would have to be disjoined and joined to new SBS domain

For my 2 cents, StorageCraft images with Hardware independent restores, is probably the best we can hope for, or offsite secondary domain controller and extra Exchange server but that would cost more than Storage Craft and still would wanna get back to SBS eventually.

Guess it depends on acceptable downtime/costs/etc

Don't know much about hosted SBS services.

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues


"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@xxxxxxxxxxxxxxx> wrote in message news:044EF19B-EE16-4B12-81CD-26426017D7C4@xxxxxxxxxxxxxxxx
Thanks Cris, for the reminder about public DNS.

So we are reminded that MX and DNS records will not fall over automagically, but If the ISP(s) can do the job in a few minutes with a low TTL, it might still be possible to have a duplicate SBS at a different location on standby waiting for the DNS to be changed.

Yes? No?

Do we know if there are hosted SBS sites with multiple locations in different data centers that offer this kind of redundancy?

--
Larry

"Cris Hanna (SBS-MVP)" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:ecUo%23MLyIHA.5472@xxxxxxxxxxxxxxxxxxxxxxx
You really can't have automatic Failover with SBS
the SBS server has to hold all the FSMO roles....it is...master of its domain to coin a phrase, and there can only be one (sorry for the Highlander reference)

In addition to my activities with SBS, I have a full time enterprise IT job, administering a Time and attendance application which supports 300 plants in North America and nearly 30,000 hourly employees. Time Clocks are connected to time clock servers by IP address. In the event my clock servers in St Louis would fail, we have a DR location in Chicago, with identical servers. But our wan guys would have to re-route the subnet to Chicago, and we would change the IPs on the two clock servers. You can't do that automagically. Same with my app servers. My application is web based and accessed by a URL. If my app/hardware crashed in St Louis. Our DNS guys would have to modify the DNS A records to point to the DR hardware in Chicago. But I do have multiple app servers in St Louis in a clustered environment...if you are in a session and that app server goes down, you are "automatically" failed over to another app server and session persistence is maintained.

Back to your question, you can have a second domain controller and even a second Exchange Server at an alternate location. You could even have file replication. Assuming the vpn connection were still up between the main location and the backup location, users could still logon, and you could have mail coming into the other Exchange server via a second MX record.

Hope that helps


--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues


"Leythos" <void@xxxxxxxxxxx> wrote in message news:MPG.22b3691d1f9d0d7f9898e5@xxxxxxxxxxxxxxxxxxxx
Anyone setup a completely, automatic, fail over of SBS from one site to
an alternative site?

I can get the T1 circuits to port to the recovery site, but I've not
seen anything that duplicates ALL settings/data from one server to
another, real time....

Thanks.


--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@xxxxxxxxxx (remove 999 for proper email address)

Relevant Pages

  • Re: SBS 2003 Licensing and Virtualization
    ... MS do not give a stuff about you proving your Disaster Recovery Strategy by having a second instance of any of their products running AS LONG AS the intent is proof of your DRS, the system is only active as long as necessary to prove this and does not supply services to clients. ... MS _want_ you to prove your DRS works, and should you need to do so and tell MS about it they will likely ask if they can make you a 'case study', proving that recovery of Windows Server Systems works. ... Currently we are running SBS 2003 on a physical server with 5 CAL's. ... You would need a second license to run two instances concurrently. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connection Between 2 SBS Servers in Different Locations
    ... I think his reference was to having SBS Server / Member Server so all users would have the Same Exchange Organization. ... Microsoft MVPs ... Why wouldn't you just set up a SharePoint site on each server, and create a HOUSTON user on the server in Dallas and a DALLAS user on the server in Houston. ...
    (microsoft.public.windows.server.sbs)
  • Re: DFS replication between Windows Sever 2003 R2 & SBS
    ... Microsoft MVPs ... SBS 2003 does not support trusts with another domain. ... So if you want DFS-R to work, you'd need another Windows Server 2003 R2 std server in your SBS domain and then the other server would have to belong to the SBS domain. ... is the DFS replication possible and enough for us? ...
    (microsoft.public.windows.server.sbs)
  • Re: DFS replication between Windows Sever 2003 R2 & SBS
    ... Microsoft MVPs ... SBS 2003 does not support trusts with another domain. ... So if you want DFS-R to work, you'd need another Windows Server 2003 R2 std server in your SBS domain and then the other server would have to belong to the SBS domain. ... is the DFS replication possible and enough for us? ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal server trial
    ... Microsoft MVPs ... We wanted to test out terminal server using the 180 day trial of Server ... member server PC running TS with our SBS R1 platform. ... Any "SBS world" ideas on the hardware required for TS? ...
    (microsoft.public.windows.server.sbs)