popp.undp.org€¦ · Web viewDisaster Recovery Plan Page 2 of 21 BOM Office of Information Systems and Technology - United Nations Development Programme 304 E. 45th Street, New York,

Disaster Recovery Plan Template

BOM Office of Information Systems and Technology - United Nations Development Programme 304 E. 45th Street, New York, NY 10017 - [email protected] - Confidential and Proprietary © 2011

mailto:[email protected]

[Office_Name] Disaster Recovery Plan Page 2 of 21

DOCUMENT CONTROL

Document Name Disaster Recovery Plan Template

Language(s) English

Responsible Unit BOM - OIST

Creator (individual) Alexey Kuzmenko <[email protected]>

Subject (taxonomy) Disaster Recovery Standards

Effective Date October 2011

Mandatory Review (12 months after last review)

Reviewed on October 2013

Next Review Date October 2014

Audience All individuals accessing the UNDP Intranet

ApplicabilityAll UNDP staff members, non-staff personnel, interns, vendors, other contract holders and all third parties owning, managing, supporting and hosting critical ICT infrastructures and systems of UNDP

Related documents ICT Disaster Recovery Standards for UNDP Offices; Information Security Policy

Inspected for Quality (Release Approval) by Paul Raines (on October 2013)

Date Author Version Change Reference11 Jan 2010 Alexey Kuzmenko 1.0 Original draft created04 Feb 2010 Alexey Kuzmenko 1.1 Incorporated editorial changed

26 Sep 2011 Alexey Kuzmenko 1.2 Reworked structure and examples

24 Oct 2013 Alexey Kuzmenko 1.2 Performed annual review. No changes required




1.0 INTRODUCTION1.1 In accordance with the Information Security Policy and the Disaster Recovery (DR) Standards for UNDP Offices, all critical ICT systems shall have adequate DR provisions in place. A list of critical ICT systems must be defined by office management along with business continuity requirements and recovery objectives for these systems.

1.2 ICT managers of a corresponding office are responsible to design, implement, maintain and formally document DR provisions that satisfy requirements of corresponding standards as well as recovery objectives set by office management.

2.0 PURPOSE2.1 This document provides a unified structure for ICT managers to outline existing DR arrangements. Plans prepared in accordance with DR standards and based on this template will serve as a single reference point for post-disaster recovery activities. Documentation based on this template will also streamline maintenance and verification of DR provisions.

3.0 SCOPE3.1 This template is aligned with the Disaster Recovery (DR) Standards for UNDP Offices. It should be noted that design, implementation, maintenance and verification of DR provisions should be in compliance with these standards. ICT Managers should use this template for the purpose of structuring a Disaster Recovery Plan.

3.2 A Disaster Recovery Plan can be created as a standalone document utilizing only pages that go after the Section 5, providing specific office information, and removing all explanatory and example text, and appropriately naming the file (ex: “UNDP Moldova Disaster Recovery Plan”).

4.0 REFERENCES4.1 This document is based upon the following policies, standards and best practices, which can assist in best understanding and using this template:

UNDP Information Security Policy Disaster Recovery Standards for UNDP Offices

5.0 FORMATTING INSTRUCTIONS5.1 First five sections of this Disaster Recovery Plan Template, as well as explanatory and example texts in the subsequent sections, shall be removed from the final Disaster Recovery Plan (DRP). The final DRP should use normal, black Times New Roman font for the majority of the text.

5.2 Explanatory text below describes what should be considered prior to writing specific sections of the document. It is also useful to understand what sections should contain.

[Explanatory text is in italic, black, Times New Roman font such as this and marked with square brackets.]

5.3 Example text shows examples of what might be written. Examples may apply to some offices or ICT systems, but most likely need to be replaced with relevant, office-specific information.

Example text is in italic, black, Arial font such as this.

5.4 All tags that need to be replaced are marked with square brackets.

[Office_Name] – Represents the name of the office where the DRP is prepared (e.g. UNDP Moldova)[ICT_Manager_Name] – Represents name of an ICT Manager of a corresponding office (e.g. John Smith)




Disaster Recovery Plan[Office_Name]




Table of Content

s

1.0 Certification..............................................................................................................................6

