August 12, 2014 at 7:06 am
Hi,
I want to know about database recovery in critical situation.
Configured full back-up on daily basis at 12:00 PM.
1. I have full back-up on Monday and followed by Transaction log
2 .Unfortunately I missed Tuesday full back-up. But I have transaction log till Tuesday at 3:00 PM.
Server was some issues at 3:30 PM, and data file not able to access due to disk level corruption happened and not able to take backup also.
In this scenario, how can we recovery database in point-in-time?
Thanks
ananda
August 12, 2014 at 7:22 am
Do you have every single transaction log backup from the Monday full backup up to now? Every single one without a gap?
Has the database been set to simple recovery at any point between the monday full backup and now?
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
August 12, 2014 at 11:31 pm
Let me explain more details about data recovery in critical situation
As per backup Plan
1. Daily one Full backups at 12:00 AM configured
2. Every 30 minutes Transaction log backup configured
Critical situation 1
I have two set of full backup file (Monday and Tuesday) and on Tuesday transaction log backup file available till at 3:00 PM
On Tuesday, Server was some issues at 3:30 PM, and database not able access also not able take Tail log backup at event of server failure.
In this scenario, how can we recovery database in point-in-time?
For the data recovery, first restore Tuesday full backup and followed restore the all TLOG backup file till 3:00 PM.
So we accepted 30 minutes data loss and can able to restore the data till 3:00 PM only. Am I correct?
Critical situation 2
1. Unfortunately Tuesday full backup file missed.
2. Monday I have all transaction log backup and Full back-up, on Tuesday I have only transaction log backup’s till 3:00 PM.
On Tuesday, Server was some issues at 3:30 PM, and data file not able to access due to disk level corruption happened and database can accessible. But not able to take full and Tail log backups
In this scenario, how can we recovery database in point-in-time?
For the data recovery, LSN chain was broken due to Tuesday full backup. So how can restore the Tuesday TLOG backup’s files on followed by restore the Monday full backup.
Thanks
ananda
August 13, 2014 at 12:55 am
Case 1, correct. If you can't take a tail-log backup, then you can only restore to the last log backup you have.
Case 2, Full backups DO NOT and NEVER have broken the log chain. Ever. Restore Monday's full then all log backups up to the last one you have.
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
August 13, 2014 at 1:37 am
Thank you for confirmation,
Case 2. we can restore point in time recovery by using perivious day full backup also apply all second day tlogs backups file even if lost second day full backup.
So in this case 2. I have to take care all Sequential log backup files. so i could't resotre point in time If log chain broken between.
what could be reason log chain will be broken?
August 13, 2014 at 2:13 am
SQL Galaxy (8/13/2014)
what could be reason log chain will be broken?
Missing log backup file (deleted) or the DB was switched to simple recovery sometime during that time period.
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
August 13, 2014 at 5:21 am
In such critical situation you must go with reliable and effortless recover tool.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply