Exactly. BOL has all the answers for restoring and recovering. While
someone could write it all out for you, it's well documented within the book
online and writing it out would be just a huge waste since it's there for
you.
If you take a look under the "How To" section, and go to "Transact SQL >
Administering SQL Server > Backing up and Restoring Databases" there is a
lot of information in there.

-----Original Message-----
From: Thomas Henley [mailto:[Email Address Removed]
Sent: Wednesday, September 18, 2002 8:54 AM
To: LazyDBA.com Discussion
Subject: RE: Tail Backup

Don't forget to use the stopat parameter (see BOL under RESTORE) on the tran
log restore if you need to limit the last tranlog to 10:45 AM (or 10:44 to
leave a minute's leeway!)

Tom

-----Original Message-----
From: Yukon DBA [mailto:[Email Address Removed] Wednesday, September 18, 2002 10:51 AM
To: LazyDBA.com Discussion
Subject: Re: Tail Backup


Hi Simon,
You are correct,
Taking full backup, differential backup and log backup is happening
regularly.

Now my query is,

Taken log backup at 10:00
Next log backup will be at 11:00

DB crashed (data file is inaccessible) at 10:45. so database is in suspect
mode.
Now I want to take a log backup(tail backup) B/w 10:00 and 10:45.

Expecting response and thank you in adv.

KM

----- Original Message -----
From: "Simon Holdsworth" <Simon.[Email Address Removed] "LazyDBA.com Discussion" <[Email Address Removed] Wednesday, September 18, 2002 8:13 PM
Subject: RE: Tail Backup


> You're gonna have to do a restore from the previous nights backup on the
new
> Disk drive set and hope for the best with the transaction logs.
> The below is taken from BOL, and has lots of information about backing up
> and restoring databases...
> How to restore to the point of failure (Transact-SQL)
> To restore to the point of failure
> 1. Execute the BACKUP LOG statement using the NO_TRUNCATE clause to back
up
> the currently active transaction log.
> 2. Execute the RESTORE DATABASE statement using the NORECOVERY clause to
> restore the database backup.
> 3. Execute the RESTORE LOG statement using the NORECOVERY clause to apply
> each transaction log backup.
> 4. Execute the RESTORE LOG statement using the RECOVERY clause to apply
the
> transaction log backup created in Step 1.
>
> -----Original Message-----
> From: Yukon DBA [mailto:[Email Address Removed] Sent: Wednesday, September 18, 2002 7:34 AM
> To: LazyDBA.com Discussion
> Subject: Tail Backup
>
> Hi All,
> Small correction on my previous query,
> Data file HDD is crashed,
> Log file HDD is Good.,
>
> Please give your valuable suggestions
> ----- Original Message -----
> From: Yukon DBA
> To: [Email Address Removed] ; [Email Address Removed] Sent: Wednesday, September 18, 2002 6:49 PM
> Subject: Tail Backup
>
>
> Hi,
> The scenario is like this,
>
> Log file HDD is crashed,
> Data file HDD is good,
> Now Database is in Suspect mode.
>
> How to take the tail log backup for getting the last min records?
>
> Have anybody faced the problem like this,
>
> Thanks in Advance,
> KM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mssqldba-[Email Address Removed] For additional commands, e-mail: mssqldba-[Email Address Removed] unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed] unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page