2.0 Maintenance Records...............................................................................................................6

3.0 Verification Records.................................................................................................................6

4.0 Scope........................................................................................................................................7

5.0 Recommendations and Action Items........................................................................................7

6.0 Off-Site Storage........................................................................................................................8

7.0 Software Library.......................................................................................................................9

8.0 Alternative Facility...................................................................................................................9

9.0 Preventative Measures..............................................................................................................9

10.0 Internet Connectivity..............................................................................................................10

11.0 Active Directory.....................................................................................................................13

12.0 File Storage.............................................................................................................................15

13.0 <System_Name>....................................................................................................................17

Annex A – Personnel Contact Information.....................................................................................18

Annex B – Vendor Contacts............................................................................................................19

Annex Y – Improvement Recommendations..................................................................................20

Annex Z – Action Items..................................................................................................................21




1.0CERTIFICATIONAs an ICT manager of [Office_Name], I certify that this Disaster Recovery Plan reflects technical DR arrangements that are actually in place and satisfy requirements of Office management outlined in the Business Continuity Plan (BCP) and/or requirements of the Disaster Recovery Standards for UNDP Offices.

(signed) 12 Mar 2009[ICT_Manager_Name]ICT manager

Date

2.0MAINTENANCE RECORDSDate Author Version Change Reference12 Mar 2009 John Smith 1.0 Initial document created

3.0VERIFICATION RECORDS These records establish an audit trail confirming that provisions of this plan were tested in accordance with the Disaster Recovery Standards for UNDP Offices document.

Date Responsible person

Test plan and report references Signature

27 Apr 2009 John Smith AD restoration procedure was tested in accordance with corresponding test plan. Both the test plan and the report are stored on the office file server at X:\DRP\Test_AD_2009\

Hardcopies are stored in the office of the OM in the folder “ICT”

(signed)




4.0SCOPE[This section defines the scope of the plan. It should list locations covered by the plan or referred in recovery procedures. The section should also include a list of critical ICT systems along with specific recovery objectives and references to recovery procedures. Planning assumptions as well as additional background information should also be mentioned here. Please note that DRP is not the right place to outline all infrastructural details. The DRP should concentrate on recovery procedures of critical ICT systems.]

4.1 This Disaster Recovery Plan (DRP) covers the following locations.

ID # Name Address GPS Coordinates Point of contact

LR-01 UNDP Office1, Klovsky Uzviz St.,Kyiv, 01021, Ukraine

+50° 26' 35.76",+30° 32' 22.04"

Vasiliy Mironen,Operations Manager+380-67-223-33-22

LR-02 Alternative Office60 Vladimirska St.,Kyiv, 01033, Ukraine

+50° 26' 31.33",+30° 30' 39.16"

Lavrentiy Yefremov,Project Manager+380-63-345-65-75

LR-03 Off-site Vault2/1 Sofiivska St.,Kyiv, 01025, Ukraine

+50° 27' 05.32", +30° 31' 18.09"

Kimberly Orr,Project Manager+380-50-423-77-15

4.2 Management of [Office_Name] has designated the following systems as critical. They shall be reconstituted within recovery objectives defined below.

ICT system Location RTO RPO Recovery Procedure [1]

Internet connectivity LR-01 (UNDP Office) LR-02 (Alternative Office)

8 hrs n/a Procedure 1.AProcedure 1.B Procedure 1.C

Active Directory LR-01 (UNDP Office) LR-02 (Alternative Office)

12 hrs 3 days Procedure 2.AProcedure 2.B

File Storage LR-01 (UNDP Office) 72 hrs 5 days Procedure 3

[1] Detailed recovery procedures are outlined in “Recovery Procedure” section for each critical system

4.3 Provisions of this plan address disasters with assumptions that:

a) Only primary location LR-01 (UNDP Office) is affected;b) Off-site storage location LR-03 (Off-site Vault) is not affected, or affected only to the point where

backup media is not damaged and could still be obtained (withdrawn);c) Secondary location LR-02 (Alternative Office) is not affected.

