Azure Blob Storage FAQs

To get started, you must first register your Azure subscription by logging in and accepting the required permissions. The setup process requires you to authorize the creation of Encryption Keys, which are used to encrypt your backups. Without this authorization, backups will fail for those subscriptions.

This means that when you configure Storage Rules to direct backups from an Azure Region to a Backup Storage location, that storage is permanently assigned to a resource when its first backup runs. It cannot be modified later.

The Restore interface has a search function that allows you to search for a blob, folder, or container name across all recovery points of a selected backup set. You can also use "Advanced Options" to search with more specific criteria, such as Blob Tag, File Type, File Size, File Extensions, or Date Modified.

When configuring a backup set, you can either choose to exclude specific blobs (based on file types, tags, or prefixes) or choose to include only specific blobs. You can select one or the other, but not both at the same time. The documentation notes that exclusion rules take precedence.

If a job fails, a "Critical" alert will be generated and it will appear in the Alerts section. You can click on the alert to view details which include the target backup set, a description of the failure, and a specific error message and error code. You can also find details about the job by navigating to the "Jobs" page.

Data Lock is a feature within a Backup Policy that prevents recovery points from accidental or malicious deletion. You can enable Data Lock when setting the retention rules for a policy. It is recommended to use this feature for enhanced security and to ensure your backups are immutable.