<?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"
	>
<channel>
	<title>Comments for ISIS Papyrus Platform Architecture</title>
	<atom:link href="http://isispapyrus.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://isispapyrus.wordpress.com</link>
	<description>The Chief Architect's News Blog</description>
	<pubDate>Sat, 19 Jul 2008 02:10:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>Comment on More on the ISIS Papyrus Platform by Max Pucher</title>
		<link>http://isispapyrus.wordpress.com/about-isis-p/more_platform/#comment-4</link>
		<dc:creator>Max Pucher</dc:creator>
		<pubDate>Tue, 10 Jun 2008 10:56:54 +0000</pubDate>
		<guid isPermaLink="false">http://isispapyrus.wordpress.com/about-isis-p/more_platform/#comment-4</guid>
		<description>Thanks for your question. Papyrus supports a High Availability Setup with Hot-Backup nodes. The Passive Hot-Backup node takes up the workload if the Active stops to respond to its pinging. It does not require a Windows 2003 Cluster Setup but just a shared disk or SAN. This functionality is available for Windows, Linux, HP/UX, AIX, Solaris and z/OS. The Hot backup node does not have to be on the same operating system as the active node.

In V7 we will also offer a FT-Cluster Mode, where several running nodes create a DB and TX cluster that is completely FAULT TOLERANT. A failing node will not even be noticed by the user and a crashed data node will be recovered from the data copies of th other cluster nodes. That functionality will be available in V7 in 2009.</description>
		<content:encoded><![CDATA[<p>Thanks for your question. Papyrus supports a High Availability Setup with Hot-Backup nodes. The Passive Hot-Backup node takes up the workload if the Active stops to respond to its pinging. It does not require a Windows 2003 Cluster Setup but just a shared disk or SAN. This functionality is available for Windows, Linux, HP/UX, AIX, Solaris and z/OS. The Hot backup node does not have to be on the same operating system as the active node.</p>
<p>In V7 we will also offer a FT-Cluster Mode, where several running nodes create a DB and TX cluster that is completely FAULT TOLERANT. A failing node will not even be noticed by the user and a crashed data node will be recovered from the data copies of th other cluster nodes. That functionality will be available in V7 in 2009.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on More on the ISIS Papyrus Platform by rgmoises</title>
		<link>http://isispapyrus.wordpress.com/about-isis-p/more_platform/#comment-3</link>
		<dc:creator>rgmoises</dc:creator>
		<pubDate>Tue, 10 Jun 2008 09:06:49 +0000</pubDate>
		<guid isPermaLink="false">http://isispapyrus.wordpress.com/about-isis-p/more_platform/#comment-3</guid>
		<description>Hi. is their an architecture for the Papyrus Docexec and pdf that handles High Availability (Active/Passive or Active/Active) Setup? Can it be also be clustered in a windows 2003 cluster ? Thank you very much</description>
		<content:encoded><![CDATA[<p>Hi. is their an architecture for the Papyrus Docexec and pdf that handles High Availability (Active/Passive or Active/Active) Setup? Can it be also be clustered in a windows 2003 cluster ? Thank you very much</p>
]]></content:encoded>
	</item>
</channel>
</rss>