5.0RECOMMENDATIONS AND ACTION ITEMS[This is a standard section and it should be left intact. The objective of this section is to explicitly inform a reader how planned but not implemented parts of the DRP are marked. Please note that if you include DR provisions that are not implemented, you shall mark them in the way it is described in this section. No planned/non-existent DR provisions shall be documented as if they already exist. Such non-professional behavior undermines the whole DR planning effort, provides false information, false sense of preparedness and puts recovery at risk of not being possible in the event of a real disaster.]

5.1 This document also captures recommendations on improvement of [Office_Name] disaster readiness in “AnnexY – Improvement Recommendations” along with corresponding action items in “Annex Z – Action Items”.

5.2 Processes, systems or items mentioned in this plan as well as sections of this plan which are currently unavailable (not implemented, out of stock, etc.) are highlighted in gray. Items that still require clarification are highlighted in yellow.




6.0OFF-SITE STORAGE[This section should contain details with regard to an off-site storage. It could mention things like type of the arrangement (contractual or reciprocal), distance to the main office, specific withdraw/deposit procedures, list of deposited items, etc.]

6.1 Off-site Vault is located within 2 km from the UNDP Office and provided by EDU project. It is facilitated by Memorandum of Understanding (MOU) #2009-03. Electronic version of the MOU is stored on the office file server at X:\DRP\. Hardcopy is stored in the office of the Operations Manager in the folder “ICT”.

6.2 Off-site Vault has an environmentally controlled storage room with no windows and a reinforced entrance with metallic door that opens outside. The room is equipped with environmental control systems that keeps temperature and humidity on the level acceptable for magnetic tape storage. Smoke detector is installed in the storage room and connected to a fire alarm system.

6.3 In order to get access to the off-site storage a person should be pre-authorized by the office management to access the facility. List of pre-authorized personnel is shared with the management of the Off-site Vault and could be found below.

Position Name Cell phoneICT Manager John Smith +380-50-441-4586

Operations Manager Vasiliy Mironen +380-67-223-3322

Finance Officer Valentina Bondarenko +380-63-544-3212

6.4 Deposition and withdrawal transactions (what, when, by whom) shall be recorded in the off-site storage log and a person performing withdrawal/deposition should sign it. The log shall be kept on file at off-site storage and another copy is stored at the office.

6.5 Items currently deposited off-site are recorded below.

ID # DescriptionOS-XX-01 Inmarsat-M4 terminalOS-XX-02 Notebook marked as “Inmarsat”OS-XX-03 Notebook marked as “ICT Manager”OS-XX-04 Dell PowerVault LTO-4-120 tape driveOS-XX-05 Vodafone broadband (cellular) USB modem – 5 pcsOS-XX-06 AT&T broadband (cellular) USB modem – 5 pcsOS-XX-07 Cisco console cableOS-XX-08 Metal box with CDs and envelopes marked as “Software Library”OS-XX-09 Tape marked as “XX.UNDP.LOCAL - DD-MM-YY”OS-XX-10 Tape marked as “XX-FILES01 - DD-MM-YY”OS-XX-11OS-XX-12OS-XX-13OS-XX-14OS-XX-15OS-XX-16OS-XX-17OS-XX-18OS-XX-19OS-XX-20




7.0SOFTWARE LIBRARY

[This section should capture software distributions required for the restoration procedures, license keys as well as any credentials required to access restored systems.]

7.1 The software library contains distributions of all the software (and corresponding licensing keys) mentioned as prerequisite items for the restoration procedures. It also contains administrative credentials required for reconstitution of critical ICT systems.

7.2 The library is stored in the off-site storage . Content of the software library is recorded below.

ID # DescriptionSL-XX-01 Distribution of the Windows 2003 Server R2 Enterprise and corresponding license keysSL-XX-02 Distribution of the Symantec Backup Exec 10 and corresponding license keysSL-XX-03 Distribution of the Dell PowerVault LTO-4-120 driversSL-XX-04 Set of envelopes with administrative credentials - 3 pcsSL-XX-05SL-XX-06SL-XX-07SL-XX-08SL-XX-09SL-XX-10

8.0ALTERNATIVE FACILITY[This section should contain information relevant to the alternative facility. It should mention resilient systems hosted there, equipment related arrangements, etc.]

