<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Richard Parker's blog - All Comments</title><link>http://blogs.msdn.com/b/msrich/</link><description>I work in Premier Support for Developers, helping others to remove barriers to successful development on the Microsoft platform.</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Managing Risk on Windows Azure</title><link>http://blogs.msdn.com/b/msrich/archive/2012/12/13/managing-risk-on-windows-azure.aspx#10378310</link><pubDate>Sat, 15 Dec 2012 09:17:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10378310</guid><dc:creator>Richard S Parker</dc:creator><description>&lt;p&gt;Hi Daniel, thanks for your feedback. In this article, I focus specifically on platform risks. Perhaps the subject of a future blog post, safeguarding against application/user error is an altogether different subject - and not one that is specific to Windows Azure. &lt;/p&gt;
&lt;p&gt;In regards to your comment specifically on SQL Azure backup options, methods exist to copy databases (&lt;a rel="nofollow" target="_new" href="http://msdn.microsoft.com/en-us/library/windowsazure/ff951631.aspx"&gt;msdn.microsoft.com/.../ff951631.aspx&lt;/a&gt;) and how to import/export them (&lt;a rel="nofollow" target="_new" href="http://msdn.microsoft.com/en-us/library/windowsazure/hh335292.aspx"&gt;msdn.microsoft.com/.../hh335292.aspx&lt;/a&gt;). You can also leverage SQL Data Sync to facilitate this process: &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/b/windowsazure/archive/2012/10/26/announcing-the-windows-azure-sql-data-sync-october-update.aspx"&gt;blogs.msdn.com/.../announcing-the-windows-azure-sql-data-sync-october-update.aspx&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Thanks for reading and taking the time to comment. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10378310" width="1" height="1"&gt;</description></item><item><title>re: Managing Risk on Windows Azure</title><link>http://blogs.msdn.com/b/msrich/archive/2012/12/13/managing-risk-on-windows-azure.aspx#10377999</link><pubDate>Fri, 14 Dec 2012 01:27:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10377999</guid><dc:creator>Daniel Smith</dc:creator><description>&lt;p&gt;Other than hardware failures, the other major concern people have is protection against application/user error.&lt;/p&gt;
&lt;p&gt;Although Azure has the protection of geographic redundancy in the event of hardware failure, if you accidentally delete a record or table in your database, there are *no* backups to go back to...which scares the hell out of potential customers!&lt;/p&gt;
&lt;p&gt;I know backup/restore functionality is in the works, but it&amp;#39;s quite surprising that such a critical feature is still missing from Azure. &amp;nbsp;Any news on when this is going to be available?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10377999" width="1" height="1"&gt;</description></item><item><title>re: Quantifying and Avoiding Risk on the Windows Azure platform</title><link>http://blogs.msdn.com/b/msrich/archive/2012/03/31/quantifying-and-avoiding-risk-on-the-windows-azure-platform.aspx#10290925</link><pubDate>Wed, 04 Apr 2012 20:51:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10290925</guid><dc:creator>Richard S Parker</dc:creator><description>&lt;p&gt;Hi Rinat. The issue of data corruption is an altogether different problem: do you refer to corruption of data by a failure of a storage resource, or by a bug or misconfiguration in your app for instance? Do you mean blob storage or SQL Azure? &lt;/p&gt;
&lt;p&gt;While both carry risks, it is appropriate to first quantify the risk factors once you have determined what the risk actually is. This will determine the scope of work you have to carry out to bring the risk within a known level of tolerance.&lt;/p&gt;
&lt;p&gt;Perhaps I will cover this in a separate blog post!&lt;/p&gt;
&lt;p&gt;Thanks for reading and taking the time to comment.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10290925" width="1" height="1"&gt;</description></item><item><title>re: Quantifying and Avoiding Risk on the Windows Azure platform</title><link>http://blogs.msdn.com/b/msrich/archive/2012/03/31/quantifying-and-avoiding-risk-on-the-windows-azure-platform.aspx#10290837</link><pubDate>Wed, 04 Apr 2012 16:24:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10290837</guid><dc:creator>Rinat Abdullin</dc:creator><description>&lt;p&gt;How would you deal with risk of data corruption on windows Azure?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10290837" width="1" height="1"&gt;</description></item></channel></rss>