usercommunications >> Mainframe Network Software
User:  guest | | | | | |

 Usercomm Number: 2012 - 14
  Usercomm - Disaster Recovery Plan - Account Shared Network Components    hits: 410
Posted by Reserved:    
     
Scope: All accounts requiring an account Network Disaster Recovery Plan that use shared mainframe gateways or other shared network components in their production environments

Effective Date: Immediate

Group Name: Disaster Recovery – DRC Services, ITSCM services, Americas Continuity Services, Mainframe Network Software Services

Affected Locations: Charlotte, Plano, Rancho Cordova, Auburn Hills, Tulsa, Toronto

Summary: Each account and client requiring network connectivity for Disaster Recovery is responsible for provisioning and maintaining a self-contained DR plan for their required network connectivity during a disaster. If the client utilizes shared mainframe gateways and/or network devices and service components in their production environment, there is no provision by the Service Line for disaster recovery and those components will not be recovered to the designated recovery site by the Mainframe Capability, Data Center or Continuity Services delivery organizations.

Justification: Ability to recover network connectivity in the event of a disaster.

Benefits to Users:
• Connectivity to business applications in the event of a disaster
• A comprehensive network DR plan that does not rely on shared components
• Less confusion and effort at time of disaster or DR exercise

Details: Some clients use shared mainframe gateways and network components to connect to their mainframe business applications (Mainframe Gateways, Routers, Switches, Firewalls, DNS, etc.). Those shared components cannot be recovered at the Americas Continuity Services recovery site in Littleton, MA, or other HP and DR vendor sites. Because the scope of any given disaster is not known until it happens, and clients recover to multiple sites, and recovery site configurations are different than production configurations, recovery of those shared components is not practical, nor can it be planned for.

Accounts need to work with the Global Network Services organization, Continuity Services and others to have a DR plan engineered to recover their entire network connectivity in the event of a disaster. This may include opening a work order (NoTA) and having a network engineer and project manager assigned. Accounts should take ownership of keeping their plans up to date and making them available to supporting organizations for DR planning purposes. If an account utilizes the ITSCM service in Americas Continuity Services, that ITSCM planner can assist in maintaining the plan. DRC Services (the leveraged exercise management service) does not keep account / client plans.

Accounts should consider any contract requirements related to Disaster Recovery and adjust if necessary to ensure the client understands shared network components will not be recovered in the event of a disaster.


Primary Contact: Tom Bowman, tom.bowman@hp.com

Secondary Contact: Dave Faulkner, dave.faulkner@hp.com
 


Technical Contact:  email at: Ray Hand   or Phone: 469-808-4288