Page History
...
- Container Name - the name of the Azure container where the new blob will be created and the backup stored. Every Azure blob must reside in a container. The container forms part of the blob name. If no container with the input name exists, a new one will be created. For more information, click
.Newtablink alias here url https://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-how-to-use-blobs/#create-a-container - Azure Storage Account Name - the account name of your storage account. Every object that you store in Azure Storage has a unique URL address. The storage account name forms the subdomain of that address. You can find more information in on the following
.Newtablink alias link url https://azure.microsoft.com/en-us/documentation/articles/storage-create-storage-account/#storage-account-endpoints - Azure Access Key - you can use any of the access keys provided to your Azure Storage Account. For more information about Azure Keys, click
.Newtablink alias here url https://azure.microsoft.com/en-us/documentation/articles/storage-create-storage-account/#view-and-copy-storage-access-keys - Sector Type - define the Azure sector: public or government.
...
By default, SQL Safe Backup splits the backup into several files, each with size of 70MB.
You can configure the file size by updating the Windows Registry on the machine hosting the SQL Safe Backup Agent using the following steps:
- Add a new registry REG_DWORD key to HKEY_LOCAL_MACHINE\SOFTWARE\Idera\SQLsafe named AzureFileSize.
- Update the AzureFileSize key to a decimal value of your desired file size. For example, if you want the default file size to be 100MB, the key value should be set to 100.
- Restart all SQL Safe services on the machine.
...
- SubFolder(s) (Optional) - specify where your backup will be stored or restored from. Consider the following situations:
- If the SubFolder field is left empty, the backup file will be saved in the root of the specified container.
- If the SubFolder field is populated with the name of a folder that does not exist on the storage container \ bucket, the folder will be created and the backup file will be saved to the specified Subfolder.
- Multiple SubFolders can be specified by separating each folder with a forward slash: MyFolder/MySubfolder/MyNestedFolder.
- The SubFolder field can contain static values as well as tokens like %instance%, %database%, %backuptype%, %policyguid%,and %timestamp%.
- Sector Type - define the Azure sector type:
- Public - commercial cloud storage solution.
- Government - cloud storage solution offered to US government customers and their partners.
| Tip |
|---|
| When Azure Blob Storage settings are defined in the Configure General Preferences section, they can be reused later through different backups and restores. |
...
Naming conventions for containers
Taken Take into account the following naming conventions for your container:
- All letters should be in lowercase.
- The container name should be a valid DNS name.
- Names have to start The container name should start or end with a letter or number and can contain only letters, numbers, and the dash (-) character.
- Every dash (-) character must be immediately preceded and followed by a letter or number. Consecutive dashes are not permitted in container names.
- All letters should be in lowercase.
- Names can be from three to sixty-three characters long.
Naming
...
your SQL Safe backup files on Microsoft Azure blob storage
Take into account the following blob naming rules:
A blob name can contain any combination of characters.
A blob name must be at least one character long and cannot be more than 1,024 characters long.
Blob names are case-sensitive.
The number of subfolders cannot exceed 254.
Avoid filenames that end with a dot (.), a forward slash (/), or a sequence or combination of the two.
The Microsoft Azure Blob service is based on a flat storage scheme, not a hierarchical scheme. However, SQL Safe allows you to specify subfolders that act as a virtual hierarchy. If you store a large number of blobs in your Azure container then it is recommended to utilize subfolders to improve SQL Safe performance
The maximum size for a blob is 70MB. If a backup file is, for example, 160 MB, multiple blobs will be created using the following naming format:
- <blobname>.safe_<i> where <i> is the blob counter
If the blob name is testdb for example, the three blobs created in the container will have the following names: testdb.safe_1 (70MB), testdb.safe_2(70MB), testdb.safe_3(20MB).