Discrepancy may exist between the reported amount of blob storage space utilized by JetStream DR and Azure portal. The following example shows the JetStream DR UI reporting 271KB of used space while Azure portal reports 41.2TB.


Troubleshooting
- Validate and ensure Azure soft delete functionality is enabled for the blob storage account.
- When enabled, soft delete retains deleted data according to a designated retention period.
- When enabled, soft delete retains deleted data according to a designated retention period.
- From the JetStream DR interface, data is reported in compressed form reflecting actual data after replication and garbage collection deletions.
- JetStream DR lacks visibility or accountability regarding data headers managed by Azure blob data protection features.
- The Jetstream DR UI indicates utilized blob space on a per-instance basis.
- For example, if the same blob storage is utilized across multiple JetStream DR protected sites, each JetStream DR instance will only display its own individual amount of usage, rather than indicating the combined usage of all sites contributing to the blob store.
- For example, if the same blob storage is utilized across multiple JetStream DR protected sites, each JetStream DR instance will only display its own individual amount of usage, rather than indicating the combined usage of all sites contributing to the blob store.