You have to protect the transaction logs
at all costs.
If minimal data loss is the need, you have to focus on protecting your backups as
much as possible. Yes, you can do things like physically protect backup tapes and such,
but that isn??™t part of the backup/recovery plan. You have to incorporate some level of
protection into your plan, such as taking advantage of the new MIRROR TO clause. The
following is one potential approach to take:
??? Full backup weekly, with five weeks??™ worth kept on file
??? Log backups every 30 minutes, mirrored to four devices, and stored for ten weeks
Depending on the size of the database, you could include file/filegroup backups,
differentials, and so on, but your main goal is to have a solid base to restore the database
from (the full backup) and a complete history of activity that can be replayed on the database
(the log files).
You should also consider a formal policy prohibiting the use of creating any backups
outside of the normal backup scheme for the purposes of refreshing a test database. The
WITH COPY_ONLY clause prevents differentials from becoming obsolete, but you need an
official policy to enforce its usage.
Pages:
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268