Publishing point failover

Publishing point failover

Post by LURDL » Thu, 06 Jan 2005 07:31:09


What options are there (besides Windows Clustering) in handling publishing
point failures? If I have two streaming servers, one a backup of the first,
is there a way to have an automatic failover when one server (or stream) dies
without implementing Windows Clustering?

Windows Clustering looks like it can handle this, but I don't want to deal
with the added complexity (more hardware, Active Directory, etc.)
 
 
 

Publishing point failover

Post by Ravi Rama » Thu, 06 Jan 2005 07:42:49

Is this what you are looking for?
http://www.yqcomputer.com/
url=/library/en-
us/wmplay10/mmp_sdk/urlandserverrollover.asp

Thx,
Ravi

handling publishing
backup of the first,
server (or stream) dies
don't want to deal
Directory, etc.)

 
 
 

Publishing point failover

Post by LURDL » Thu, 06 Jan 2005 08:45:02

Not quite. My scenario is that I'm sending unicast from media server to
media server, not media server to media player. So I need to make sure that
if a publishing point or server fails, the receiving server can still get the
streams from an alternate location, preferably without interruption.
 
 
 

Publishing point failover

Post by LURDL » Fri, 07 Jan 2005 02:21:10

That looks like it could definitely help, at least with our server-to-server
unicast streams. Thanks.

In the case of multicasting to Media Player, I'm not sure if this would do
anything since we're dealing with .nsc files and not publishing points per
se. If a multicast stream stops, can the player automatically resume from a
secondary server?
 
 
 

Publishing point failover

Post by LURDL » Sat, 08 Jan 2005 09:23:06

uess it's worth testing.

One thing I did notice with the unicast setup is that if one source fails,
the other automatically takes over, but if BOTH sources fail, the publishing
point stops streaming and doesn't automatically recover when a source comes
back online. Is there a way to fix this behavior?

"Ravi Raman" wrote:

 
 
 

Publishing point failover

Post by RmVsaX » Wed, 16 Feb 2005 18:35:02

f you refer to Ravi's reference in Microsoft's implementation of failover,
you should should be able to add so called "standby" materials such as a
short ad, movie or audio next to your source. If both your sources are not
ready to unicast, the Media server will automatically loop back to the
"standby" material until your next source is available.

This is the solution I have. Does anyone else have a better one?

God bless,
Felix

"-DC-" wrote: