Comments
Sort by recent activity
The backup file appears to have been correctly generated. When running the backup from the command line, you mentioned that it never ended either. Could you post the output you receive when running from the command line? I would like to see at which stage it appears to be 'hanging'. Thanks. / comments
The backup file appears to have been correctly generated. When running the backup from the command line, you mentioned that it never ended either. Could you post the output you receive when runni...
Just to confirm something in your last post: when you backup the database from the GUI, the backup completes but the log file is incomplete? Or is it incomplete only when you run it from the cmd line and QA?
If you run the same command from the cmd line but without the LOGTO option, do you encounter the same error? / comments
Just to confirm something in your last post: when you backup the database from the GUI, the backup completes but the log file is incomplete? Or is it incomplete only when you run it from the cmd l...
Can you run the following from the command line on the backup file that was created from the cmd line (not the GUI), to check if the backup file is 'complete'?
sqlbackupc -sql "RESTORE SQBHEADERONLY FROM DISK = '<your backup file>'"
Do the LSN numbers have any values? Thanks. / comments
Can you run the following from the command line on the backup file that was created from the cmd line (not the GUI), to check if the backup file is 'complete'?
sqlbackupc -sql "RESTORE SQBHEADERONL...
Thx for the update. / comments
Thx for the update.
This will not be changed in version 3 as on non-English systems, the 44 bytes need to cater for multi-byte character sets.
In version 4, the full name of the database (max 128 characters) will be stored as a unicode string. / comments
This will not be changed in version 3 as on non-English systems, the 44 bytes need to cater for multi-byte character sets.
In version 4, the full name of the database (max 128 characters) will be s...
Thx for reporting the bug. / comments
Thx for reporting the bug.
The problem is that database names are truncated to 22 characters in the SQL Backup file header block. For ERASEFILES to work, it needs to find an exact match for the database name.
This will be fixed in a future release. If you need this to work now on English operating systems, you can do the following, but note that this is an unofficial, unsupported workaround and has not been fully tested:
Using a hex editor, look for the following sequence in sqlbackup.exe and sqlbackupc.exe:
B916000000BA01000000
Change the value 16 (hex for 22) to 2C (hex for 44). You should find two occurences of this sequence. The first is for the instance name, and the second for the database name. Making both changes will then store the first 44 characters of the instance/database name in the SQL Backup file header block. / comments
The problem is that database names are truncated to 22 characters in the SQL Backup file header block. For ERASEFILES to work, it needs to find an exact match for the database name.
This will be f...
Try stopping and restarting the SQL Backup Agent service. If that doesn't work, try stopping and restarting the SQL Server service. If that still doesn't work, try rebooting the machine.
Thanks. / comments
Try stopping and restarting the SQL Backup Agent service. If that doesn't work, try stopping and restarting the SQL Server service. If that still doesn't work, try rebooting the machine.
Thanks.
Try installing the SQL Backup server components manually. To do this, copy the server components installer, SQBServerSetup.exe, from your client machine to the machine running the SQL Server instance. Run the setup there.
Thanks. / comments
Try installing the SQL Backup server components manually. To do this, copy the server components installer, SQBServerSetup.exe, from your client machine to the machine running the SQL Server insta...
You will need to use the ERASEFILES command. ERASEFILES_REMOTE only works on remote shares. Unfortunately, ERASEFILES will also apply the retention period to your primary backup folder. / comments
You will need to use the ERASEFILES command. ERASEFILES_REMOTE only works on remote shares. Unfortunately, ERASEFILES will also apply the retention period to your primary backup folder.