Backups = Yes, T-Logs = No

[BlakeK]

SQL 2000, all patches...

We recently created a new database, and I added it to the job that I have created for all the other user databases, to do backups, transaction logs, integrity checks, etc.
I did this simply by opening the Database Maintence Plan that was already in existence, and checked off the new database that had been created.

The optimizations, integrity checks, and full backups are running successfully. But the job for the tranaction log backup is failing.
In the log report, all it says is:
"Backup can not be performed on database 'ADCO1'. This sub task is ignored."

That's real helpful!!

The log report for the successful full backup is as follows:

[9] Database ADCO1: Database Backup...
Destination: [E:\ADCO1_db_200409131719.BAK]

** Execution Time: 0 hrs, 0 mins, 9 secs **

[10] Database ADCO1: Verifying Backup...

** Execution Time: 0 hrs, 0 mins, 3 secs **

Any ideas on why the transaction log backup would be failing? Any more info I can provide to help trouble shot this?

Thanks,
Blake

 

[nigelrivett]

Is the new database using simple recovery model?

Don't use maint plans - code it yourself and you won't get these problems.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.

 

[SQLBill]

Use Enterprise Manager, right click on the database, select Properties and go to the Options tab. Then, as nigel suggests, check your Recovery Mode for the database. If it's in SIMPLE mode you cannot backup the transaction log.

-SQLBill

 

[BlakeK]

You guys were right on!
I changed it to Full, and the Transaction Log backup ran perfectly.

Thanks for your help.