[THIN] Re: zone design

  • From: "Ron Oglesby" <roglesby@xxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Mon, 10 May 2004 08:30:26 -0500

Well 3.0 will change zone design some.  It really depends on network
connectivity etc. 

One thing I would look at would be having 3 primary sites/zones, then have a
DR site/zone or two. Then set up your primary and backup zones using the DR
site as a location for DR servers/apps for all of your sites. 

OR another option is to create a "DR Circle" use Site B to backup Site A,
Site C is the Back up to B etc. etc. Even then you still have ONE zone per
site. And in the zone preferences for the users just use their primary and
someone else's primary as their secondary. Of course this requires that each
production location be overbuilt to handle the load during DR (2x number of
servers assuming 100% capacity).  Where the one DR site for all three prod
sites requires less total servers (generally 30-40%) if you can make the
assumption that only one site would need the DR at a time. (this of course
depends on their geographical locations)

I love DR planning. It's the bomb. :-D

Ron Oglesby
Senior Technical Architect
Microsoft MVP - Windows Server
 
RapidApp, Chicago
Mobile 815 325-7618
Office 312 372-7188
e-mail roglesby@xxxxxxxxxxxx
 
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Lilley, Brian
Sent: Monday, May 10, 2004 6:10 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] zone design

Hello all,

Here are my thoughts on zone design for global MPS3 farm.. any comments
appreciated.

Farm is made up of three regional zones - A, B and C.  Each regional zone
has
a hot-site DR zone Aa, Bb, Cc.

The DR hot sites are well connected through low latency fibre connections.
WAN links between regional sites are low latency ATM.

My initial thoughts were that the Citrix policy would ensure 

1. Each regional set of users would have their primary zone pointing to
their
local regional zone
2. If user in another regions zone, then they would point to the local
regional zone, assuming these servers support same apps and have local
access
to users data
3. If the preferred zone has died for either of the above zone preferences,
I
guess it should failover to either the lowest latency 'best' connected
regional site using the 'follow the sun idea', or, it should failover to the
local DR site.  I guess this decision is based on what is actually available
in the DR site compared to what is available in the other regions??

Is there any benefit in have a global 'backup' zone which had a presence in
each of the regional offices and the DR sites? hhmmm...

TIA, Brian

============================================================================
==
This message is for the sole use of the intended recipient. If you received
this message in error please delete it and notify us. If this message was
misdirected, CSFB does not waive any confidentiality or privilege. CSFB
retains and monitors electronic communications sent through its network.
Instructions transmitted over this system are not binding on CSFB until they
are confirmed by us. Message transmission is not guaranteed to be secure.
============================================================================
==

********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm

********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm

Other related posts: