#5 Transactionlog backup error

[Michel van der Voort]

We use tooling around MSBP to read errors occuring while making backups with MSBP.
When we attempt to make a backup of an OFFLINE database there is a decent error message stating (e.g) :
Database 'mytestdb' cannot be opened because it is offline.
Since we filter the STDOUT file on the databasename being backupped, that works fine.
But, when we make a transactionlog backup for the same database, there is no errorline containing the name of the database, so we do not get any decent error message.
The only result is (summarized) :
Exception #1
Invalid attempt to read when no data is present.
NULL
System.InvalidOperationException
...
...

Can you please make a change to the transactionlog backup error handling, so it states what went wrong AND report the databasename ?

I hope you can

Regards,

Michel

[Clay Lenhart]

In general the error handling could be much better. It is too verbose and needs a summary analysis of what went wrong in terms of what the user sees, not the internal components.

Unfortunately I am busy at the moment and can't spend time on this for at least several months. Patches are welcome, especially ones like this that shouldn't have a big impact. (Larger impact patches would take more of my time -- though I'd love them too). The easiest way to submit patches is to download the source, make changes and email me your code (including the .hg directory).

Something that might interest you, the MSBackupPipe.Common.dll is designed to be UI independent, and you may find it easier to integrate with this instead. And if you want raw SQL Server VDI access, there is MSBackupPipe.VirtualBackupDevice.dll as well.

[Clay Lenhart]

I wonder if it would be useful to you to get feedback from stdout in XML format -- either success, or the error details if there is an error, including the context such as the database name.

[Michel van der Voort]

What would be really helpfull (for now) would be that the transactionlog backup reports an error similar to the one mentioned coming from the database backup.
Sinc ewe monitor systems with a combination of Korn shell scripting and SQL Server SQL commands we filter the STDOUT with a KSH grep command looking for the name of the database.
This way we can check for Completed Succesfully messages and if that is not there CAT the STDOUT file filtering on DBNAME.

I hope you can make this (simple ?) change

Regards,

Michel