<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.cas-group.net/index.php?action=history&amp;feed=atom&amp;title=Recovery-Oriented_Computing</id>
	<title>Recovery-Oriented Computing - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.cas-group.net/index.php?action=history&amp;feed=atom&amp;title=Recovery-Oriented_Computing"/>
	<link rel="alternate" type="text/html" href="https://wiki.cas-group.net/index.php?title=Recovery-Oriented_Computing&amp;action=history"/>
	<updated>2026-07-19T18:05:46Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://wiki.cas-group.net/index.php?title=Recovery-Oriented_Computing&amp;diff=1227&amp;oldid=prev</id>
		<title>Admin: Reverted edits by Eboxytezi (Talk) to last version by Jfromm</title>
		<link rel="alternate" type="text/html" href="https://wiki.cas-group.net/index.php?title=Recovery-Oriented_Computing&amp;diff=1227&amp;oldid=prev"/>
		<updated>2011-02-11T21:40:10Z</updated>

		<summary type="html">&lt;p&gt;Reverted edits by &lt;a href=&quot;/index.php?title=Special:Contributions/Eboxytezi&quot; title=&quot;Special:Contributions/Eboxytezi&quot;&gt;Eboxytezi&lt;/a&gt; (&lt;a href=&quot;/index.php?title=User_talk:Eboxytezi&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;User talk:Eboxytezi (page does not exist)&quot;&gt;Talk&lt;/a&gt;) to last version by &lt;a href=&quot;/index.php?title=User:Jfromm&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;User:Jfromm (page does not exist)&quot;&gt;Jfromm&lt;/a&gt;&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 16:40, 11 February 2011&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot; id=&quot;mw-diff-left-l1&quot;&gt;Line 1:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 1:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;−&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;del style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;=[http://akekuqegify.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-added&quot;&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Recovery Oriented Computing&amp;#039;&amp;#039;&amp;#039; (ROC) was started as a joint Berkeley/Stanford project in order to investigate novel techniques for building highly-dependable Internet services [http://roc.cs.berkeley.edu/]. Contrary to traditional fault-tolerance approaches in distributed systems, ROC doest not assume that total avoidance and prediction of failures is possible. The philosophy of ROC is to accept the fact that failures will happen, but to be well prepared to recover quickly. It emphasizes fast recovery from failures rather than complete failure-avoidance.&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Recovery Oriented Computing&amp;#039;&amp;#039;&amp;#039; (ROC) was started as a joint Berkeley/Stanford project in order to investigate novel techniques for building highly-dependable Internet services [http://roc.cs.berkeley.edu/]. Contrary to traditional fault-tolerance approaches in distributed systems, ROC doest not assume that total avoidance and prediction of failures is possible. The philosophy of ROC is to accept the fact that failures will happen, but to be well prepared to recover quickly. It emphasizes fast recovery from failures rather than complete failure-avoidance.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://wiki.cas-group.net/index.php?title=Recovery-Oriented_Computing&amp;diff=1029&amp;oldid=prev</id>
		<title>Eboxytezi at 02:47, 24 November 2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.cas-group.net/index.php?title=Recovery-Oriented_Computing&amp;diff=1029&amp;oldid=prev"/>
		<updated>2010-11-24T02:47:50Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 21:47, 23 November 2010&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot; id=&quot;mw-diff-left-l1&quot;&gt;Line 1:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 1:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;=[http://akekuqegify.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Recovery Oriented Computing&amp;#039;&amp;#039;&amp;#039; (ROC) was started as a joint Berkeley/Stanford project in order to investigate novel techniques for building highly-dependable Internet services [http://roc.cs.berkeley.edu/]. Contrary to traditional fault-tolerance approaches in distributed systems, ROC doest not assume that total avoidance and prediction of failures is possible. The philosophy of ROC is to accept the fact that failures will happen, but to be well prepared to recover quickly. It emphasizes fast recovery from failures rather than complete failure-avoidance.&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Recovery Oriented Computing&amp;#039;&amp;#039;&amp;#039; (ROC) was started as a joint Berkeley/Stanford project in order to investigate novel techniques for building highly-dependable Internet services [http://roc.cs.berkeley.edu/]. Contrary to traditional fault-tolerance approaches in distributed systems, ROC doest not assume that total avoidance and prediction of failures is possible. The philosophy of ROC is to accept the fact that failures will happen, but to be well prepared to recover quickly. It emphasizes fast recovery from failures rather than complete failure-avoidance.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>Eboxytezi</name></author>
	</entry>
	<entry>
		<id>https://wiki.cas-group.net/index.php?title=Recovery-Oriented_Computing&amp;diff=112&amp;oldid=prev</id>
		<title>Jfromm: New page: &#039;&#039;&#039;Recovery Oriented Computing&#039;&#039;&#039; (ROC) was started as a joint Berkeley/Stanford project in order to investigate novel techniques for building highly-dependable Internet services [http://r...</title>
		<link rel="alternate" type="text/html" href="https://wiki.cas-group.net/index.php?title=Recovery-Oriented_Computing&amp;diff=112&amp;oldid=prev"/>
		<updated>2008-09-14T15:50:34Z</updated>

		<summary type="html">&lt;p&gt;New page: &amp;#039;&amp;#039;&amp;#039;Recovery Oriented Computing&amp;#039;&amp;#039;&amp;#039; (ROC) was started as a joint Berkeley/Stanford project in order to investigate novel techniques for building highly-dependable Internet services [http://r...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Recovery Oriented Computing&amp;#039;&amp;#039;&amp;#039; (ROC) was started as a joint Berkeley/Stanford project in order to investigate novel techniques for building highly-dependable Internet services [http://roc.cs.berkeley.edu/]. Contrary to traditional fault-tolerance approaches in distributed systems, ROC doest not assume that total avoidance and prediction of failures is possible. The philosophy of ROC is to accept the fact that failures will happen, but to be well prepared to recover quickly. It emphasizes fast recovery from failures rather than complete failure-avoidance.&lt;br /&gt;
&lt;br /&gt;
In large distributed software systems, failures are inevitable, and the exact cause of the fault or error is not always necessary for many recovery techniques. A simple method to recover quickly is to restart the corresponding components of the system: the server, the service or single EJBs. The goal of ROC is to create [[Dependable System|dependable systems]] and to reach higher levels of [[Fault Tolerance|fault tolerance]] and [[Scalability|scalability]]. The two principles of ROC are therefore&lt;br /&gt;
&lt;br /&gt;
* Microreboot - selective restart of small system parts &lt;br /&gt;
* System-Level Undo - reconfiguration by rollback recovery&lt;br /&gt;
&lt;br /&gt;
[[Category:x-Computing_Techniques]]&lt;/div&gt;</summary>
		<author><name>Jfromm</name></author>
	</entry>
</feed>