I??™ll start with a
generic template that contains required steps regardless of the specific business or
technical needs and constraints. From there, I??™ll examine common business and technical
scenarios to which you can apply the general template. When discussing
approaches to common scenarios, I??™ll include samples for three arbitrary categories
of database sizes: small (less than 50GB), medium (greater than 50GB and less than
500GB), and large (greater than 500GB). Given the size of the databases, an approach
to dealing with any specific scenario may change or be completely untenable.
A General Template
While backup/restore planning is always specific to each individual situation, you should
always use a general set of rules??”templates, if you will??”as a starting point. Every
backup/recovery plan should contain the following:
??? A documented schedule for backing up system databases
??? Documentation for restoring system databases
??? A list of requirements or goals to achieve
??? A description of a potential approach
??? Backup types and schedule
??? Naming standards
??? Restore scenario
??? Handling out-of-sequence backups
??? An identification of risks involved in the plan
I prefer to back up system databases at least once a week.
Pages:
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253