The approach is simple
and is laid out in the following list of backups to be taken:
??? PRIMARY filegroup backup every Sunday at 10 a.m.
??? Order_FG filegroup backup every night at 10 p.m.
??? Transaction log backups every 30 minutes
You still need all of the transaction logs to ensure consistency. Actually, if you??™re ever
in doubt, back up the transaction logs on a frequent basis.
Inherent Risks
When you choose to restore only specific tables, be sure that the approach you??™re
choosing is really necessary. It should be rare and applicable only in very specific situations.
Continually question whether it is sufficient to restore just a few tables, even if
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 135
your testing at first appears successful. To determine whether it??™s valid to restore specific
tables, someone needs intimate knowledge of the database structure and of the
application design itself. Personally, I would avoid the approach of restoring specific
tables described in this scenario, but I do acknowledge that it can be useful at times.
Table 5-5 shows the risks to prepare for.
Pages:
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275