Tape arrays provide larger
amounts of storage, although they do stripe the backup from a hardware standpoint. You can also use a bitbased
backup over a network from SAN to SAN. I??™ll discuss some of these technologies in Chapter 10. For
now, though, you should consider options such as these after you??™ve defined the base requirements and a
base plan. Never jump to a solution before you??™ve clearly defined the problem.
You definitely need to create filegroup backups and perhaps even move to the partial
backup/piecemeal restore. Let??™s assume that 40GB is your maximum portability size. For
all sizes of databases, the plan would look something like this:
??? PRIMARY filegroup the first Sunday of every month at 10 p.m.
??? Single file backup nightly at 10 p.m.
??? Transaction log backups every 30 minutes
As with most backup/restore plans, transaction logs are the key. In this case, if you
lose a single data file, you could restore only that file plus all the transaction logs since
that file was created to ensure transactional consistency.
Inherent Risks
Because of the complexity of the backup plan (lots of file backups spread over multiple
days), this scenario runs the risk of logistical issues.
Pages:
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272