8.1 Alternative office arrangement is facilitated by the Memorandum of Understanding (MOU) #2009-07 with MSDP project. Electronic version of the MOU is stored on the office file server at X:\DRP\. Hardcopy is stored in the office of the Operations Manager in the folder “ICT”.

8.2 MSDP is situated 1.6 km away from the primary office. Project office hosts AD domain controller to provide resiliency and ability to deploy UNDP personnel notebooks into MSDP LAN without reconfiguration and creation of additional AD account.

8.3 MSDP office also has a conference room for 15 people with a wireless access point that supports 802.11 a/b/g/n clients. This conference room shall be used as a temporary workplace for activated personnel.

9.0PREVENTATIVE MEASURES[This section should describe required preventive measures like fire alarm, smoke detectors, environmental management, etc.]

9.1 Server room of the primary compound is equipped with environmental control system that keeps temperature and humidity on the level required by the DR Standards document. There is also an environmental monitoring system established. This system sends alerts over SMS to ICT Manager and Admin Associate if temperature in the server room hits the threshold of 25°C or water sensor on the floor is activated.

9.2 Server room is also equipped with a smoke detector that is connected to an office fire alarm system. In case of fire an alarm goes to the nearest fire department that is 3km away from the primary compound.




10.0 INTERNET CONNECTIVITY

[This is a system specific section. Each critical system should have a designated section in the DRP capturing brief description of the system’s capabilities, logical components the system consists of, administrative credentials required to manage or restore the system, possible external dependencies as well as data backup arrangements and specific restoration procedures. Some sub-sections might be inapplicable to some systems. For example, there is no data backup arrangements or external dependencies for the internet connectivity.]

10.1 General Information

10.1.1 Internet connectivity at the primary location LR-01 (UNDP Office) is supplied by the BestNET ISP through a 2 Mb/s fiber-optic leased line. Secondary Internet connectivity is supplied by the EMC Inc. through a 512 kb/s VSAT link (satellite).

10.1.2 Both connections are terminated on the modular router XX-CORE01 managed by the local ICT personnel of the office. Managed security service (MSS) firewall XX-FW01 is installed behind the router and acts as a gateway for all workstations.

10.1.3 Secondary location LR-02 (Alternative Office) is connected to the Internet by AlterNet ISP through a 1 Mb/s copper-leased line. It is terminated on the ADSL modem connected to the Linux router XX-RT01 through an Ethernet interface. XX-RT01 also acts as a firewall and is used as a gateway by user workstations.

10.1.4 EtherTrans Communications supplies Ethernet transport service between the office compound and the alternative facility. This link is terminated on CORE01 and RT01.

10.2 Logical ComponentsDNS Name Inventory # Serial # Location SpecificationXX-CORE01 UNDP-1239 JAD05450AZE LR-01, Server room,

rack 01, position 15Cisco 3640

XX-FW01 UNDP-1250 DFE127834REW

LR-01, Server room, rack 01, position 18

Cisco ASA 5520

XX-RT01 112 13858613 LR-02, Comm. closet, position 03

Intel Xenon X5355 2.66GHz CPU, 4GB RAM, 2x250GB SATA HDD, 2x1GbE NIC

ADSL modem 120 DL1245-NEK LR-02, Comm. closet, top shelf

Provided by AlterNet ISP

10.3 Administrative Credentials

ID # Last Update Provides Access toAC-01 2011-09-01 CORE01, FW01, RT01

10.4 Backup Arrangements

DNS NameOn-Site Off-Site

Location Frequency Location FrequencyN/A N/A N/A N/A N/A




10.5 External Relationships

10.5.1 The system does not depend on any other infrastructure other than electrical power and cooling.

10.6 Recovery ProceduresRecovery Procedure 1.A

Scope: Connectivity to the Internet through both ISPs or cellular operators is unavailable due to a disaster affecting national communications infrastructure. EMC Inc. stationary satellite terminal in the office compound is also damaged by the disaster.

Assumptions:a) Inmarsat satellites and their communications infrastructure is not affectedb) Off-site Vault is not affected

Required Items:a) Inmarsat-M4 terminalb) Notebook marked as “Inmarsat”

