I have a question about the Tail Log being backed up first before backing up. I have a database thats in Full Recovery mode and I want to backup the Tail log first, the thing is when I did that yesterday it took a long time like over 45mins. Is that normal, see the database is 2714.13 MB. Is that normal or should I be alarmed??
Hi Mcrowley, I have a database that I put in full recovery mode and I wanted to use the options under Transaction log
BACK UP THE TAIL OF THE LOG AND LEAVE THE DATABSE IN THE RESTORING STATE. That takes a long time though and I was wondering is that normal cause the database really isnt that big. Or am I being paranoid
Used the Maintenance plan to back up the databases, FULL, DIFF, TRANSACTION LOGS
Its that "Leave database in restoring state" that bugs me. That is not a normal backup option, and would probably only be used in extreme circumstances. As you saw, it left the database in a restoring state, and unusable.
yeah thats what I'm saying, I didnt understand why it was like that for so long. I was reading about it in the BOL This topic is relevant only for databases that are using the full or bulk-logged recovery models. I jsut want to cover all the bases
In most cases, under the full or bulk-logged recovery models, SQL Server 2005 requires that you back up the tail of the log to capture the log records that have not yet been backed up. A log backup taken of the tail of the log just before a restore operation is called a tail-log backup.
SQL Server 2005 usually requires that you take a tail-log backup before you start to restore a database. The tail-log backup prevents work loss and keeps the log chain intact. When you are recovering a database to the point of a failure, the tail-log backup is the last backup of interest in the recovery plan. If you cannot back up the tail of the log, you can recover a database only to the end of the last backup that was created before the failure.
Not all restore scenarios require a tail-log backup. You do not have to have a tail-log backup if the recovery point is contained in an earlier log backup, or if you are moving or replacing (overwriting) the database. Also, if the log files are damaged and a tail-log backup cannot be created, you must restore the database without using a tail-log backup. Any transactions committed after the latest log backup are lost. For more information, see "Restoring Without Using a Tail-Log Backup" later