April 22, 2011 at 12:37 am
We have a full backup job and transaction log backup job for a server.
Full backup job is running every day at 11:50 PM and TX Log backup job Occurs every day every 1 hour(s) between 5:05:00 AM and 10:59:59 PM.
All backup (Full backup and TX Log backup) running fine except Saturday.
But three TX lob backup failed on Saturday between 8:06 PM to 10:09 PM and i found that at the same time re indexing job is running on server.From the job history i have confirmed that Re indexing job is starting at 8:02 pm every Saturday and take 3:05:00 hours to complete.
Only one particular database is failing that time. While Tx log backup occurs on other DB.
So i just want to know that does that cause the issue?
Thanks
April 22, 2011 at 12:48 am
what is the error that you see in job history for scheduled tnx job.
Regards,
MShenel
April 22, 2011 at 12:55 am
Error we are getting is there is no current database backup.
We never change recovery model and current database backup is there.
Attached screenshot for the error.
Thanks for quick reply
April 22, 2011 at 2:03 am
If this is with only one single database? I think there is some issue with database. Check the SQL Server error log what does that say? Run DBCC CHECKDB on the failed DB. Try to run manually the full backup followed by Tlog backup if that is successfull ,this might be VDI issue too check with their support too.
"More Green More Oxygen !! Plant a tree today"
April 22, 2011 at 3:23 am
EasyBoy (4/22/2011)
Error we are getting is there is no current database backup.We never change recovery model and current database backup is there.
Attached screenshot for the error.
Thanks for quick reply
The Job is running under which account? is that account have the proper permission to database as well as msdb and write permission to folder where you want to put the backup file's?
Also try manually log backup as Minaz Amin said.
Ali
MCTS SQL Server2k8
April 22, 2011 at 3:57 am
The "No current database backup" error means one of two things:
There's a switch to simple recovery and back to full somewhere between the last successful log backup and the failed one.
There's a backup log ... truncate only (SQL 2005 only) somewhere between the last successful log backup and the failed one.
It's not permissions, it's not corruption.
Check the index rebuild job, it's not uncommon to find that those switch the recovery model before they start.
Check the SQL error log, all changes of recovery model are logged.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 22, 2011 at 3:59 am
whats the Version of SQL Server?
Is there any activity if some one changed the model and then changed backup to the previous one ?
Last Full backup is done successfully ?
Regards,
Syed Jahanzaib Bin Hassan
MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply