Does Azure Storage failover and failback need two replications?
If I have an Azure Storage with GRS, and the WUS is primary and EUS is secondary.
Then if I need to do a customer failover, what will happen is that WUS is deleted, EUS becomes primary.
For example, after the issue in WUS has fixed, how many replications do I need to bring back to the state that WUS is primary and EUS is secondary?
Based on what I learned from the official document in Microsoft Learn. I think the process is like this:
- Change to GRS again. There will be a replication happen that transfer all data in EUS to WUS. After this we have: WUS(secondary) + EUS(primary)
- Failback to WUS. We will have: WUS(LRS) + EUS(deleted)
- Change to GRS again. There will be another replication happen that transfer all data in WUS to EUS. After this we have: WUS(primary) + EUS(secondary)
So, my question is that do we need to twice replications in order to change back to "primary is WUS, secondary is EUS" state? Because this since to be rather expensive as you need to transfer all data twice and it is time consuming, costly a lot.
This is a question on how Azure Storage works.
Yes, there would be 2 replications required and the process would work as documented .
Azure storage disaster recovery planning and failover
We currently have Planned Failover in private preview which will allow customers to test the Failover work flow while keeping geo-redundancy. As a result, there is no need to re-enable geo redundancy after each failover and failback operation. This table highlights the key differences between Customer Managed Failover (currently GA) and Planned Failover (currently in planned state ).
- Is this truly best way to delete last element in C?
- Understanding the difference in timing of two functions that increment each element of an integer array
- Why MSVC generates warning C4127 when constant is used in "while" - C
- Executing a user-space function from the kernel space
- Why must the variable used to hold getchar's return value be declared as int?
- mpirun -np 4 ./a.out doesn't use all my cores (ubuntu 24.04LTS)
- Shadowing an iterator inside a for loop has undefined (?) behaviour in C
- Sleep for N seconds and wait for keypress
- Dereference twice in gdb
- Is this declaration UB?
- return type defaults to 'int' [-Wimplicit-int]
- What is the scope of `fesetround()`?
- Which specific optimization flag causes libm functions to be treated as pure?
- How to render text in SDL2?
- Why would you use 'extern "C++"'?
- Strange Behavior Compiler Ignoring NULL Check Unless I Print Something in the if Statement
- Fast inverse square root using fixed point instead of floating point
- What is the const qualifier attached to in C: the memory area or the pointer?
- GCC options for strictest C code?
- How to do an explicit fall-through in C
- How do compilers treat CONST qualifier when the pointer points to a memory location obtained with malloc()?
- C: cmocka headers - how to unittest?
- Why in C when I print a double with a one decimal it round it to the next number
- Android C to Java SWIG unable to compile: incompatible types: byte cannot be converted to SWIGTYPE_p_uint8_t
- GNU Make in Ubuntu giving fatal error: rpc/types.h: No such file or directory
- How can I exclude non-numeric keys? CS50 Caesar Pset2
- How change every struct in an array of pointers?
- Optimized 2x2 matrix multiplication: Slow assembly versus fast SIMD
- Simple frame by frame video decoder library
- GCC no longer implements <varargs.h>