Versions Compared

Old Version 27

changes.mady.by.user Alejandra Rivera

Saved on

compared with

New Version Current

changes.mady.by.user Alejandra Rivera

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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
    aliashere
    urlhttps://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
    aliaslink
    urlhttps://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
    aliashere
    urlhttps://azure.microsoft.com/en-us/documentation/articles/storage-create-storage-account/#view-and-copy-storage-access-keys
    .
  • 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.

...

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:

...

    • .
  • Restart all SQL Safe services on the machine.

    • If there are network connection problems, the backup eventually fails, but files remain on Windows Azure. SQL Safe will not delete these partial backup files. If you want to delete those, you need to do it manually on your Azure account.

    Tip
    When Azure Blob Storage settings are defined in the Configure General Preferences section, they can be reused later through different backups and restores.

    ...

    The Microsoft Azure Blob service is based on a flat storage scheme, not a hierarchical scheme. However, SQL Safe allows you to specify subfolders which 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.

    ...