Re: TS disaster recovery / split site scenario
- From: "Frankster" <Frank@xxxxxxxxxxxxxx>
- Date: Mon, 12 Jun 2006 06:54:49 -0600
The only thing I would say is that, with TS, usually you do not store data
on a TS, but instead use file servers to store data. TSs are normally simply
"workstation" boxes (at least "workstation" sessions). I've never worried
about any disaster recovery on a TS other than being able to build a new one
quickly.
-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
.
- Follow-Ups:
- Re: TS disaster recovery / split site scenario
- From: daveberm
- Re: TS disaster recovery / split site scenario
- Prev by Date: Re: Users can Install on Terminal Servers
- Next by Date: Re: Cross Session Printer Security
- Previous by thread: Warning when printing to networkprinter
- Next by thread: Re: TS disaster recovery / split site scenario
- Index(es):
Relevant Pages
|
Loading