Scenario: Short Backup Window
Time is a luxury. Common base BRPs focus on minimizing the time required for a particular
part of the plan. In a perfect world, backups would happen instantaneously,
disasters would never occur, and DBAs would be treated like kings. As we all know, this
is far from a perfect world. Trying to minimize the time required to perform a backup
can end up being quite complex.
Requirements
In this scenario, there is only a short period of time where you can make backups without
interrupting other tasks or impacting user experience. Other maintenance work can also
limit the backup window. The bottom line is that all backup procedures need to occur as
quickly as possible.
Potential Approach
One of the biggest technical restraints that affect this scenario is the size of your database.
For a medium or large database (greater than 50GB), a single, full backup can be
prohibitive in terms of time; once the terabyte range is hit, it is all but impossible.
For smaller databases (less than 50GB), completing a single full backup is usually
possible. The real question is: how often can you perform that full backup? Nightly?
Weekly? Monthly? Given the best-case scenario of a nightly full backup, a backup
scheme would look something like this:
??? Full backup Sunday at 6 p.
Pages:
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255