70-450 · Question #92
You are a professional level SQL Sever 2008 Database Administrator. The solution is log-shipped for high-availability purposes. The data files of the database reside on drive D, while the…
The correct answer is C. You should perform the tail-log backup of the primary database. This topic is relevant only for databases that are using the full or bulk-logged recovery models. In most cases, under the full or bulk-logged recovery models, SOL Server 2005 and later versions require that you back up the tail of the log to capture the log records that have…
Question
You are a professional level SQL Sever 2008 Database Administrator. The solution is log-shipped for high-availability purposes. The data files of the database reside on drive D, while the transaction log files of the database reside on drive E. A restoring test plan should be implemented to satisfy the requirements listed below for the log- shipping solution.
- First, the secondary database is brought online in the shortest time.
- Secondly, the data is in a consistent state.
- Thirdly, the data loss is reduced to the least.
The first step for the recovery test plan should be identified in the event of drive D failure. Which step should be performed?
Options
- AYou should bring the secondary database online.
- BYou should execute the DBCC CHECKDB command along with the REPAIR_REBUILD
- CYou should perform the tail-log backup of the primary database.
- DYou should execute the DBCC CHECKDB command along with the
How the community answered
(19 responses)- A5% (1)
- B11% (2)
- C79% (15)
- D5% (1)
Explanation
This topic is relevant only for databases that are using the full or bulk-logged recovery models. In most cases, under the full or bulk-logged recovery models, SOL Server 2005 and later versions require 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- SQL Server 2005 and later versions usually require 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 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 it you are moving or replacing {overwriting) the database. Also, it the log tiles 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
Topics
Community Discussion
No community discussion yet for this question.