Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Query: Azure Storage failover for a RA-GRS account #15290

Closed
asgoe opened this issue Jun 17, 2021 · 9 comments
Closed

Query: Azure Storage failover for a RA-GRS account #15290

asgoe opened this issue Jun 17, 2021 · 9 comments
Labels
customer-reported question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. Storage

Comments

@asgoe
Copy link

asgoe commented Jun 17, 2021

We are working on creating scripts to failover our storage accounts (RA-GRS configuration). The failover documentation mentions that after failover the account is configured as LRS and needs to be re-enabled as RA-GRS. We use the Set-AzStorageAccount cmd (after failing over the account to the secondary region) to covert the account back from LRS to RA-GRS. Few questions about this flow:

  1. When the primary region is in an outage, will the Set-AzStorageAccount cmd succeed in converting the storage account from LRS to RA-GRS?

  • If yes, what happens to the replication while primary region is under outage?

  • If no, what is the correct process to follow to convert the account back to RA-GRS?

  1. Is the Set-AzStorageAccount cmd asynchronous? We have had cases where in our testing the above command succeeded, but the portal was still showing the account as LRS. Also, the when we ran the Get-AzStorageAccount cmd call with -IncludeGeoReplicationStats as a parameter, it failed with the error "AccountType Standard_LRS is invalid. ".
@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported labels Jun 17, 2021
@dingmeng-xue dingmeng-xue added Service Attention This issue is responsible by Azure service team. Storage labels Jun 17, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jun 17, 2021
@ghost
Copy link

ghost commented Jun 17, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details

We are working on creating scripts to failover our storage accounts (RA-GRS configuration). The failover documentation mentions that after failover the account is configured as LRS and needs to be re-enabled as RA-GRS. We use the Set-AzStorageAccount cmd (after failing over the account to the secondary region) to covert the account back from LRS to RA-GRS. Few questions about this flow:

  1. When the primary region is in an outage, will the Set-AzStorageAccount cmd succeed in converting the storage account from LRS to RA-GRS?

  • If yes, what happens to the replication while primary region is under outage?

  • If no, what is the correct process to follow to convert the account back to RA-GRS?

  1. Is the Set-AzStorageAccount cmd asynchronous? We have had cases where in our testing the above command succeeded, but the portal was still showing the account as LRS. Also, the when we ran the Get-AzStorageAccount cmd call with -IncludeGeoReplicationStats as a parameter, it failed with the error "AccountType Standard_LRS is invalid. ".
Author: asgoe
Assignees: -
Labels:

Service Attention, Storage, customer-reported, needs-triage, question
Milestone: -

@blueww
Copy link
Member

blueww commented Jun 17, 2021 •
edited
Loading

@asgoe
For Question 1, this is more like a server behavior question than a Powershell question, need check with server team.

For Question 2， Set-AzStorageAccount cmd is synchronous. We need to check with server team why you don't see the property update on server.

Could you give the debug log on Set/Get-AzstorageAccount cmdlet (add "-debug"), to help server team investigate the issue?
It's better if you can give the failover start and end time.

BTW, for storage server questions, https://github.com/Azure/azure-rest-api-specs might be a better place to raise them.

@asgoe
Copy link
Author

asgoe commented Jun 17, 2021 via email

@blueww
Copy link
Member

blueww commented Jun 17, 2021 •
edited
Loading

I have written a mail to server team.

If you can give your mail address, I might can add you to the mail thread.

@asgoe
Copy link
Author

asgoe commented Jun 17, 2021 via email

@blueww
Copy link
Member

blueww commented Jun 17, 2021 •
edited
Loading

@asgoe
It seems your mail is hidden by system.
So I will update the issue when get any update from server team.

BTW, for server issues, you can also use "Help + support" button in Azure Portal to raise the request.
image

@asgoe
Copy link
Author

asgoe commented Jun 17, 2021 via email •
edited
Loading

@blueww
Copy link
Member

blueww commented Jun 18, 2021

@asgoe
I have added you to the mail thread.

There are already some answer from server team, you can see details in the mail.
Let's go with the issue in mail first.

@blueww blueww mentioned this issue Jun 18, 2021
Closed
@blueww
Copy link
Member

blueww commented Jul 2, 2021

As we are discussing this server question/issue in mail, and this is not a PSH issue, I will close this issue.

@blueww blueww closed this as completed Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customer-reported question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. Storage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@blueww @dingmeng-xue @asgoe