SBS2003 server replication

I have an SBS2003 web server running IIS6 and SQL2000. My company wants a
secondary server that this server can replicate to so if anything happens to
it, we can just change a few router settings and the replication server can
take over. Ideally I want a second sbs2003 server with the same
domain\servername that Active Directory\IIS and SQL can replicate too. I'm
not too bother about SQL or IIS configurations yet, I just want o know if its
possible. I'm mostly bothered about AD at this point....are there any good
documents on replication AD in this way?

Pablo
Wed Jan 19 12:09:21 CST 2005

I don't think you can...

You can't add to SBS to the same Domain. All other replicas, I'm not
sure you can do them with Standar products.

PV


On Wed, 19 Jan 2005 09:31:05 -0800, "rich"
<rich@discussions.microsoft.com> wrote:

>I have an SBS2003 web server running IIS6 and SQL2000. My company wants a
>secondary server that this server can replicate to so if anything happens to
>it, we can just change a few router settings and the replication server can
>take over. Ideally I want a second sbs2003 server with the same
>domain\servername that Active Directory\IIS and SQL can replicate too. I'm
>not too bother about SQL or IIS configurations yet, I just want o know if its
>possible. I'm mostly bothered about AD at this point....are there any good
>documents on replication AD in this way?

Saludos,

Pablo Vernocchi
vernocchi@pcoffice.com.ar.delete.this
Buenos Aires, Argentina

SuperGumby
Wed Jan 19 15:24:42 CST 2005

there are ways of creating a 'failover' server.

We had one such system in place but after three years of operation with it
never being required the client took our advice and spent the budget buying
decent hardware again.

The failover system we put together was exactly the same hardware as the SBS
but no RAID and an additional drive (this one drive was IDE). The failover
system ran as a workstation on the network, located in a locked basement.
Each night at midnight Backup Exec copied the whole SBS drive to a drive
which appeared as a network share on the WS.

In the event of a SBS failure all someone had to do was shutdown the WS,
flick a switch to turn off the IDE drive, power up again.

Like I said, it was never required. Waste of time, money and effort. Put the
three into making your server more robust and you'll save on all three.

"rich" <rich@discussions.microsoft.com> wrote in message
news:E6C86DE8-C45A-45F3-90F6-C33D47EA987C@microsoft.com...
>I have an SBS2003 web server running IIS6 and SQL2000. My company wants a
> secondary server that this server can replicate to so if anything happens
> to
> it, we can just change a few router settings and the replication server
> can
> take over. Ideally I want a second sbs2003 server with the same
> domain\servername that Active Directory\IIS and SQL can replicate too. I'm
> not too bother about SQL or IIS configurations yet, I just want o know if
> its
> possible. I'm mostly bothered about AD at this point....are there any good
> documents on replication AD in this way?

rich
Wed Jan 19 17:53:02 CST 2005

thanks for the advice, my company definalty want this though, no way of
getting out of it really. Are there any decent links to describe in more
details what you had setup. Wouldn't sbs 2003 be picky about different serial
numbers on the hardware - the ones mircosoft use for activation?

"SuperGumby [SBS MVP]" wrote:

> there are ways of creating a 'failover' server.
>
> We had one such system in place but after three years of operation with it
> never being required the client took our advice and spent the budget buying
> decent hardware again.
>
> The failover system we put together was exactly the same hardware as the SBS
> but no RAID and an additional drive (this one drive was IDE). The failover
> system ran as a workstation on the network, located in a locked basement.
> Each night at midnight Backup Exec copied the whole SBS drive to a drive
> which appeared as a network share on the WS.
>
> In the event of a SBS failure all someone had to do was shutdown the WS,
> flick a switch to turn off the IDE drive, power up again.
>
> Like I said, it was never required. Waste of time, money and effort. Put the
> three into making your server more robust and you'll save on all three.
>
> "rich" <rich@discussions.microsoft.com> wrote in message
> news:E6C86DE8-C45A-45F3-90F6-C33D47EA987C@microsoft.com...
> >I have an SBS2003 web server running IIS6 and SQL2000. My company wants a
> > secondary server that this server can replicate to so if anything happens
> > to
> > it, we can just change a few router settings and the replication server
> > can
> > take over. Ideally I want a second sbs2003 server with the same
> > domain\servername that Active Directory\IIS and SQL can replicate too. I'm
> > not too bother about SQL or IIS configurations yet, I just want o know if
> > its
> > possible. I'm mostly bothered about AD at this point....are there any good
> > documents on replication AD in this way?
>
>
>

SuperGumby
Thu Jan 20 04:46:07 CST 2005

If you had a problem because the system didn't think it was activated you
would spend no more than 5 minutes on the phone explaining to 'activation'
'My server is _down_ , here are my license details, I'm falling back to a
copy of the server as of midnight last night, activate me, please.'

'OHHH, and when I repair my SBS and it wishes to be activated for similar
reason I'm gonna call up again.'



"rich" <rich@discussions.microsoft.com> wrote in message
news:D68F07D4-08E6-47EA-8DDF-A5C838C62E59@microsoft.com...
> thanks for the advice, my company definalty want this though, no way of
> getting out of it really. Are there any decent links to describe in more
> details what you had setup. Wouldn't sbs 2003 be picky about different
> serial
> numbers on the hardware - the ones mircosoft use for activation?
>
> "SuperGumby [SBS MVP]" wrote:
>
>> there are ways of creating a 'failover' server.
>>
>> We had one such system in place but after three years of operation with
>> it
>> never being required the client took our advice and spent the budget
>> buying
>> decent hardware again.
>>
>> The failover system we put together was exactly the same hardware as the
>> SBS
>> but no RAID and an additional drive (this one drive was IDE). The
>> failover
>> system ran as a workstation on the network, located in a locked basement.
>> Each night at midnight Backup Exec copied the whole SBS drive to a drive
>> which appeared as a network share on the WS.
>>
>> In the event of a SBS failure all someone had to do was shutdown the WS,
>> flick a switch to turn off the IDE drive, power up again.
>>
>> Like I said, it was never required. Waste of time, money and effort. Put
>> the
>> three into making your server more robust and you'll save on all three.
>>
>> "rich" <rich@discussions.microsoft.com> wrote in message
>> news:E6C86DE8-C45A-45F3-90F6-C33D47EA987C@microsoft.com...
>> >I have an SBS2003 web server running IIS6 and SQL2000. My company wants
>> >a
>> > secondary server that this server can replicate to so if anything
>> > happens
>> > to
>> > it, we can just change a few router settings and the replication server
>> > can
>> > take over. Ideally I want a second sbs2003 server with the same
>> > domain\servername that Active Directory\IIS and SQL can replicate too.
>> > I'm
>> > not too bother about SQL or IIS configurations yet, I just want o know
>> > if
>> > its
>> > possible. I'm mostly bothered about AD at this point....are there any
>> > good
>> > documents on replication AD in this way?
>>
>>
>>