Ability to manually initiate failover on Geo-Redundant storage accounts (GRS & RA-GRS)
GRS & RA-GRS storage accounts currently geo-replicate all contents from a primary zone's storage account (storageA) to a secondary zone's storage account (storageB) automatically and this is wonderful.
Right now, it is Microsoft that control when the failover occurs from storageA to storageB. It is also very well documented that this switch will happen only as a last resort move because of the complexity of switching all accounts, possible data loss, etc...
For advanced DR scenarios it would be very handy for us to have a way to manually trigger the failover switch between storageA and storageB.
After the manual switch, DNS would point to storageB instead of storageA and read/write operations would work as expected on the newly promoted storage account (storageB)
Thank you for your feedback. We are working on customer controlled failover for both disaster and DR drill scenarios. Please contact firstname.lastname@example.org for more details about enrolling in a private preview, and for any further questions.
Art Khlobystin commented
Customer initiated failover is in preview in US West 2 and US West Central - https://docs.microsoft.com/en-us/azure/storage/common/storage-disaster-recovery-guidance. Regional expansion is in works! Please contact email@example.com to get enrolled.
Ramsey Callaway commented
After yesterday's South Central US outage, this ability is more important than ever. Microsoft is unwilling to call a failover event at the risk of having to update all of their marketing slides, so we need this power in our hands.
Hi, is there any timeline for GA or public preview?
Sascha Wenninger commented
@Lavanya it seems this email address is internal-only and is rejecting emails.
Lavanya Kasarabada [lakasa@MSFT] commented
Hi Stephane, we have some great news to share! We are working on having customer controlled failover for both disaster and DR drill scenarios. We have a private preview coming soon so please contact firstname.lastname@example.org for more details.
Mohammed Kasim commented
Any update on manual trigger of fail over?
Jason Tang commented
Hi guys, we are actively working on customer controlled failover scenario but don't have a release date to share it. If you are interested in this scenario, please don't hesitate to contact me at Jutang@microsoft.com so we can learn more from you, thanks.
-Jason Tang (PM of Azure Storage)
Shaun Laughton commented
Tis really is a glaring omission. I may be overlooking something, but this kind of feature is available for Azure SQL Database in the form of Failover Groups. Why not storage?
Gonzalo Parra commented
This is an important requirement so we can have control over the RTO, otherwise its a big question mark...
does any one if this blocking changed at this time?
This not existing is crazy.
Krishnendu Ghosh commented
If a certain amount of data loss is acceptable in a particular scenario and there is short RTO requirement, manually initiating a failover is highly required feature.
It must be supported, it has no point that failover is out of control on customer side.
Failover is not only for the purpose of "Real Disaster" happens.
Ranger Due commented
CSA: Without the ability to test this feature, it greatly puts into question the ability of my clients to correctly measure their risk profile on Azure. It is an unnecessary blocker.