Activity overview
Latest activity by KHartman
When I run this against my db from QA, this is my result... not finding the stored procedure....
Statement
sqlbackup '-sql "RESTORE HEADERONLY FROM DISK = [E:\FULL_(local)_XXXXXKLH_20061110_075654.sqb] " '
Result
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sqlbackup'.
Unless I am running this wrong.. / comments
When I run this against my db from QA, this is my result... not finding the stored procedure....
Statement
sqlbackup '-sql "RESTORE HEADERONLY FROM DISK = [E:\FULL_(local)_XXXXXKLH_20061110_075654....
Yes, the agent has full rights to the share. The SQLagent, BACKUPagent, and SQLSERVERagent all use the same domain ID. Essentially the same config used on the other servers that backup to the same share drive.
I have done some more experimentation as well in the mean time... I can successfully reroute a backup from one of the other servers to the shared folder in question, and restore that to the original database. However, I CAN NOT restore that same backup to a database on the problem server. I also tried to restore a backup from the problem server to a test database on another server, and was able to do that successfully.
Everything seems to point to a problem somewhere on the database server in question. The share seems fine, the agents are synched and have permissions, backups to and from other servers are fine, backups from other servers to the share folder of the server in question seem fine, all SQLServer versions are the same, and while the backup job "fails" the backups seem to be writing and completing with this "300" warning in the log.
The only thing I can't do is restore any database on the problem server, which pretty much makes the whole backup routine useless for that environment. I even blew away all the backup jobs and rebuilt them, only to achieve the same results. I am thinking now of re-installing the RedGate on that server, but that seems rather drastic for something that was working fine and now isn't.
Any other ideas? / comments
Yes, the agent has full rights to the share. The SQLagent, BACKUPagent, and SQLSERVERagent all use the same domain ID. Essentially the same config used on the other servers that backup to the sam...
Thanks Brian...
Well, I guess that makes sense, however, these are all SQL2000 databases... Over the weekend, I did a defrag of the share drive, and moved the "free" segment from 2.3M to 3.7M, but since the first threshold is 6MB according to what I have read, I have the same results on a test backup. I still can't figure out why the other servers backing up on the same share to a different folder seem to be working fine...
Kevin / comments
Thanks Brian...
Well, I guess that makes sense, however, these are all SQL2000 databases... Over the weekend, I did a defrag of the share drive, and moved the "free" segment from 2.3M to 3.7M, but...
Exit code 300 puzzle
I am having a problem with my full backup routine which errors as follows..
SQL Backup job failed with exitcode: 300 SQL error code: 0 [SQLSTATE 42000] (Error 50000). The step failed.
From other ...