Re: Windows 2003 recovery

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Antonis:

With two licensed copies of SBS, hopefully of the same edition, you can have a "cold spare". Unfortunately there is no way to set them on the same wires with the same AD structure. SBS will not allow this.

Further, you can't "move the license" if it is OEM, and meet the terms of the license so a backup from server_old and a restore to server_new would be a violation, if server_old is OEM. (Although I don't think MS would send you to jail over this. Sorry Mr. Software policeman, I guess I put in the "wrong" one of these two license numbers... I won't let it happen again.)

So, you can do a swing migration (www.sbsmigration) of the AD to the new box, new license, OR an image and hardware independent restore OR SBS backup restore to the new box (license permitting) to get your current "snapshot" over, but it will be a pain to keep it current.

Better to do it, test it, make sure it works, and then practice it however often you feel comfortable, keeping the second machine available, but preferably off site. Machine failure is not the only disaster you may need to recover from.

There is a commercial product that you might consider: I make no recommendation, as I have no knowledge:

http://www.doubletake.com/english/products/sbs-solutions/Pages/default.aspx

-Larry



"Antonis" <Antonis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:514797ED-326E-46D6-A0E5-89621C24E91E@xxxxxxxxxxxxxxxx
Currently my company is running with a small business server 2003 on an old
machine. There are group polices, active directory, sql servers, antivirus
servers and other on it. There is also an unused different hardware machine
with windows 2003 small business server. My question is: is there a way when
in hardware failure of the one to have the other pick up the pieces? How can
I have them synchronized all the time? What happens with ip address, domain
name etc when they are on the same network?

.

Relevant Pages

  • Re: OEM licencing and virtualization
    ... If you are running the OEM SBS on the hardware the OEM license was attached ... SBS as a webserver, you're freakin crazy. ...
    (microsoft.public.windows.server.sbs)
  • Re: Which X server?
    ... aware of the prevalence of different X servers. ... Depends on the hardware, if you have really old hardware that don't have ... Puppy uses Xorg version of X Windows System, ... license, Xorg is based on a version before the change of license, and is ...
    (alt.os.linux)
  • Re: SBS 2003 Licensing questions (long)...
    ... When you install SBS, you DEFINITELY need a license key! ... It's also dated July 2005 Servers Windows Servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connection monitor versus licenses
    ... What you might be seeing on the licensing node of standard management is the maximum number of users that SBS has seen connected, ... That isn't there to indicate how many CALs you can purchase. ... There is however another server product, called Windows Server for Small Business Server, which SBS is built upon. ... Some products have only "user" licensing; each user must have a license. ...
    (microsoft.public.windows.server.sbs)
  • Re: Transfer SBS 2003 License
    ... I have an aged SBS 2003 R2 Standard server that needs to be trashed ... hardware to another hardware? ... If it is a retail or volume license purchase, then just install on the new ...
    (microsoft.public.windows.server.sbs)