A look at things to consider if NOT using paired regions. Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc. 👂 Translate the captions to your native language via the auto-translate feature in settings! ruclips.net/video/v5b53-PgEmI/видео.html for a demo of using this feature. Thanks for watching! 🤙
always great work John! This has been top of mind since struggling to get quotas increased in East US and even seeing arm fail to deploy D and E series even with quota remaining. This run on the bank concept has kind of pushed me into looking at non paired regions. My biggest hurdle is the recovery service vault. It’s just so easy to have it paired, rebuild the infrastructure from bicep and then restore those pets that people won’t give up, into that paired region. Like you said though, it’s on us to put forth technology that becomes less geo dependent and explain the risk to the customer.
Great video per typical, especially on the rollout/upgrade sequencing. However, some customers (especially small to mid-size companies) also want simplicity. Paired regions make things simple, and operating across more regions adds complexity and cost (MPLS connections, etc.). I've started seeing capacity issues in our paired region with support saying we should pivot to another region. All this goes against simplicity and "the cloud is scalable". I hope these scale issues are temporary.
I'm not sure to give a green tick to the Storage Account support for not-paired regions. The only way to get back some of the functionalities is to use object replication, but as you said it is limited to blob files. I am not saying to add support to queues and files, but it having that mechanism for table data would be very important. I presume cosmos DB data migration tool is the tool to use but it requires application changes or multiple runs based on timestamps
A look at things to consider if NOT using paired regions. Please make sure to read the description for the chapters and key information about this video and others.
⚠ P L E A S E N O T E ⚠
🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there!
🕰 I don't discuss future content nor take requests for future content so please don't ask 😇
🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc.
👂 Translate the captions to your native language via the auto-translate feature in settings! ruclips.net/video/v5b53-PgEmI/видео.html for a demo of using this feature.
Thanks for watching!
🤙
always great work John! This has been top of mind since struggling to get quotas increased in East US and even seeing arm fail to deploy D and E series even with quota remaining. This run on the bank concept has kind of pushed me into looking at non paired regions. My biggest hurdle is the recovery service vault. It’s just so easy to have it paired, rebuild the infrastructure from bicep and then restore those pets that people won’t give up, into that paired region. Like you said though, it’s on us to put forth technology that becomes less geo dependent and explain the risk to the customer.
Thanks again John, really useful content as always ❤
My pleasure!
Really useful content John, Thanks again!
My pleasure!
Great video per typical, especially on the rollout/upgrade sequencing. However, some customers (especially small to mid-size companies) also want simplicity. Paired regions make things simple, and operating across more regions adds complexity and cost (MPLS connections, etc.). I've started seeing capacity issues in our paired region with support saying we should pivot to another region. All this goes against simplicity and "the cloud is scalable". I hope these scale issues are temporary.
I'm not sure to give a green tick to the Storage Account support for not-paired regions. The only way to get back some of the functionalities is to use object replication, but as you said it is limited to blob files. I am not saying to add support to queues and files, but it having that mechanism for table data would be very important. I presume cosmos DB data migration tool is the tool to use but it requires application changes or multiple runs based on timestamps
enjoying this video for today learning, thanks a lot!
Welcome!
Great content, like your videos 👌
Appreciate it!
🤙
remember, John is not posh
All regions have at least 2 x AZ’s I thought?!
No, not all regions have AZs. If they do its 3 seen per subscription.