{"id":8466,"date":"2019-02-01T00:05:00","date_gmt":"2019-01-31T23:05:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=8466"},"modified":"2019-02-01T09:38:21","modified_gmt":"2019-02-01T08:38:21","slug":"ups-microsoft-deleted-azure-cloud-data-bases","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/02\/01\/ups-microsoft-deleted-azure-cloud-data-bases\/","title":{"rendered":"Ups, Microsoft deleted Azure Cloud data bases"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/Stop.jpg\" align=\"left\">[<a href=\"https:\/\/www.borncity.com\/blog\/2019\/01\/31\/dumm-gelaufen-microsoft-lscht-azure-cloud-datenbanken\/\" target=\"_blank\">German<\/a>]That's not cool: The issues that Microsoft have had with Microsoft 365 on January 29, 2019 also affected Azure SQL databases. Some customers have had SQL databases deleted on Azure. After restoring a snapshot, customers discovered that there were transaction data of up to 5 minutes are missing within their databases.<\/p>\n<p><!--more--><\/p>\n<h2>Microsoft 365 outage on January 29, 2019<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg01.met.vgwort.de\/na\/00cd74a0273c4f36a287c75acde0ea83\" width=\"1\" height=\"1\">The last days Microsoft was shaken by failures of its Office365.com and Microsoft 365 services &#8211; see article links at the end of this article. Now The Register reported <a href=\"https:\/\/www.theregister.co.uk\/2019\/01\/30\/azure_sql_delete\/\" target=\"_blank\">here<\/a> that Azure's January 29, 2019 failure even claimed some unexpected victims. Customers suddenly discovered that their Azure SQL databases had been deleted or that data was missing. Here is a tweet from a victim:<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p lang=\"en\" dir=\"ltr\">Spent my whole day on why our Azure SQL database was dropped and a new Azure SQL Database was created with random name appended to dropped database name,<\/p>\n<p>\u2014 SANTHANAM SENGUTUVAN (@santhu7289) 30. Januar 2019<\/p><\/blockquote>\n<p><span id=\"preserve3c68134bf2be475abe2faa880e776aa5\" class=\"wlWriterPreserve\"><SCRIPT charset=\"utf-8\" src=\"https:\/\/platform.twitter.com\/widgets.js\" async><\/SCRIPT><\/span> <\/p>\n<p>Also the following user was probably caught cold by the deleted Azure SQL database.&nbsp; <\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p lang=\"en\" dir=\"ltr\"><a href=\"https:\/\/twitter.com\/AzureSupport?ref_src=twsrc%5Etfw\">@AzureSupport<\/a> <a href=\"https:\/\/twitter.com\/AzureSQLDB?ref_src=twsrc%5Etfw\">@AzureSQLDB<\/a> Last night around 21.23 some of our azure SQL databases where deleted and not by us. The database is back restored but is empty, we did not do the restore?<br \/>I heard from other people that they have the same issue but there databases are not restored<\/p>\n<p>\u2014 Koen Vanden Bossche (@VdBosscheKoen) <a href=\"https:\/\/twitter.com\/VdBosscheKoen\/status\/1090541995360161793?ref_src=twsrc%5Etfw\">30. Januar 2019<\/a><\/p><\/blockquote>\n<p><span id=\"preserve78910de3cd7947ddb4f19cf440083310\" class=\"wlWriterPreserve\"><SCRIPT charset=\"utf-8\" src=\"https:\/\/platform.twitter.com\/widgets.js\" async><\/SCRIPT><\/span> <\/p>\n<p>The issue only affected customers using Transparent Data Encryption (TDE). This is to protect the databases against malicious activities of attackers.&nbsp; <\/p>\n<h2>Azure SQL database deleted<\/h2>\n<p>According to the site <a href=\"https:\/\/www.theregister.co.uk\/2019\/01\/30\/azure_sql_delete\/\" target=\"_blank\">The Register<\/a>, during the Azure instabilities that occurred on 01\/29\/2019, internal automatic task simply deleted the affected SQL databases. Microsoft was able to restore the databases from snapshots. But the snapshots was up to 5 minutes in the past, so customers were missing 5 minutes of data from various transactions. <\/p>\n<p>The issue affected a number of Azure SQL databases that use custom KeyVault keys for transparent data encryption (TDE). The Register cited from a messages Microsoft has send to affected users: <\/p>\n<blockquote>\n<p>\"An automated process, designed to trigger when custom keys are removed from KeyVault, inadvertently caused these TDE databases to be dropped.<\/p>\n<p>We are in the process of restoring a copy of these SQL DBs from a recovery point in time of less than 5 minutes before the database was dropped. These restored databases &#8230; are located on the same server as the original database\"<\/p>\n<\/blockquote>\n<p>Within the notification, Microsoft asks customers to check the databases for lost data and, if necessary, open a support ticket. <\/p>\n<blockquote>\n<p>We ask that customers, for each database, identify if lost transactions, during this 5 minute timeframe, could impact business processes or applications outside the database. We would ask you to raise a support ticket in this instance. If the restored database is suitable, the database can be renamed to the original name to continue usage of it.<\/p>\n<\/blockquote>\n<p>I guess, some customers are pretty pissed. But Microsoft has good news for those affected \u2013 the company wrote: <\/p>\n<blockquote>\n<p>We sincerely apologize for the impact on your service. Azure usage fees are waived for all restored databases for 2 months and for all original databases for 3 months. We are continuously taking steps to improve the Microsoft Azure platform and our processes to ensure that such incidents do not occur again in the future.<\/p>\n<\/blockquote>\n<p>That sounds good &#8211; or what's your opinion? The Register asked Microsoft what the next step would be. A spokesman said: 'We're working to restore access to resources that were unavailable to a limited subset of customers. Full access has been re-established for most of those customers already.' <\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]That's not cool: The issues that Microsoft have had with Microsoft 365 on January 29, 2019 also affected Azure SQL databases. Some customers have had SQL databases deleted on Azure. After restoring a snapshot, customers discovered that there were transaction &hellip; <a href=\"https:\/\/borncity.com\/win\/2019\/02\/01\/ups-microsoft-deleted-azure-cloud-data-bases\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463],"tags":[47,65],"class_list":["post-8466","post","type-post","status-publish","format-standard","hentry","category-issue","tag-issue","tag-microsoft"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=8466"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8466\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=8466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=8466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=8466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}