Comments
Sort by recent activity
Looks like something may be amiss in the header. Could you pls post the header information of the first backup file (LOG_(local)_Bigben_20050701 030002.sqb) using the RESTORE SQBHEADERONLY ... command? Thanks.
As you may have noticed, there is a bug in SQL Backup in that it does not report SQL Server errors, only errors that it encounters itself. That is why the status code returned is 0 (successful) even though this was not the case. This will be fixed in a future version. / comments
Looks like something may be amiss in the header. Could you pls post the header information of the first backup file (LOG_(local)_Bigben_20050701 030002.sqb) using the RESTORE SQBHEADERONLY ... co...
Try separating the recipients with a semicolon e.g. ... MAILTO = [recipient1@host1.com;recipient2@host1.com;recipient3@host2.com] ...
/ comments
Try separating the recipients with a semicolon e.g.... MAILTO = [recipient1@host1.com;recipient2@host1.com;recipient3@host2.com] ...
Could you repeat the same tests, but this time, instead of using SQL Backup to perform the differential backup, could you try using the SQL Server to perform the differential backup? Do your get the same results?
Thanks. / comments
Could you repeat the same tests, but this time, instead of using SQL Backup to perform the differential backup, could you try using the SQL Server to perform the differential backup? Do your get t...
I can only guess that the transaction at 12:40 PM was not committed by 1 PM, hence it wasn't visible in the read-only database.
If you can reproduce this situation easily, you could try changing some records using your application, then use Query Analyzer/SSMS to verify if the changes are immediately committed. I wouldn't use the application itself to check, just in case they run using the read-uncommitted isolation level or lower (I used to work on an ERP software that actually did this).
Thanks. / comments
I can only guess that the transaction at 12:40 PM was not committed by 1 PM, hence it wasn't visible in the read-only database.
If you can reproduce this situation easily, you could try changing so...
It appears to be a permissions issue. Can you confirm that the SQL Backup Agent service startup account has the necessary rights to that folder? Can you try backing up to another folder that everyone has read/write rights to, just to check that SQL Backup is working correctly?
Thank you. / comments
It appears to be a permissions issue. Can you confirm that the SQL Backup Agent service startup account has the necessary rights to that folder? Can you try backing up to another folder that every...
The extended stored procedure returns a failure status if SQL Backup encounters any errors or warnings. In this case, a warning was raised because one of the mirror files failed to be created.
An option may be to use the command line executable instead, and use the exit code value to check for warnings/errors, as warnings are in the range 1 to 499. Admittedly, this is a little cumbersome to work into a script.
I've logged an issue to propose that future extended stored procedures return an output value that indicates the actual warning/error code. / comments
The extended stored procedure returns a failure status if SQL Backup encounters any errors or warnings. In this case, a warning was raised because one of the mirror files failed to be created.
An ...
Usage of the -I parameter from within the extended stored procedure is not really intuitive, and will not be necessary in future versions. / comments
Usage of the -I parameter from within the extended stored procedure is not really intuitive, and will not be necessary in future versions.
Use the same parameters as you would for the command line i.e. use the -I parameter to specify an instance name e.g.
master..sqlbackup '-sql "BACKUP DATABASE pubs TO DISK = [Z:\sqlrec\pubs.sqb]" -I INSTANCE2' / comments
Use the same parameters as you would for the command line i.e. use the -I parameter to specify an instance name e.g.
master..sqlbackup '-sql "BACKUP DATABASE pubs TO DISK = [Z:\sqlrec\pubs.sqb]" -I...
I apologize for not posting a follow-up. The private message was not a resolution but a request for more (possibly) sensitive information from the user to troubleshoot the error.
The conclusion is that this is an annoyance in the GUI when running on clusters. SQL Backup tries to connect to every instance of SQL Server that it finds on a machine, and when it fails to connect, an error is raised.
On a regular server, most instances are running so this is not a problem. On a cluster however, there are probably some failover instances on each node, so they are inactive most of the time.
The 'fix' for this in a future version is to not raise these errors so aggresively if running on a cluster. / comments
I apologize for not posting a follow-up. The private message was not a resolution but a request for more (possibly) sensitive information from the user to troubleshoot the error.
The conclusion is...
Pls see private message. Thx. / comments
Pls see private message. Thx.