Perform the following steps:1. Get above mentioned items from the off-site storage.2. Prepare M4 terminal for work outdoors according to the manual enclosed with it.3. Direct the antenna towards the Inmarsat-4 F3 satellite (azimuth 228,588°, elevation angle 8,467°).4. Connect the notebook and the terminal with a cable enclosed.5. Notebook is pre-configured to use M4 terminal as a modem, double-click “Connect” shortcut on

the desktop to initiate a connection.

Recovery Procedure 1.B

Scope: Office compound and alternative facility are affected by a disaster. Connectivity to the Internet through BestNET ISP, AlterNet ISP or EMC Inc. stationary satellite terminal is unavailable.

Assumptions:a) National communications infrastructure (country's connectivity to the rest of the Internet/world) is

intact and operationalb) Communications infrastructure of the cellular providers is intact and operationalc) Off-site Vault is not affected

Required Items:a) Vodafone broadband (cellular) USB modem – 5 pcsb) AT&T broadband (cellular) USB modem – 5 pcs

Perform the following steps:1. Get above mentioned items from the off-site storage.2. Distribute USB modems among activated personnel.3. Plug broadband modem into a powered computer.4. Drivers will be installed automatically.5. Connectivity can be established by double-clicking on the broadband connection icon in the task

panel notification area.




Recovery Procedure 1.C

Scope: Office compound connectivity to the Internet through the BestNET ISP is unavailable due to a disaster affecting the leased line.

Assumptions:a) National communications infrastructure (country’s connectivity to the rest of the Internet/world) is

intact and operationalb) EMC Inc. stationary satellite terminal and their communications infrastructure are intact and

operationalc) Off-site Vault is not affected

Required Items:a) Notebook marked as “ICT Manager”b) Cisco console cablec) Administrative credentials package "AC-01"

Perform the following steps:1. Get above mentioned items from the off-site storage.2. Connect console cable to the com port of the notebook.3. Plug console cable into the XX-CORE01 management port on the back.4. Double-click on the icon “Terminal” on the desktop. It will initiate default HyperTerminal session

(COM1; Bits per sec: 9600; Data bits: 8; Parity: none; Stop bits: 1; Flow control: none).5. Change default gateway for XX-CORE01 from BestNET ISP to EMC Inc. with the following

commands: Type “enable” Type “configure terminal” Type “no ip route 0.0.0.0 0.0.0.0 170.170.3.4” Type “no ip route 0.0.0.0 0.0.0.0 74.113.250.4” Type “copy run mem” Type “exit” Type “exit”




11.0 ACTIVE DIRECTORY

[This is a system specific section. Each critical system should have a designated section in the DRP capturing brief description of the system’s capabilities, logical components the system consists of, administrative credentials required to manage or restore the system, possible external dependencies as well as data backup arrangements and specific restoration procedures. Some sub-sections might be inapplicable to some systems.]

11.1.1 The infrastructure utilizes XX.UNDP.LOCAL as a domain name. The domain contains two sites XX01-SITE (UNDP Office) and XX02-SITE (Alternative Office).

11.1.2 For resiliency purposes, two domain controllers XX-DC01 (UNDP Office) and XX-DC02 (Alternative Office) are installed in each location. Both contain full replicas of the local AD and synchronize through the link provided by EtherTrans Communications.

11.2 Logical Components

DNS Name Inventory # Serial # Location SpecificationXX-DC01 UNDP-1239 JAD05450AZE LR-01, Server room,

rack 01, position 12IBM X346, Intel Xeon 3.2GHz CPU, 1GB RAM, 3x73.4GB Ultra SCSI HDD, 100MbE NIC

XX-DC02 UNDP-1250 DFE127834REW

LR-02, LAN closet, rack 01, position 02

Dell Optiplex GX 240, P4 2.4GHz CPU, 512MB RAM, 40GB ATA HDD, 100MbE NIC


ID # Last Update Provides Access toAC-02 2011-09-01 Domain Controllers XX-DC1 and XX-DC2 as well as all other servers

joined into the domain XX.UNDP.LOCAL


DNS NameOn-Site Off-Site [1]

Location Frequency Location FrequencyXX-DC01 Network Attached

Storage Every day between 20:00 and 01:00

LR-03, Storage room 47

Every week between 20:00 Friday and 06:00 Saturday

XX-DC02 Network Attached Storage

