You administer a Microsoft SQL Server 2012 instancethat contains a financial database hosted on a storage
area network (SAN).
The financial database has the following characteristics:
A data file of 2 terabytes is located on a dedicated LUN (drive D).
A transaction log of 10 GB is located on a dedicated LUN (drive E).
Drive D has 1 terabyte of free disk space.
Drive E has 5 GB of free disk space.
The database is continually modified by users during business hours from Monday through Friday between
09:00 hours and 17:00 hours.
Five percent of the existing data is modified each day.
The Finance department loads large CSV files into anumber of tables each business day at 11:15 hours and
15:15 hours by using the BCP or BULK INSERT commands.
Each data load adds 3 GB of data to the database.
These data load operations must occur in the minimum amount of time.
A full database backup is performed every Sunday at10:00 hours.
Backup operations will be performed every two hours(11:00, 13:00, 15:00, and 17:00) during business hours.
On Wednesday at 10:00 hours, the development team requests you to refresh the database on a
development server by using the most recent version.
You need to perform a full database backup that will be restored on the development server.
Which backup option should you use?
A.
NORECOVERY
B.
FULL
C.
NO_CHECKSUM
D.
CHECKSUM
E.
Differential
F.
8ULK_LOGGED
G.
STANDBY
H.
RESTART
I.
SKIP
J.
Transaction log
K.
DBO ONLY
L.
COPY_ONLY
M.
SIMPLE
N.
CONTINUE AFTER ERROR
Explanation:
Verified answer as correct.
Reference: http://msdn.microsoft.com/en-us/library/ms191495.aspx
Reference: http://msdn.microsoft.com/en-us/library/ms186858.aspx
J.
Transaction log
L. Copy Only
Copy-only backup do not affect the normal sequence of backups. A copy-only backup is created independently of your regularly scheduled, conventional backups. A copy-only backup does not affect your overall backup and restore procedures for the database.
why not option B, FULL?
Because the COPY_ONLY will do just that: copy the db, and will not break the order of transaction log backups.