SQL Backup 4.2 Build 511 - new keyword MAXTRANSFERSIZE
HJoyce
Posts: 186
There is an updated version of the server side components which offers a new keyword, MAXTRANSFERSIZE.
Download from: ftp://ftp.red-gate.com/SQB4.2.0.511.zip
Copy SQBServerSetup.exe and SQLBackupC.exe to the installation directory. To upgrade the server components run SQBServerSetup.exe. Alternatively you can upgrade each instance from the GUI by selecting the SQL Server instance in the left hand panel, right click and select Install/upgrade server components
MAXTRANSFERSIZE indicates to SQL Server the maximum size of each block of memory that it uses to store backup data, prior to SQL Backup compressing/encrypting the data.
Options are:
MAXTRANSFERSIZE = 1048576 (1 MB) (default)
MAXTRANSFERSIZE = 524288 (512 KB)
MAXTRANSFERSIZE = 262144 (256 KB)
MAXTRANSFERSIZE = 131072 (128 KB)
MAXTRANSFERSIZE = 65536 (64 KB)
For example,
master..sqlbackup N'-SQL "BACKUP DATABASE [DatabaseA] TO DISK = ''<AUTO>'' WITH COMPRESSION = 1, MAXTRANSFERSIZE = 524288"'
master..sqlbackup N'-SQL "RESTORE DATABASE [DatabaseA] FROM DISK = ''C:\DatabaseA.sqb''WITH RECOVERY, MAXTRANSFERSIZE = 262144"'
This is particularly useful if you experience an error such as "Failed to close vdi".
In this case the VDI.log will show for example
"Error at ServerBufferAreaManager::Allocate: Map buffers Status Code: 8, x8
Explanation: Not enough storage is available to process this command."
In this case you can use the MAXTRANSFERSIZE keyword with a lower value than the 1MB default, e.g. MAXTRANSFERSIZE = 524288
Download from: ftp://ftp.red-gate.com/SQB4.2.0.511.zip
Copy SQBServerSetup.exe and SQLBackupC.exe to the installation directory. To upgrade the server components run SQBServerSetup.exe. Alternatively you can upgrade each instance from the GUI by selecting the SQL Server instance in the left hand panel, right click and select Install/upgrade server components
MAXTRANSFERSIZE indicates to SQL Server the maximum size of each block of memory that it uses to store backup data, prior to SQL Backup compressing/encrypting the data.
Options are:
MAXTRANSFERSIZE = 1048576 (1 MB) (default)
MAXTRANSFERSIZE = 524288 (512 KB)
MAXTRANSFERSIZE = 262144 (256 KB)
MAXTRANSFERSIZE = 131072 (128 KB)
MAXTRANSFERSIZE = 65536 (64 KB)
For example,
master..sqlbackup N'-SQL "BACKUP DATABASE [DatabaseA] TO DISK = ''<AUTO>'' WITH COMPRESSION = 1, MAXTRANSFERSIZE = 524288"'
master..sqlbackup N'-SQL "RESTORE DATABASE [DatabaseA] FROM DISK = ''C:\DatabaseA.sqb''WITH RECOVERY, MAXTRANSFERSIZE = 262144"'
This is particularly useful if you experience an error such as "Failed to close vdi".
In this case the VDI.log will show for example
"Error at ServerBufferAreaManager::Allocate: Map buffers Status Code: 8, x8
Explanation: Not enough storage is available to process this command."
In this case you can use the MAXTRANSFERSIZE keyword with a lower value than the 1MB default, e.g. MAXTRANSFERSIZE = 524288
Helen Joyce
SQL Backup Project Manager
Red Gate Software
SQL Backup Project Manager
Red Gate Software
Comments
SQL Backup Project Manager
Red Gate Software
SQL Backup exit code :1050
SQL error code:3202
Write on "SQLBACKUO_<string>" failed: 112(There is not enough space on the disk.)
Failed to close vdi
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
I tried ALL the suggested values for MAXTRANSFERSIZE, from 1 MB down to 64 KB, and got the same result.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
As I recall, the file was partially created, but I'm not sure how much was written (if any) or if the file was merely created, and not written to.
Thanks,
Linda
Yes you can get the latest version from ftp://ftp.red-gate.com/SQLBackupRescueBundle.zip
SQL Backup Project Manager
Red Gate Software