| < Day Day Up > |
|
To maintain a consistent view of this plan, you should list the responsible plan's authors and editors, along with the location of each plan per author/editor, as shown in Table D.14.
The location of the electronic components of a DR plan should also be recorded, as shown in Table D.15.
PLAN AUTHOR/EDITOR/DATE LAST EDITED | DOCUMENT NAME/ PURPOSE | LOCATION: (P)APER/(E)LECTRONIC |
---|---|---|
D.C. / D.L./12-09-02 | DR Plan | P-Off-site E-SERV/PATH/DOCNAME |
D.C./K.W./01-01-03 | Backup Plan/Backup and Recovery Strategies | P-On-site/Off-site E-SERV/PATH/DOCNAME |
PURPOSE | DOCUMENT NAME (P)APER/(E)LECTRONIC | LOCATION(S) | LAST UPDATED | OWNER |
---|---|---|---|---|
Disaster Recovery | P-DR Plan E-DR_120502.doc | P-Room 1202 E-Server/Path/Document | 08-19-02 | J. Dekrator |
Oracle Recovery | P-Oracle Recovery Guide E-ORA_RG.doc | P-DBA Filing Cabinet and Off-site Vendor E-Server/Path/Document | 08-30-02 | D. Alvish |
Ops Guide | P-NBU Operations E-NBUOPS.doc | P-NONE E-Server/Path/Document | 11-20-02 | T. Traansman |
BIA for Sales | P-BIA Assessment for Sales Division E-BIA_SALES.doc | P-USA Bank Safe Deposit Box E-Server/Path/Document | 3-19-02 | A. Prenzes |
Determine your company's policy for updates and list them here. Perhaps your company will choose to update every six months or annually at the very minimum. The wording need not be exhaustive; be simple and concise to reduce complexity. The following is an example of a brief statement you might include in your company's DR testing policy plan:
The DR plan must be reviewed and updated annually at the very minimum. All members of the DR team should participate in the review and update of the plan. The next planned meeting is December 14, 2003. The Management Team will be responsible for sending out a reminder email as the date approaches.
Note that the paragraph indicates the next scheduled meeting. This is very important to maintain a consistency in your testing, review, and maintenance of your DR plan.
| < Day Day Up > |
|