April 24, 2006 at 8:44 am
I have several instances of SQLSERVER 2000 on a server ( windows 2003).
There are db maintenance plans create.
for some reason, the transaction logs back up jobs errors out. Upon further checking I split the simple/full logged dbs into 2 maintenance plans. The full dbs are backed up but not the simple: Get the generic error on the job history:
Executed as user: <username> sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Windows Event log show a warning: Event Id 208
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan 'System Databases Maintenance Plan'' (0x71C719D675D7A543BE4DE1BF32F5F39C) - Status: Failed - Invoked on: 2006-04-24 10:25:09 - Message: The job failed. The Job was invoked by User <username>. The last step to run was step 1 (Step 1).
For more information, see Help and Support Center at
Not sure why this fails ??
My system dbs: master/model/msdb are set to simple recovery on all the instances
April 24, 2006 at 8:54 am
Hi, you need to read Books Online (BOL) for an explanation of recovery modes. You cannot backup the transaction log of a database with simple recovery mode as the transaction log is truncated .
April 24, 2006 at 9:11 am
Found this out: simple dbs having transaction log backed up does not make sense:
Do I need to have system dbs: master/model/msdb set to full recovery?
These can remain simple as long as I have the db backed up: MDFs. Any pros/cons on this ?
April 24, 2006 at 9:16 am
hi,
in my experience it is usual to have system databases set to simple recovery, with a daily full backup.
Paul
April 24, 2006 at 9:26 am
I have these set to same: full backup:daily. So I would nto worry too much: jult remove the transaction backup job.
thanks ripq1011
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply