Re: TS disaster recovery / split site scenario
- From: "Frankster" <Frank@xxxxxxxxxxxxxx>
- Date: Tue, 13 Jun 2006 08:01:34 -0600
Mike, it might help if you are more clearly what you mean by disaster
recovery. Disaster recovery is different from High Availability and is
different from Backup/Restore.
Multiple TSs with load balancing is great for High Availability, but does
nothing for disaster recovery or backup/restore.
-Frank
"Mike K" <MikeK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D9D3B7CC-639F-4C81-A3C8-D33DEB31630F@xxxxxxxxxxxxxxxx
Hi all,
I'm currently implementing a full disaster recovery solution for a client.
They have multiple servers running the usual stuff - exchange / sql etc.
The idea is to run active / passive clustering using a clever product
called
neverfail. This is fine for exchange & Sql but they don't have a solution
for Terminal Services.
My plan is to run a load balanced TS configuration. One TS will be on the
main site with another TS running at the branch office.
Is this something that any else has an experience with ?
Or, are there better ways around this issue?
Many thanks in advance for any help.
Mike
.
- Prev by Date: TS won't work after reboot
- Next by Date: Re: User customization in TS
- Previous by thread: Re: TS disaster recovery / split site scenario
- Next by thread: Re: Automatically start on Application on a Remote desktop connection.
- Index(es):
Relevant Pages
|
