May 18, 2009 at 4:04 am
Dear experts,
Iam facing a big issues now. need to resolve this error very fast.
my DB is of 80Gb and its configured for Log Shipping. Actually the DB was in full and some one or somehow changed the recovery mode to SIMPLE.
And from then the LS process failed from two days. Can this be synchronized now. As i have made the settings to FULL.
I tried after recovery mode set to FULL. But when i run the LSBackup job am facing the below error report.
I need to backup and restore the database now to make the LS Process in synch..
-----------------------------------------------------------------------------------------------------\Duration00:00:06
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
2009-05-18 15:16:46.05Retrieved backup settings. Primary Database: 'AuditDB', Backup Directory: 'E:\PrimaryLogShippingServer', Backup Retention Period: 2880 minute(s)
2009-05-18 15:16:46.22Backing up transaction log. Primary Database: 'AuditDB', Log Backup File: 'E:\PrimaryLogShippingServer\AuditDB_20090518094646.trn'
2009-05-18 15:16:46.49*** Error: Backup failed for Server 'INCHNDB'. (Microsoft.SqlServer.Smo) ***
2009-05-18 15:16:46.49*** Error: An exception occurred while executing a Transact-SQL statement or batch.(Microsoft.SqlServer.ConnectionInfo) ***
2009-05-18 15:16:46.49*** Error: BACKUP LOG cannot be performed because there is no current database backup.
BACKUP LOG is terminating abnormally.(.Net SqlClient Data Provider) ***
2009-05-18 15:16:46.75----- END OF TRANSACTION LOG BACKUP -----
Exit Status: 1 (Error)
Cheers,
- Win
"Dont Judge a Book by its Cover"
May 18, 2009 at 4:37 am
Hate to say it, but I believe the backup chain was broken when the Recovery Mode was reset. This is probably why you can't continue with the log restores.
My advice is to get another full backup, restore it to your destination server, then start the log shipping over from that point on. I don't think you'll be able to fix the broken chain issue unless you do it from scratch.
May 18, 2009 at 5:44 am
That's right ! There is no way that you can synchronise the broken log chain.
You would have to re configure your Log shipping.
May 18, 2009 at 5:50 am
Yes,
The only thing i can do is backup and restore. But apart from that can't i restore or perform any backups on this db ?
Cheers,
- Win
"Dont Judge a Book by its Cover"
May 18, 2009 at 5:53 am
SQL_Monster (5/18/2009)
But apart from that can't i restore or perform any backups on this db ?
Sorry, did not get that. You should break the logshipping and start it again. I mean take a fresh full backup and ship the logs.
May 18, 2009 at 7:48 am
SQL_Monster (5/18/2009)
The only thing i can do is backup and restore. But apart from that can't i restore or perform any backups on this db ?
Not quite sure what you mean by this.
A log shipped server is in a constant state of restore, so I doubt you'd ever be able to back it up. Unless your problems are on your main server...
Is that what you're saying, that you can neither backup nor restore the main server?
You'll never be able to restore future backups to the log shipped server without breaking and restarting the process from scratch. But if it's the main server that's having a problem, that's a horse of a different (and more alarming) color.
May 18, 2009 at 9:23 pm
Thanks for all the inputs...
I Have reconfigured the LS again... Its working fine now...
Cheers,
- Win
"Dont Judge a Book by its Cover"
May 18, 2009 at 11:52 pm
SQL_Monster (5/18/2009)
Thanks for all the inputs...I Have reconfigured the LS again... Its working fine now...
It's our pleasure 🙂
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply