GregE
ADSM.ORG Senior Member
On on of our SQL servers (SQL Express) we are having intermitted backup issues and I think we have determined the reason, though I don't understand it. None of our other servers have this issue.
When the backup fails, TSM TDP logs show this for each of the DBs that won't backup (normally it's all of them, except for the system DBs which are always ok).........
ACO5422E Received the following from the MS SQL server:
Specified cast is not valid. (HRESULT:0x80004002)
Backup of SQL DB1 will not be attempted.
The owners of this server sent me this info that they see during the backup......
2012-03-02 03:05:23.60 spid51 Starting up database 'DB1'.
2012-03-02 03:05:24.43 spid51 Recovery is writing a checkpoint in database 'DB1' (5). This is an informational message only. No user action is required.
2012-03-02 03:05:24.56 spid51 Starting up database 'DB2'.
2012-03-02 03:05:25.16 spid51 Starting up database 'DB3'.
2012-03-02 03:05:26.33 spid51 Recovery is writing a checkpoint in database 'DB3' (9). This is an informational message only. No user action is required.
2012-03-02 03:05:26.53 spid51 Starting up database 'DB4'.
2012-03-02 03:05:27.49 spid51 Starting up database 'DB5'.
When the backups work correctly, it's because they are already "started" and TSM TDP doesn't try to do that. They reboot the server every night, and after reboot, the SQL DBs are not "started."
They are trying to figure out how to have the DBs started before the backup since it seems to be the reason that the backup fails.
Has anyone dealt with this?
When the backup fails, TSM TDP logs show this for each of the DBs that won't backup (normally it's all of them, except for the system DBs which are always ok).........
ACO5422E Received the following from the MS SQL server:
Specified cast is not valid. (HRESULT:0x80004002)
Backup of SQL DB1 will not be attempted.
The owners of this server sent me this info that they see during the backup......
2012-03-02 03:05:23.60 spid51 Starting up database 'DB1'.
2012-03-02 03:05:24.43 spid51 Recovery is writing a checkpoint in database 'DB1' (5). This is an informational message only. No user action is required.
2012-03-02 03:05:24.56 spid51 Starting up database 'DB2'.
2012-03-02 03:05:25.16 spid51 Starting up database 'DB3'.
2012-03-02 03:05:26.33 spid51 Recovery is writing a checkpoint in database 'DB3' (9). This is an informational message only. No user action is required.
2012-03-02 03:05:26.53 spid51 Starting up database 'DB4'.
2012-03-02 03:05:27.49 spid51 Starting up database 'DB5'.
When the backups work correctly, it's because they are already "started" and TSM TDP doesn't try to do that. They reboot the server every night, and after reboot, the SQL DBs are not "started."
They are trying to figure out how to have the DBs started before the backup since it seems to be the reason that the backup fails.
Has anyone dealt with this?
