An error occurred while processing 'BackupMetadata' metadata for database

I have transferred a database from SQL 2000 to SQL 2005 and now I am getting an error when I try to run backup. I get there error "An error occurred while processing 'BackupMetadata' metedata for datase ID..." Does anyone have any suggestions on how to resolve this error?

whats there in the error log ? ? ?......also did you try to backup using T-SQL .......is the db accessible ? ? ? after you restored from SQL 2000......try running

dbcc checkdb........

|||

Below is the error log:

Failed-1073548784) Executing the query "BACKUP DATABASE [SURVIAC] TO DISK = N'C:\\DatabaseBackups\\DailyFull\\SURVIAC\\SURVIAC_backup_200707091051.bak' WITH NOFORMAT, NOINIT, NAME = N'SURVIAC_backup_20070709105151', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "An error occurred while processing 'BackupMetadata' metadata for database id 13 file id 65537.
Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE option.
BACKUP DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

The database is accessible and is being used. I ran checkdb and did not come up with anything. I haven't used T-SQL. I have only used enterprise manager and my maintenance plans.

|||

seems your db is corrupted i guess.........the error log states that metadata is inconsistent ........also it allows you to take transaction log backup by using the option WITH CONTINUE_AFTER_ERROR ........you have the following options,

1.Try to backup the db with T-SQL or

2.Take a tran log backup with the above option

3.If you have any recent full backup just restore it somewhere and test if you can take backup on that restored db....coz i doubt your db is corrupted....

|||

It looks like you could be hitting a problem where you have damaged pages in the backup. The default behavior under 2005 is for the backup to fail if the checksum can't be verified.

To see if it is the maintenance plan or not, first try to backup the database using your own T-SQL and not the maintenance plan.

Also, run your DBCC CHECKDB using your own T-SQL, not a maintenance plan.

How long ago did you move this from 2000 to 2005? Did you run a checkdb after that migration? How did upgrade the database? Have you done any successful backups since upgrading the database to 2005?

-Sue