Every day between 01:00 and 6:00


Every week between 20:00 Saturday and 06:00 Sunday

[1] Backup tapes are deposited off-site on Monday between 09:00 and 13:00


11.5.1 The system does not depend on any other infrastructure other than electrical power and cooling.




11.6 Recovery ProceduresRecovery Procedure 2.A

Scope: No Active Directory (AD) services is available due to a disaster affecting both the primary and alternative locations where AD servers are installed. Procedure covers restoration/installation of a new and independent Domain Controller server.

Warning: The procedure shall not be used to restore/install a new DC server in case at least one DC with correct AD domain/forest is already available on the same network. Connecting the restored server into the network will corrupt the production AD database or will lead to synchronization with the old/incorrect data.

Assumptions:a) Off-site Vault is not affectedb) Latest backup is not more than 180 days old1.

1Note: 180 days is a default tombstone period of Windows Server 2003 SP2 for AD database. The data older than the tombstone period cannot be restored.

Required Items:a) Server compliant with the specification from the Logical Components sectionb) Distribution of the Windows 2003 Server R2 Enterprise and corresponding license keysc) Distribution of the Symantec Backup Exec 10 and corresponding license keysd) Dell PowerVault LTO-4-120 tape drivee) Distribution of the Dell PowerVault LTO-4-120 driversf) Tape marked as “XX.UNDP.LOCAL - DD-MM-YY”g) Administrative credentials package "AC-02"

Perform the following steps:1. Install OS on the available server. Make sure, that OS is installed on the same drive letter and

partition as for the one used to produce the backup. 2. Give the same hostname to the server as for the one used to produce the backup.3. Install drivers for the tape drive4. Install Symantec Backup Exec 10 on the available server.5. Connect the LTO4 tape drive to the server6. Reboot the server7. Import the backup tape into Symantec Backup Exec 108. Restore System partition and System State data from backup.9. Restart the computer and press F8 to go to Directory Restore mode.10. Run NTDSUTIL in command prompt and enter "authoritative restore".11. Enter "restore database" and click "Yes".12. Once the restoration is done, reboot the server.

Recovery Procedure 2.B

Scope: Primary location is affected by a disaster.

Assumptions:a) Alternative facility is not affected




Required Items:a) Administrative credentials package "AC-02"

Perform the following steps:1. If administrative credentials (Administrator’s password) are not available, get above mentioned

envelope from the off-site storage.2. Alternative Office already has a domain controller XX-DC02 with the replica of the local AD

domain. 3. Login to XX-DC02 using administrative credentials from the envelope.4. To operate correctly five FSMO roles have to be seized by XX-DC02 with the following

commands:a. Click Start, click Run, type “Ntdsutil” in the Open box, and then click OK.b. Type “roles”, and then press ENTER.c. Type “connections”, and then press ENTER.d. Type “connect to server XX-DC02”, and then press ENTER.e. At the server connections: prompt, type q, and then press ENTER again.f. Type “Seize domain naming master”.g. You will receive a warning window asking if you want to perform the seize. Click on Yes.h. Repeat steps f) and g) for other roles (“seize infrastructure master”, “seize PDC”, “seize

RID master”, “seize schema master”)

12.0 FILE STORAGE12.1 General Information

12.1.1 File server is used by the office users to store and share official records, important documents and other files. File server is based on the Windows 2003 server which is part of the local AD domain.


DNS Name Inventory # Serial # Location SpecificationXX-FILES01 UNDP-1201 44512309192 LR-01, Server room,

rack 02, position 15Dell PowerEdge 2970, AMD Opteron 2435 2.6GHz CPU, 2x1GB DDR2 RAM, 5x250GB SATA HDD, 1GbE NIC


ID # Last Update Provides Access toAC-03 2011-09-01 Local administrator account on server XX-FILES01


DNS NameOn-Site Off-Site [1]

Location Frequency Location FrequencyXX-FILES01 Network Attached

Storage Every day between 20:00 and 01:00


Every week between 20:00 Friday and 06:00 Saturday

[1] Backup tapes are deposited off-site on Monday between 09:00 and 13:00


12.5.1 Correct access permissions to the file shares depends on the availability of the Active Directory infrastructure. File server has to be joined into the XX.UNDP.LOCAL domain.




