Re: Need help on NLB for streaming
From: Mark (anonymous_at_discussions.microsoft.com)
Date: 03/30/04
- Next message: Shon Shah [MSFT]: "Re: Event logs not replicating"
- Previous message: Mark: "NLB server 2003 content maintenance?"
- In reply to: Chris Darling [MSFT]: "Re: Need help on NLB for streaming"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 30 Mar 2004 14:38:35 -0800
Why not setup your splash page with a image map or a drop
down so users can select their location. That way the
user is automatically directed to the "nearest" streaming
server site. You could still use round-robin DNS and
place the same welcome page at all sites. Keep NLB site
specific. Don't try to accomplish that over large
geographical locations.
Another option is to use Akamai's streaming services.
That would saave you the hassle of having to manage all of
your streaming locations.
Peace,
Mark
>-----Original Message-----
>Hi Ernie,
>
>It sounds like you can get a big benefit by using DNS
round-robin (do an
>Internet search of the term for more information) to
split the load between
>your two sites. You enter both server IP addresses in DNS
for the same DNS
>name. DNS servers will then hand out IP addresses to
clients by looping
>through the list. The down side to this technique is that
when a server is
>taken offline, customers are still directed to it.
Furthermore, changes to
>the DNS records can take a long time to propagate to your
customers. The
>bottom line is that you need to be vigilent in keeping
these hosts online.
>
>Another technique would be to have users consult a web
page to select the
>server location they want to use. They can choose the one
geographically
>closest to them. If the connection attempt fails then
they can try the
>other.
>
>If your site grows to the point that you have multiple
hosts at the same
>location, then consider using load-balancing solutions
such as NLB to
>address the downtime issue. With load-balancing you can
remove hosts from
>the cluster and the remaining hosts take up the load. You
would still use
>DNS round-robin, but now you would round-robin between
clusters instead of
>individual hosts.
>
>I hope this helps...
>
>Cheers,
>Chris
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"ErnieG" <anonymous@discussions.microsoft.com> wrote in
message
>news:815888E7-0E48-4BE5-8D15-3408F6201C18@microsoft.com...
>> Thank you Chris for your input, let me give you a more
detail of what we
>> do. We are a religious entity that every other day
conduct a series of
>> video conference, these are internal conferences and
are controlled by the
>> System Administrator (me) but since we're growin and
have a branch on
>> almost in every place of the world, our internet line
can't hold such high
>> bandwith demand (only 2Mbs U/L 4Mb D/L). The idea came
after reading about
>> NLB, one of our branches in the Caribbean aquired a
server in order to
>> help us with the demand, so the idea was, when a client
request access to
>> the US server, it will be redirected to the one in the
Caribbean and so
>> forth - distributing the access between the 2 servers
and eventually into
>> more as we install them. The point is not a failover,
but more as of a
>> relief to the server since we don't have the means of
adding a dedicated
>> T3 line. Thank you for your time.
>>
>> ----- Chris Darling [MSFT] wrote: -----
>>
>> Hi Ernie,
>>
>> NLB exposes a single IP address with load from end-
users shared across
>> the
>> hosts. This is called a LAN-based solution (local
area network), and
>> the
>> machines must be homed to the same subnet for them
to form a cluster.
>> As a
>> result you can't form an NLB cluster of two servers
as you've
>> outlined; that
>> would be a WAN-based solution (wide are network).
There are some WAN
>> solutions in the marketplace, but Microsoft doesn't
not have such an
>> offering. They are quite expensive ($US 30000+) and
operate by sharing
>> a DNS
>> name rather than an IP address.
>>
>> My advice is to reexamine your orginal requirements
and look for a
>> creative
>> way to address them. What led you down the path of
choosing a
>> geographically
>> dispersed cluster? Is this for failover or do you
really need the
>> sites to
>> be load-balanced? Who are your customers? If they
are internal to your
>> organization you might be able to get away with a
DNS name change
>> instead of
>> a WAN load-balancing solution. Or perhaps you can
just use DNS
>> round-robin
>> to get you close enough to meeting your
requirements.
>>
>> If you provide more detail on what you are trying
to accomplish I can
>> give
>> you feedback.
>>
>> Cheers,
>> Chris
>>
>> --
>> This posting is provided "AS IS" with no
warranties, and confers no
>> rights.
>>
>>
>> "ErnieG" <anonymous@discussions.microsoft.com>
wrote in message
>> news:150C7F4E-E185-4286-95B2-
7A0728AFD00D@microsoft.com...
>> > Hi all, I have two WinServer 2003 servers, one in
the US and one in
>> the
>> > Caribbean, I want to NLB the two of them for
streaming with
>> possiblities
>> > on adding more servers to the NLB, How can this
be done? I'm new in
>> this,
>> > so any light that you can throw this way will be
really helpfull.
>>
>>
>>
>
>
>.
>
- Next message: Shon Shah [MSFT]: "Re: Event logs not replicating"
- Previous message: Mark: "NLB server 2003 content maintenance?"
- In reply to: Chris Darling [MSFT]: "Re: Need help on NLB for streaming"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
