Skip to content

Commit 476d6a5

Browse files
committed
Add note
1 parent 6582acb commit 476d6a5

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/reliability/reliability-device-registry.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -107,6 +107,8 @@ For Azure Device Registry, Recovery Time Objective (RTO) is approximately 24 hou
107107

108108
<!-- Is there any guidance for what to do if this capability doesn't meet a customer's needs - e.g. if you a customer has no tolerance for downtime or data loss? Are there approaches a customer could follow to geo-replicate the data themselves, by provisioning multiple registries? Or would this be too hard to keep in sync? -->
109109

110+
<!-- Is there any way to back up/restore device registry data? -->
111+
110112
## Service-level agreement (SLA)
111113

112114
<!-- Does this service actually have an SLA? If so, where in the SLA document is this service? I can't see it, either as "IoT Operations" or "Device Registry". -->

0 commit comments

Comments
 (0)