First, note that everything includes
the word documented. It isn??™t enough to have a plan in place??”it must be documented at
some level. Raise your hand if you enjoy writing documentation. Something tells me that
there aren??™t many of you with your hands up. Documentation is a time-consuming, boring
(for most technical staff), and tedious task. When corners need to be cut on any
activity, documentation is one of the first things to skimp on.
Second, consider data-protection requirements. Who determines those? It had better
not be you. Without the involvement of the business staff, creating a backup/recovery
plan could lead to the loss of a job. However, it??™s much more complicated than asking a
manager for requirements; you have the responsibility as the technical expert to make
the manager understand the implications of his choices. That isn??™t always an easy thing
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 100
to do. If you talk in any sort of tech-ese, you won??™t be successful. You have to be clear, concise,
and, most of all, able to explain things in a way that make senses to your audience.
Pages:
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212