12.6 Recovery ProceduresRecovery Procedure 3

Scope: File server is unavailable due to disaster affecting office compound. Procedure covers restoration/installation of a new file server from scratch.

Assumptions:a) Off-site Vault is not affectedb) Active Directory services for XX.UNDP.LOCAL domain are available in the network where a new

file server is being installed

Required Items:a) Server compliant with the specification from the Logical Components sectionb) Distribution of the Windows 2003 Server R2 Enterprise and corresponding license keysc) Distribution of the Symantec Backup Exec 10 and corresponding license keysd) Dell PowerVault LTO-4-120 tape drivee) Distribution of the Dell PowerVault LTO-4-120 driversf) Tape marked as “XX-FILES01 - DD-MM-YY”g) Administrative credentials package "AC-03"

Perform the following steps:1. Install OS on the available server. Make sure, that OS is installed on the same drive letter and

partition as for the one used to produce the backup. 2. Give the same hostname to the server as for the one used to produce the backup.3. Install drivers for the tape drive4. Install Symantec Backup Exec 10 on the available server.5. Connect the LTO4 tape drive to the server6. Reboot the server7. Import the backup tape into Symantec Backup Exec 108. Restore System partition from backup.9. Restore Storage partition from backup.




13.0 <SYSTEM_NAME>13.1 General Information

13.1.1 <System_Description>


DNS Name Inventory # Serial # Location Specification<DNS_Name> <Inventory#> <Serial#> <Rack_Location> <Specs>


ID # Last Update Provides Access toAC-?? <Last_Pwd_Update

><Access_Rights_Description>


DNS NameOn-Site Off-Site

Location Frequency Location Frequency

<DNS_Name> <On_Location> <On_Freq> <Off_Location> <Off_Freq>


13.5.1 <Dependencies_Description>

13.6 Recovery ProceduresRecovery Procedure <#>

Scope: <Procedure_Scope>

Assumptions:a) <Procedure_Assumptions>

Required Items:a) <Procedure_Prerequisites>

Perform the following steps:1. <Procedure_Steps>




ANNEX A – PERSONNEL CONTACT INFORMATION

Position Name Mobile Phone Home AddressICT Manager [ICT_Manager_Name] <Cell_Phone> <Home_Address>




ANNEX B – VENDOR CONTACTS

BestNET ISP Point of ContactPhones Name: Nazar Demyanenko

Office: +380-44-253-1216 Title: Account ManagerFax: +380-44-253-1210 Mobile: +380-50-211-7676Tech Support: +380-44-253-1919 Email: <[email protected]>

Postal Address Other Info59 Gorkogo St., Kyiv, 03150, Ukraine

AlterNet ISP Point of ContactPhones Name: Petro Vasilyev


Postal Address Other Info47 Zhylanska St., Kyiv, 01033, Ukraine

EtherTrans Communications Point of ContactPhones Name: Mariya Galushko


Postal Address Other Info11 Leontovicha St., Kyiv, 01030, Ukraine

EMC Inc. Point of ContactPhones Name: Munroe Lindsey


Postal Address Other InfoRedditch, Worcs B98 9AY, UK

<Vendor_Name> Point of ContactPhones Name: <POC_Name>

Office: <Office_Phone> Title: <POC_Title>Fax: <Office_Fax> Mobile: <POC_Mobile>Tech Support: <Support_Phone> Email: <POC_Email>

Postal Address Other Info<Postal_Address> <Other_Information>




ANNEX Y – IMPROVEMENT RECOMMENDATIONS

ID # Status DescriptionIR-XX-001 Open

IR-XX-002 Open

IR-XX-003 Open

IR-XX-004 Open

IR-XX-005 Open




ANNEX Z – ACTION ITEMS<?> out of <?> action items (<?>%) are closed. Open/Pending items are:

ID# Status Assigned to DescriptionAI-XX-001 OpenAI-XX-002 OpenAI-XX-003 OpenAI-XX-004 Open



Documents

popp.undp.org€¦ · Web viewDisaster Recovery Plan Page 2 of 21 BOM Office of Information Systems and Technology - United Nations Development Programme 304 E. 45th Street, New York,