October 10, 2018 at 2:04 pm
Hi All
Error: "Log was restored. Database: TestDB creation date(time): 2018/06/27(17:59:45), first LSN: 263:2036:1, last LSN: 263:2042:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\M01\logshipping\Test_DB_a04c286990e3f45b29.trn'}). This is an informational message. No user action is required."
Issue: "I have one of the backup maintenance job failing once a week and it "runs again fine without any issues"...I checked the sql server logs and do not see anything happening at the same time when job failed however in event log ( windows) I see a log was restored ( Above message) at same time".
My Question : since the log was being restored ( log shipping) will that can impact the maintenance plan Job which is trying to run at the "same time"? Please let me know your thoughts...!
October 10, 2018 at 3:11 pm
If you are trying to backup the database, it must be available. If you have log shipping, you cannot make a backup of a database in standby or norecovery mode. If this is working some of the time, are you taking the database out of recovery?
October 10, 2018 at 3:34 pm
No, not taking the database out of recovery. Thanks
October 12, 2018 at 5:04 pm
sizal0234 - Wednesday, October 10, 2018 3:34 PMNo, not taking the database out of recovery. Thanks
What is the maintenance you are performing on the log shipped database when the log is being restored? Are you in standby mode doing DBCC CHECKDB or what?
Sue
October 17, 2018 at 2:25 pm
I think we are in standby mode doing DBCC CHECKDB.
October 17, 2018 at 4:41 pm
sizal0234 - Wednesday, October 17, 2018 2:25 PMI think we are in standby mode doing DBCC CHECKDB.
You probably need to know how you have your log shipping implemented and exactly what was running in the jobs to figure out why the one failed.
Likely the database was in the middle of a log restore and it wasn't accessible.
Sue
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply