Always be conservative
with estimates, risk assessments, and the like. Nothing will kill your career faster
than overpromising and underdelivering. (Hint: Don??™t mention that you??™re being
conservative. It defeats the purpose completely.)
??? Be paranoid: Nothing makes for a better backup/recovery plan than a paranoid
mind. Assume the worst. Assume things won??™t work as planned; this help generates
the drive to test regularly. Assume you??™ll be fired if the plan fails. However,
don??™t have a defeatist (???This will never work???) or nihilist (???Oh, what??™s the point????)
attitude. Only the truly paranoid need apply.
??? Be diligent: Remember that a backup/recovery plan isn??™t just a function of the
DBA; the business unit has the final say (if it can pay for it) and equal responsibility.
Always keep the business in mind. The point of backup and recovery is not
the protection of the database, but the protection of the business processes it
supports. It??™s also critical to set expectations appropriately. No one likes surprises,
especially not upper management.
??? Be vigilant: Test, test, and test again.
Pages:
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282