|
|
| naresh_sky 2002-12-14, 5:49 am |
| Hi to all...
The Problem i am not able to understand is that .When i read a book it states that you can read the transaction log after the server has crashed to get the database to the point of return just before crash.
well what i dont understand is that
if your server crashes. then that means your harddisk has gone for a toss.
if that is right then how can you read the
log file which is created in the harddisk
as a file.
please help me out from this confusion
thank's
naresh | |
| sjgross 2002-12-15, 10:16 pm |
| Hi Naresh,
I found the following link from Microsoft:
support.microsoft.com/servicedesks/ webcasts/wc120500/WC120500.ppt
It talks a bit about recovery models. Also, in BOL, under "Full Recovery" It says: "You can restore a database to the state it was in at the point of failure if the current transaction log file for the database is available and undamaged. "
It also adds a note: "To protect against loss of transactions under the Full Recovery model, the transaction log must be protected against damage. It is strongly recommended that fault-tolerant disk storage be used for the transaction log."
So, my understanding is that if the failure happened to damage the database itself, but not the transaction log you could restore the database if you had it set for Full Recovery. | |
| naresh_sky 2002-12-16, 12:27 am |
| thank's susan!!!
So the point you mean to say.
was that if a part of the hard disk
fails then only there are chances of
gaining back the server to the point
of return befire crash.
and again "thanks" for yor help
cheer's
Naresh | |
|
| As tbe person has mention. If the server crash, hard disk is all gone. Efinately, all the data will be gone.
I believe every company have their own backup tapes.
Database, systems and program files can be restore from the backup tapes.
So,i dun see any reason, why data can't be restore from the backup tapes.
Regarding transaction log file, yes, it can restore to the point where the database fails. But, before you do that, you need to know how's your company backup function. Daily full backup, differential backup or something else.
Restore the normal backup to the server, and lastly restore the transaction log files to the server. From there, you will have your data back. | |
| mchoirul 2002-12-28, 12:00 am |
| as a DBA, one of your job is preparing disaster recovery planning. So the server must be configured with disk array (RAID) configuration for maximum fault tolerance.
do regular backup of your data & log and save it on a save place | |
| naresh_sky 2003-01-06, 2:35 am |
| thanks mchoirul and dann..
sorry for a delayed response ..
i got the point u mean to say that.
there should be a perfect planning to
cope up with the disaster of server crash.
thanks
naresh | |
| rcaine 2003-02-09, 10:06 am |
| Key point to remember for the 70-228 exam. The logs have everything since the last backup (last night/the weekend maybe). Recommended practice is to have logs on a different disk and hopefully controller from the data (mdf file). This improves performance and if the data disk fails you can still recover the logs. First step of any disaster recovery is recover logs with NO_TRUNCATE option. | |
| naresh_sky 2003-02-10, 8:00 am |
| hi rcaine..
thanks I got your point mate.
and again thanks for your help
Cheer's
Naresh |
|
|
|