build a journaling system for azure table storage
Cloud storage services such as Windows Azure Table storage do present somewhat unique opportunities for protecting us against failures. Yaron Goland has proposed (http://www.goland.org/do-i-need-to-backupjournal-my-windows-azure-table-store/) what he termed a "journal" system which captures all PUT, POST & DELETE operations against a service:
I would like to have a journal that records every command issued against the system ... then when I find out about a data logic corruption bug caused by my front end I could at least try to figure out which of my users was likely to be affected by reviewing the journal
The very nature of Windows Azure Table storage (i.e. CRUD operations against a simple partition key/row key scheme) means that such a journaling system could (and argubly should) be provided by Windows Azure itself rather than being something that the application developer has to build themselves. The service could also provide the ability to "replay" all operations against a given partion key/row key since a specified point in time.
We have now delivered Windows Azure Storage Logging (http://blogs.msdn.com/b/windowsazurestorage/archive/2011/08/03/windows-azure-storage-logging-using-logs-to-track-storage-requests.aspx), which supports logging of requests against storage accounts. You can configure usage of this through the management portal (http://www.windowsazure.com/en-us/documentation/articles/storage-monitor-storage-account/). The ability to replay the requests is under review.