@MAXTRANSFERSIZE, @BLOCKSIZE params are not supported when performing backups to URL #544
Unanswered
RoD-OlBilyk
asked this question in
Questions & Answers
Replies: 1 comment
-
There are some limitations when you are backing up to page blob. The solution is to switch to block blob and Shared Access Signature. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
EXECUTE master.dbo.DatabaseBackup @databases = 'exampleDB', @BackupType = 'LOG' ,
@compress = 'Y', @Encrypt = 'Y', @EncryptionAlgorithm = 'AES_128', @ServerCertificate = 'SomeCert',
@verify = 'Y', @LogToTable='Y',
@url = 'https://example.blob.core.windows.net/example', @credential = 'https://example.blob.core.windows.net/example',
@MaxTransferSize = 4194304,@Blocksize = 65536
Version: 2020-12-31 18:58:56
Source: https://ola.hallengren.com
generates errs as follows (but in reality, it is unhappy with @credential parameter (remove it & everything works perfectly). ).
Msg 50000, Level 16, State 4, Procedure master.dbo.DatabaseBackup, Line 2278 [Batch Start Line 4]
The value for the parameter @Blocksize is not supported.
Msg 50000, Level 16, State 4, Procedure master.dbo.DatabaseBackup, Line 2278 [Batch Start Line 4]
The value for the parameter @MaxTransferSize is not supported.
Msg 50000, Level 16, State 1, Procedure master.dbo.DatabaseBackup, Line 2278 [Batch Start Line 4]
The documentation is available at https://ola.hallengren.com/sql-server-backup.html.
Beta Was this translation helpful? Give feedback.
All reactions