In my book, backup/recovery comes first, then high availability. Unless a client specifically indicates
that x amount of data loss is acceptable, I assume that zero data loss is the goal.
Requirements
When a database is critical to the day-to-day financial success of the company, it definitely
has a need for minimal data loss. Any database that must retain a continuous log
of transactions (a bank, perhaps) cannot tolerate data loss. The database needs to return
to a functional state as quickly as possible. Any interruptions caused by backup operations
??”however important those backups may be??”take second seat to data protection.
Potential Approach
Transaction log backups are the key toward minimizing data loss. Lose a single file, and
you??™re looking for a new job. Yes, you still need that full backup, and differential backups
certainly help restore times, but that isn??™t your main objective. Your main objective is no
data loss. Period.
The nice thing about setting up this type of backup/recovery plan is that it doesn??™t
much matter what the size of the database is. It could be 50MB, or it could be 50EB
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 131
(exabytes??”in other words, 50,000,000GB).
Pages:
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267