<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: BES failover software released</title>
	<atom:link href="http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/</link>
	<description>The voice of the BlackBerry community.</description>
	<lastBuildDate>Sat, 11 Feb 2012 05:22:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Gregg S.A. Tuijnenburg</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-329810</link>
		<dc:creator>Gregg S.A. Tuijnenburg</dc:creator>
		<pubDate>Fri, 02 Jan 2009 21:45:49 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-329810</guid>
		<description>I can&#039;t agree more Brennels ..</description>
		<content:encoded><![CDATA[<p>I can&#8217;t agree more Brennels ..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg S.A. Tuijnenburg</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-487584</link>
		<dc:creator>Gregg S.A. Tuijnenburg</dc:creator>
		<pubDate>Fri, 02 Jan 2009 21:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-487584</guid>
		<description>I can&#039;t agree more Brennels ..</description>
		<content:encoded><![CDATA[<p>I can&#8217;t agree more Brennels ..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brennels</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-329802</link>
		<dc:creator>brennels</dc:creator>
		<pubDate>Fri, 02 Jan 2009 20:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-329802</guid>
		<description>No matter what solution you are looking it’s never wrong to do your research, compare all product capabilities, get the facts, request customer references or case studies and you won&#039;t be misled from gathering your own information. And beware of those who try to put words in your mouth.</description>
		<content:encoded><![CDATA[<p>No matter what solution you are looking it’s never wrong to do your research, compare all product capabilities, get the facts, request customer references or case studies and you won&#8217;t be misled from gathering your own information. And beware of those who try to put words in your mouth.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brennels</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-487583</link>
		<dc:creator>brennels</dc:creator>
		<pubDate>Fri, 02 Jan 2009 20:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-487583</guid>
		<description>No matter what solution you are looking it’s never wrong to do your research, compare all product capabilities, get the facts, request customer references or case studies and you won&#039;t be misled from gathering your own information. And beware of those who try to put words in your mouth.</description>
		<content:encoded><![CDATA[<p>No matter what solution you are looking it’s never wrong to do your research, compare all product capabilities, get the facts, request customer references or case studies and you won&#8217;t be misled from gathering your own information. And beware of those who try to put words in your mouth.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg S.A. Tuijnenburg</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-329759</link>
		<dc:creator>Gregg S.A. Tuijnenburg</dc:creator>
		<pubDate>Fri, 02 Jan 2009 14:39:44 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-329759</guid>
		<description>Erik,

Regarding the pricing structure it depends on how you look at it. DT is priced on a &#039;per server&#039; basis while Neverfail is priced per server pair.

Also both products may only be compared on a &#039;replication&#039; level (where DT does not copy the registry changes accross while Neverfail does - what is an application worth without the registry being consistent?). 

Neverfail is application aware and so takes care of the whole chain of applications where the BlackBerry Enterprise Server is depending on.

Neverfail is all about &#039;Continuous Availability&#039; what simply means that the &#039;enduser should be able to use the application at all times&#039;, no matter what failure occurs (hardware-failure,software-failure, data corruption, registry corruption, connectivity problems, performance de-crease etc.).

So there&#039;s no way to compare the two products. If you&#039;re looking for an automated failover solution so your end-users will always be able to use your application: go for Neverfail, without a doubt.

As Brennels said earlier, DT is more complex to implement (build of secondary server = manually), Neverfail is easy to install, all automated &amp; easy to maintain.

Best regards,
Gregg.</description>
		<content:encoded><![CDATA[<p>Erik,</p>
<p>Regarding the pricing structure it depends on how you look at it. DT is priced on a &#8216;per server&#8217; basis while Neverfail is priced per server pair.</p>
<p>Also both products may only be compared on a &#8216;replication&#8217; level (where DT does not copy the registry changes accross while Neverfail does &#8211; what is an application worth without the registry being consistent?). </p>
<p>Neverfail is application aware and so takes care of the whole chain of applications where the BlackBerry Enterprise Server is depending on.</p>
<p>Neverfail is all about &#8216;Continuous Availability&#8217; what simply means that the &#8216;enduser should be able to use the application at all times&#8217;, no matter what failure occurs (hardware-failure,software-failure, data corruption, registry corruption, connectivity problems, performance de-crease etc.).</p>
<p>So there&#8217;s no way to compare the two products. If you&#8217;re looking for an automated failover solution so your end-users will always be able to use your application: go for Neverfail, without a doubt.</p>
<p>As Brennels said earlier, DT is more complex to implement (build of secondary server = manually), Neverfail is easy to install, all automated &amp; easy to maintain.</p>
<p>Best regards,<br />
Gregg.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg S.A. Tuijnenburg</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-487582</link>
		<dc:creator>Gregg S.A. Tuijnenburg</dc:creator>
		<pubDate>Fri, 02 Jan 2009 14:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-487582</guid>
		<description>Erik,

Regarding the pricing structure it depends on how you look at it. DT is priced on a &#039;per server&#039; basis while Neverfail is priced per server pair.

Also both products may only be compared on a &#039;replication&#039; level (where DT does not copy the registry changes accross while Neverfail does - what is an application worth without the registry being consistent?). 

Neverfail is application aware and so takes care of the whole chain of applications where the BlackBerry Enterprise Server is depending on.

Neverfail is all about &#039;Continuous Availability&#039; what simply means that the &#039;enduser should be able to use the application at all times&#039;, no matter what failure occurs (hardware-failure,software-failure, data corruption, registry corruption, connectivity problems, performance de-crease etc.).

So there&#039;s no way to compare the two products. If you&#039;re looking for an automated failover solution so your end-users will always be able to use your application: go for Neverfail, without a doubt.

As Brennels said earlier, DT is more complex to implement (build of secondary server = manually), Neverfail is easy to install, all automated &amp; easy to maintain.

Best regards,
Gregg.</description>
		<content:encoded><![CDATA[<p>Erik,</p>
<p>Regarding the pricing structure it depends on how you look at it. DT is priced on a &#8216;per server&#8217; basis while Neverfail is priced per server pair.</p>
<p>Also both products may only be compared on a &#8216;replication&#8217; level (where DT does not copy the registry changes accross while Neverfail does &#8211; what is an application worth without the registry being consistent?). </p>
<p>Neverfail is application aware and so takes care of the whole chain of applications where the BlackBerry Enterprise Server is depending on.</p>
<p>Neverfail is all about &#8216;Continuous Availability&#8217; what simply means that the &#8216;enduser should be able to use the application at all times&#8217;, no matter what failure occurs (hardware-failure,software-failure, data corruption, registry corruption, connectivity problems, performance de-crease etc.).</p>
<p>So there&#8217;s no way to compare the two products. If you&#8217;re looking for an automated failover solution so your end-users will always be able to use your application: go for Neverfail, without a doubt.</p>
<p>As Brennels said earlier, DT is more complex to implement (build of secondary server = manually), Neverfail is easy to install, all automated &amp; easy to maintain.</p>
<p>Best regards,<br />
Gregg.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brennels</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-326937</link>
		<dc:creator>Brennels</dc:creator>
		<pubDate>Thu, 11 Dec 2008 16:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-326937</guid>
		<description>Hi Erik, it has been a while since I have implemented Double-Take for BES but know there have been some significant improvements with the DT Application Manager that will help auto-discover the BES server and related database. There is usually two parts the BES server and the SQL backend. Double-Take will replicate all the changes from the primary server to the DR target and in the event of a disaster redirect the DNS, mount the database and start all the relevent services. There are some white papers on BES that may be useful to you http://www.doubletake.com/Documents/DBTK/Ensuring_Availability_of_Blackberry_Enterprise_Server.pdf

Hope this helps,

- Regards</description>
		<content:encoded><![CDATA[<p>Hi Erik, it has been a while since I have implemented Double-Take for BES but know there have been some significant improvements with the DT Application Manager that will help auto-discover the BES server and related database. There is usually two parts the BES server and the SQL backend. Double-Take will replicate all the changes from the primary server to the DR target and in the event of a disaster redirect the DNS, mount the database and start all the relevent services. There are some white papers on BES that may be useful to you <a href="http://www.doubletake.com/Documents/DBTK/Ensuring_Availability_of_Blackberry_Enterprise_Server.pdf" rel="nofollow">http://www.doubletake.com/Documents/DBTK/Ensuring_Availability_of_Blackberry_Enterprise_Server.pdf</a></p>
<p>Hope this helps,</p>
<p>- Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brennels</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-487581</link>
		<dc:creator>Brennels</dc:creator>
		<pubDate>Thu, 11 Dec 2008 16:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-487581</guid>
		<description>Hi Erik, it has been a while since I have implemented Double-Take for BES but know there have been some significant improvements with the DT Application Manager that will help auto-discover the BES server and related database. There is usually two parts the BES server and the SQL backend. Double-Take will replicate all the changes from the primary server to the DR target and in the event of a disaster redirect the DNS, mount the database and start all the relevent services. There are some white papers on BES that may be useful to you http://www.doubletake.com/Documents/DBTK/Ensuring_Availability_of_Blackberry_Enterprise_Server.pdf

Hope this helps,

- Regards</description>
		<content:encoded><![CDATA[<p>Hi Erik, it has been a while since I have implemented Double-Take for BES but know there have been some significant improvements with the DT Application Manager that will help auto-discover the BES server and related database. There is usually two parts the BES server and the SQL backend. Double-Take will replicate all the changes from the primary server to the DR target and in the event of a disaster redirect the DNS, mount the database and start all the relevent services. There are some white papers on BES that may be useful to you <a href="http://www.doubletake.com/Documents/DBTK/Ensuring_Availability_of_Blackberry_Enterprise_Server.pdf" rel="nofollow">http://www.doubletake.com/Documents/DBTK/Ensuring_Availability_of_Blackberry_Enterprise_Server.pdf</a></p>
<p>Hope this helps,</p>
<p>- Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Walraven</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-326882</link>
		<dc:creator>Erik Walraven</dc:creator>
		<pubDate>Thu, 11 Dec 2008 10:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-326882</guid>
		<description>Neverfail in contrast to Doubletake is more as twice so expensive. That&#039; s one of the reasons that Doubletake is an interesting player on the relative small &#039;BES failover&#039; market.

What I am wondering is, has anyone got any experiences with Doubletake? Pls share them with me, because I am building a failover situation at this moment.</description>
		<content:encoded><![CDATA[<p>Neverfail in contrast to Doubletake is more as twice so expensive. That&#8217; s one of the reasons that Doubletake is an interesting player on the relative small &#8216;BES failover&#8217; market.</p>
<p>What I am wondering is, has anyone got any experiences with Doubletake? Pls share them with me, because I am building a failover situation at this moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Walraven</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-487580</link>
		<dc:creator>Erik Walraven</dc:creator>
		<pubDate>Thu, 11 Dec 2008 10:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-487580</guid>
		<description>Neverfail in contrast to Doubletake is more as twice so expensive. That&#039; s one of the reasons that Doubletake is an interesting player on the relative small &#039;BES failover&#039; market.

What I am wondering is, has anyone got any experiences with Doubletake? Pls share them with me, because I am building a failover situation at this moment.</description>
		<content:encoded><![CDATA[<p>Neverfail in contrast to Doubletake is more as twice so expensive. That&#8217; s one of the reasons that Doubletake is an interesting player on the relative small &#8216;BES failover&#8217; market.</p>
<p>What I am wondering is, has anyone got any experiences with Doubletake? Pls share them with me, because I am building a failover situation at this moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick harmer</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-273686</link>
		<dc:creator>nick harmer</dc:creator>
		<pubDate>Tue, 15 Apr 2008 15:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-273686</guid>
		<description>Neverfail has offered HA/DR for BES servers for more than two years with hundreds of deployed customers.  See Neverfail at WES where they are a Gold Sponsor</description>
		<content:encoded><![CDATA[<p>Neverfail has offered HA/DR for BES servers for more than two years with hundreds of deployed customers.  See Neverfail at WES where they are a Gold Sponsor</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick harmer</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-487579</link>
		<dc:creator>nick harmer</dc:creator>
		<pubDate>Tue, 15 Apr 2008 15:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-487579</guid>
		<description>Neverfail has offered HA/DR for BES servers for more than two years with hundreds of deployed customers.  See Neverfail at WES where they are a Gold Sponsor</description>
		<content:encoded><![CDATA[<p>Neverfail has offered HA/DR for BES servers for more than two years with hundreds of deployed customers.  See Neverfail at WES where they are a Gold Sponsor</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WES Exhibitor Spotlight: Double-Take Software &#124; BlackBerry Cool</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-271753</link>
		<dc:creator>WES Exhibitor Spotlight: Double-Take Software &#124; BlackBerry Cool</dc:creator>
		<pubDate>Fri, 11 Apr 2008 18:45:11 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-271753</guid>
		<description>[...] normal business continues, often within minutes or even seconds of the service interruption. They only recently announced BES support in addition to their support for Lotus Notes, Exchange, and so on, so [...]</description>
		<content:encoded><![CDATA[<p>[...] normal business continues, often within minutes or even seconds of the service interruption. They only recently announced BES support in addition to their support for Lotus Notes, Exchange, and so on, so [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: booyaa</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-199197</link>
		<dc:creator>booyaa</dc:creator>
		<pubDate>Fri, 26 Oct 2007 14:18:56 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-199197</guid>
		<description>How does this compare to neverfail&#039;s offering? Neverfail provides load balancing and high availability across all your enterprise apps i.e. Mail, Fax and Blackberry.</description>
		<content:encoded><![CDATA[<p>How does this compare to neverfail&#8217;s offering? Neverfail provides load balancing and high availability across all your enterprise apps i.e. Mail, Fax and Blackberry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: booyaa</title>
		<link>http://www.blackberrycool.com/2007/10/26/bes-failover-software-released/comment-page-1/#comment-487578</link>
		<dc:creator>booyaa</dc:creator>
		<pubDate>Fri, 26 Oct 2007 14:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/10/26/005915/#comment-487578</guid>
		<description>How does this compare to neverfail&#039;s offering? Neverfail provides load balancing and high availability across all your enterprise apps i.e. Mail, Fax and Blackberry.</description>
		<content:encoded><![CDATA[<p>How does this compare to neverfail&#8217;s offering? Neverfail provides load balancing and high availability across all your enterprise apps i.e. Mail, Fax and Blackberry.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  www.blackberrycool.com/2007/10/26/bes-failover-software-released/feed/ ) in 0.50347 seconds, on Feb 11th, 2012 at 10:22 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 11:22 am UTC -->
