This message was deleted.
# citrix-vad
s
This message was deleted.
s
I'd use this:
l
Do you want profiles for all users to exist in both locations? The replicate profile store info Steven linked above may work, but it does add time to logoff writing to the remote location.
j
when using the replicate profile, does UPM automatically pick up from this list the next path if the first one is not available? Thanks!
s
are the datacenters close? like would one datacenter be considered an extension of the first datacenter?
n
they are close. I was to configure one site and have it span the two data center. Latency between the two site is 4 ms. They have a 10 GB network connection.
i plan on using fslogix for them.
s
totally get the consolidation effort, makes sense. how are the other apps configured? Only out of 1 datacenter? or AppA is in datacenter1 and AppB is in datacenter2? Do the other teams use 1 datacenter as more of a passive/DR datacenter? If so, i'd follow suit.
i've seen a very similar case where 2 datacenters were so close. Everyone called it Datacenter 2, however, it really just became an extension of Datacenter 1. Single points of failure everywhere, on both sides. Just trying to have you avoid that or at least set the expectations for the manager/execs. If datacenter # goes down, what doesn't work?
n
thanks steve. So both data centers will be mirrors of each other. The same apps will be installed in datacenter 1 and 2. so if datacenter 1 goes down users can use the apps in datacenter 2.
there use to be documentation for on creating one site spanning multiple datacenter that would list the requirements, but i can't find that now...do any of you have a link? i need it for my RA doc and plus i want to review.
Hey guys
quick question
anyone know if citrix has what is stated in this link documented anywhere
my client is asking me for updated version of this
s
not sure if anyone else has hard 'citrix site' latency and bandwidth requirements, let me know if you find something there.
most of the recommendation around best practice would be sep citrix sites per datacenter. Again, just guidance.
it's a very complicated answer with tons of customer variables
maybe a good time to entertain citrix cloud too.
n
i reached out to citrix, and awaiting feedback
i just need like clear documentation as to why a seperate site should be created.
i found this...
Basically if you span to a citrix site to a secondary site you can't claim it as being as a DR site
you would need to create a seperate site as DR, technically
s
are you stretching the SQL cluster too?
j
when you use zones you can make it resilient. I did many DR testing in lab and it works.
n
yes, we stretching the SQL cluster too
hey guys
citrix came back with saying that the site can be stretched even though the two data centers are 150 miles a part.
they said they don't have any updated documentation on those recommendations but will update what they have
s
it's not miles, it's latency and bandwidth.
and when they say stretched are they talking about zones?
n
there use to be guidelines for distance as well.
s
hopefully you can get them to publish a new article...
n
i hope so...its worked before. i had them update guidelines on a few things.
....in the past
like the sql scripts to re-point the DDC to a new sql cluster