Skip to content

Commit 87ed7e0

Browse files
committed
Adding include for reliability guidance
1 parent 7215ed9 commit 87ed7e0

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

articles/storage-actions/storage-tasks/storage-task-best-practices.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -93,9 +93,7 @@ Storage Actions perform more reliably in accounts with [geo-redundant storage](.
9393

9494
### Use geo redundancy for business continuity
9595

96-
Storage accounts with GRS and GZRS replicate data to a secondary region in the event of storage account failovers. The business continuity of storage actions significantly depends on the redundancy configuration of the target storage account. Storage accounts that are configured with geo-redundancy benefit from an automated failover process. This automatic management ensures that future task assignment run iterations, whether single or recurrent, executes in the secondary region without issues. However, storage tasks that were in progress at the time of failover might encounter failures. New storage tasks and storage task assignments continue to function as expected.
97-
98-
Consistent monitoring of the storage account is crucial. With a failover, you should thoroughly review task reporting and monitoring to verify the successful completion of all blob operations and to identify any discrepancies that need attention.
96+
[!INCLUDE [Storage Actions continuity after a failover](../../../includes/storage-actions-reliability.md)]
9997

10098
## Monitoring
10199

0 commit comments

Comments
 (0)