Monday, February 20, 2012

MSDB Backup Fails on SQL Server 7.0

I'm having the following problem with the backup I have running on our
SQL Server. I have it scheduled to run once a week and when I check
the event viewer I see the following:
SQL Server Scheduled Job 'msdb backup'
(0x1DA8D66C8D076D4D973B1AF97C122CA7) - Status: Failed - Invoked on:
8/13/2006 12:00:00 AM - Message: The job failed. The Job was invoked
by Schedule 4209 (Schedule 1). The last step to run was step 1 (Step
1).
Event ID: 208
The script I'm using for my backup is as follows:
BACKUP DATABASE [msdb] TO [H:\SQLServerBackUpNBR] WITH NOINIT ,
NOUNLOAD , NAME = N'msdb backup', SKIP , STATS = 10, NOFORMAT
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='msdb'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='msdb')
RESTORE VERIFYONLY FROM [H:\SQLServerBackUpNBR] WITH FILE = @.iCan you post the Error / message from the step 1: of this job. That
probability gives more info. regarding the failure.
-Saravanan
"Creative" <GraberJ@.gmail.com> wrote in message
news:1155651035.260790.231840@.i42g2000cwa.googlegroups.com...
> I'm having the following problem with the backup I have running on our
> SQL Server. I have it scheduled to run once a week and when I check
> the event viewer I see the following:
> SQL Server Scheduled Job 'msdb backup'
> (0x1DA8D66C8D076D4D973B1AF97C122CA7) - Status: Failed - Invoked on:
> 8/13/2006 12:00:00 AM - Message: The job failed. The Job was invoked
> by Schedule 4209 (Schedule 1). The last step to run was step 1 (Step
> 1).
> Event ID: 208
> The script I'm using for my backup is as follows:
> BACKUP DATABASE [msdb] TO [H:\SQLServerBackUpNBR] WITH NOINIT ,
> NOUNLOAD , NAME = N'msdb backup', SKIP , STATS = 10, NOFORMAT
> DECLARE @.i INT
> select @.i = position from msdb..backupset where database_name='msdb'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset where database_name='msdb')
> RESTORE VERIFYONLY FROM [H:\SQLServerBackUpNBR] WITH FILE = @.i
>|||Are you referring to within SQL Server? Sorry I'm a little new at
troubleshooting SQL Server and I'm not sure where the error message is
you're looking for. All I can find is the one in the Event Viewer that
I posted below and the other is when I view Job History I see "The job
failed. The Job was invoked by Schedule 4209 (Schedule 1). The last
step to run was step 1 (Step 1)." which tells me nothing.
If this isn't what you wanted please tell me where to find what you are
referring to.
Thanks
Saravanan Palanivelu wrote:[vbcol=seagreen]
> Can you post the Error / message from the step 1: of this job. That
> probability gives more info. regarding the failure.
>
> -Saravanan
>
> "Creative" <GraberJ@.gmail.com> wrote in message
> news:1155651035.260790.231840@.i42g2000cwa.googlegroups.com...|||Ok here is the error message from the Job History File. Any
suggestions would be appreciated.
No entry in sysdevices for backup device 'H:\SQLServerBackUpNBR'.
Update sysdevices and rerun statement. [SQLSTATE 42000] (Error 3206)
Backup or restore operation terminating abnormally. [SQLSTATE 42000]
(Error 3013) Associated statement is not prepared [SQLSTATE HY007]
(Error 0) No entry in sysdevices for backup device
'H:\SQLServerBackUpNBR'. Update sysdevices and rerun statement.
[SQLSTATE 42000] (Error 3206) Backup or restore operation terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Creative wrote:[vbcol=seagreen]
> Are you referring to within SQL Server? Sorry I'm a little new at
> troubleshooting SQL Server and I'm not sure where the error message is
> you're looking for. All I can find is the one in the Event Viewer that
> I posted below and the other is when I view Job History I see "The job
> failed. The Job was invoked by Schedule 4209 (Schedule 1). The last
> step to run was step 1 (Step 1)." which tells me nothing.
> If this isn't what you wanted please tell me where to find what you are
> referring to.
> Thanks
>
> Saravanan Palanivelu wrote:

No comments:

Post a Comment