Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-09-26 : 07:50:41
|
| Prabhaakar B writes "Hello Sir, I have read the SQL Books online and it says that " You can restore the Db to the point of failure, provided you have the current transactional log intact on a fault tolerant disk".Now the question...1)Say every sunday night there is a full db backup.2)Every night there is a transactional log backup.3)Now my db fails on say Tuesday afternoon 2.pm. say.Now i will restore the sunday full backup and apply monday's transaction log backup. Now to get db as on Tuesday afternoon 2 pm i need to restore the current transaction log from the fault tolerant disk. But i cant restore the current transaction log because i dont have it backed up(because the transaction log backup is taken every night only). To back it up now i dont have my mdf file intact because its been damaged. How to make the db now compatible as on tuesday afternoon 2 p.m???Prabhaakar B" |
|
|
franco
Constraint Violating Yak Guru
255 Posts |
Posted - 2003-09-26 : 08:55:19
|
| For what I know in order to restore to a point in time you need to backup t-log as often as possible.I mean if you can affoard to loose one hour of work you can set up a t-log backup every hour or, if you can affoard to loose only 5 minutes of work, you have to set up a t-log backup every 5 minutes.It's clear that if something damage your database 2 hours ago, you can only restore to that point in time, the time when accident happen.Log Explorer from Lumigent (www.lumigent.com) can help you in undo a bad transaction.Regards.Franco |
 |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2003-09-26 : 11:12:43
|
| OK, I'm a little rusty on this, but as I recall, the key is not running a transactional log backup every 5 minutes, but rather, BEFORE you begin your restore, you need to save the transaction logs at the time of failure. Then you restore your full, the t-log backups, and finally the t-log at the point of failure.Keep reading in BOL, I'm sure it's in there.------------------------------------------------------The more you know, the more you know you don't know. |
|
|
|
bm1000
Starting Member
37 Posts |
Posted - 2003-09-26 : 11:54:17
|
quote:
Originally posted by AskSQLTeam
Prabhaakar B writes "Hello Sir, I have read the SQL Books online and it says that " You can restore the Db to the point of failure, provided you have the current transactional log intact on a fault tolerant disk".Now the question...1)Say every sunday night there is a full db backup.2)Every night there is a transactional log backup.3)Now my db fails on say Tuesday afternoon 2.pm. say.Now i will restore the sunday full backup and apply monday's transaction log backup. Now to get db as on Tuesday afternoon 2 pm i need to restore the current transaction log from the fault tolerant disk. But i cant restore the current transaction log because i dont have it backed up(because the transaction log backup is taken every night only). To back it up now i dont have my mdf file intact because its been damaged. How to make the db now compatible as on tuesday afternoon 2 p.m???Prabhaakar B"
I think that the command you want is:Backup log with no_truncateIt tells SQL Server to backup the tran log, but not to try to access the database files since they are damaged or gone. |
|
|
|
|
|
|
|
|
Difficulty in Restoring the Db to the point of Failure.