TECHNICAL SPECIFICATIONS For DISASTER RECOVERY SERVICES TKG 15001 02/09/2015



Similar documents
Big Data Storage in the Cloud

Response to Bidder Questions and Amendment 2 to Request for Proposal Disaster Recovery Services

z/vm and Linux Disaster Recovery A Customer Experience Lee Stewart Sirius Computer Solutions (DSP)

Scope Statement for DST IT Disaster Recovery Services

OKHAHLAMBA LOCAL MUNICIPALITY

Open Source Mainframe Backup with Hercules

Module 5 Introduction to Processes and Controls

Using Virtualization to Help Move a Data Center

CA s Cloud Storage for System z

INSIDE. Preventing Data Loss. > Disaster Recovery Types and Categories. > Disaster Recovery Site Types. > Disaster Recovery Procedure Lists

Virtualization: TCP/IP Performance Management in a Virtualized Environment Orlando Share Session 9308

University of Central Florida Class Specification Administrative and Professional. Information Security Officer

Oracle Networking and High Availability Options (with Linux on System z) & Red Hat/SUSE Oracle Update

Improving disaster recovery with Virtual Tape Libraries in Mainframe Environments By Deni Connor Principal Analyst, Storage Strategies NOW

DISASTER RECOVERY AND CONTINGENCY PLANNING CHECKLIST FOR ICT SYSTEMS

FDR/UPSTREAM and INNOVATION s other z/os Solutions for Managing BIG DATA. Protection for Linux on System z.

Virtual Linux Server Disaster Recovery Planning

Virtual Networking with z/vm Guest LAN and Virtual Switch

UPSTREAM for Linux on System z

Second Line of Defense Virtual Private Network Guidance for Deployed and New CAS Systems

Virtual Networking with z/vm Guest LANs and the z/vm Virtual Switch

NOTICE ADDENDUM NO. TWO (2) JULY 8, 2011 CITY OF RIVIERA BEACH BID NO SERVER VIRTULIZATION/SAN PROJECT

Cross-Platform Access

zframe: a technical overview for

How To Write An Ets Request For Proposal (Rfp)

Replicating Mainframe Tape Data for DR Best Practices Session #10929

CATS+ TORFP # Maryland Department of Transportation (MDOT)

Department of Technology Services UNIX SERVICE OFFERING

IBM Mainframe Services. 10 April G-Cloud. service definitions

Ancero Backup & Disaster Recovery (BDR) Service Guide

CLOUD SERVICE SCHEDULE Newcastle

Data Protection History, Evolution, Best Practices By Global Data Vault

Understanding the New Enterprise Cloud System

Implementing Tivoli Storage Manager on Linux on System z

BUSINESSES NEED TO MAXIMIZE PRODUCTIVITY, LOWER COSTS AND DECREASE RISKS EVERY DAY.

IBM Systems and Technology Group Technical Conference

Scope Statement for Business Recovery Services. BCRS Contract Attachment #1 #ITS

Mainframe. Large Computing Systems. Supercomputer Systems. Mainframe

Scope Statement for North Carolina State University. Administrative Computing Services. Disaster Recovery Services

Application Backup and Restore using Fast Replication Services. Ron Ratcliffe March 13, 2012 Session Number 10973

z/vm built on IBM Virtualization Technology

VMWARE VSPHERE 5.0 WITH ESXI AND VCENTER

SCHEDULE 25. Business Continuity

IBM Communications Server for Linux - Network Optimization for On Demand business

Version: Page 1 of 5

Axcient Data Protection Platform. Axcient Data Protection Platform

CA Cloud Storage for System z

Disaster Recovery Checklist Disaster Recovery Plan for <System One>

How To Install A Virtual Image Facility On Linux (Amd64) On A 3390 Dasd 3390 (Amd32) Dasda (Amd86) (Amd66) (Dasd) (Virtual Image Facility) (For

SHARE Lunch & Learn #15372

CENTER FOR NUCLEAR WASTE REGULATORY ANALYSES

CA Products for z/vm Old Dogs with New Tricks

IBM Software Group. Lotus Domino 6.5 Server Enablement

Solution Brief: Creating Avid Project Archives

PROMAPP TECHNICAL INFORMATION

CounselorMax and ORS Managed Hosting RFP 15-NW-0016

BME CLEARING s Business Continuity Policy

Attachment E. RFP Requirements: Mandatory Requirements: Vendor must respond with Yes or No. A No response will render the vendor nonresponsive.

Redbooks Paper. Local versus Remote Database Access: A Performance Test. Victor Chao Leticia Cruz Nin Lei

INFRASTRUCTURE AS A SERVICE (IAAS) SERVICE SCHEDULE Australia

Veeam Backup and Replication Architecture and Deployment. Nelson Simao Systems Engineer

RELEASE NOTES. StoneGate Firewall/VPN v for IBM zseries

Virtual Server and Storage Provisioning Service. Service Description

The Modern Mainframe Data Center Sharing a Tape Infrastructure Session #10932

CommuniGate Pro SIP Performance Test on IBM System z9. Technical Summary Report Version V03

Understand the New Enterprise Cloud System

Virtualised MikroTik

JOHNSON COUNTY COMMUNITY COLLEGE College Blvd., Overland Park, KS Ph Fax

Information Technology Security Procedures

CONTINGENCY PLANNING -- THE AUDIT PROCESS Leslie A. Virgilio OFF-SITE, Inc. 32 Ellicott Street Batavia, New York 14020

SAN TECHNICAL - DETAILS/ SPECIFICATIONS

CONTINUITY AND RECOVERY PLANNING GUIDE

Transcription:

TECHNICAL SPECIFICATIONS For DISASTER RECOVERY SERVICES TKG 15001 02/09/2015 Index I. General Requirements II. Central Computer Recovery Requirements III. Network Recovery Requirements 1

TECHNICAL SPECIFICATIONS For DISASTER RECOVERY SERVICE SEPTA requires the ability to recover the functions and information of the mainframe computer in the event of any situation, which would render it incapacitated for an extended duration. Prospective bidders must provide written description detailing how their solution meets each of the following requirements. I. General Requirements A. The Vendor must possess sufficient experience in provision of disaster recovery services for clients of similar size and complexity. A minimum of twenty five (25) recoveries of equal or larger configurations than SEPTA must be documented, including references. B. The Vendor must provide immediate and exclusive access to center-based computer systems (Hot Site), which can attach to SEPTA's data communication network -with a reasonable expectation of resuming mainframe-computing services within an eight-hour elapsed time from declaration of the disaster. In the special case of a multiple-disaster situation in which multiple subscribers require use of the same resources, SEPTA shall be granted equal rights of access to recovery resources as the other affected subscribers. SEPTA shall cooperate with the Vendor and other affected subscribers to implement a workable multiple-disaster plan for sharing of recovery resources. C. The Vendor must guarantee the use of this Hot Site for a minimum of six weeks from the disaster declaration. D. The Vendor must provide a ready computer room (Cold Site) with sufficient electrical, air conditioning, and fire detection/suppression systems to accommodate installation and operation of SEPTA's hardware configuration following the initial recovery. E. The Vendor must guarantee the use of this Cold Site for a minimum of six months from the migration out of the Hot Site. F. The Vendor must provide a Recovery Operations Site (ROS) to be used by SEPTA personnel during testing or during a declared disaster. This facility must be located within approximately twenty-five (25) miles of SEPTA's computing facility in center city Philadelphia. The Hot/Cold Site can be located outside this area so long as the Vendor provides sufficient capabilities at the ROS to fully control testing. Network connectivity from the ROS to the Hot/Cold Site shall be included in the Vendor's cost. G. In addition to the annual contract costs, Bidder must disclose all costs associated with the proposed services, to include declaration fees, Hot Site charges, Cold Site charges, office space charges, additional test time rates and any additional charges or fees that may apply. H. The duration of this service shall be three years, with option for two (2) additional one (1) 2

year extensions. I. The Vendor must guarantee use of said equipment for testing at least six (6) eight-hour periods per contract year. All costs related to testing must be included in the bid price. J. The Vendor must provide technical support during tests and for the duration of SEPTA's recovery at the Vendor site. K. The Vendor must notify SEPTA in writing at least sixty days in advance of its intention to initiate significant changes to the equipment configuration described in the contract. SEPTA shall be granted a reasonable amount of additional free test time after every significant change. If in SEPTA s judgement following testing, the equipment is deemed substantially unusable by SEPTA, SEPTA may terminate the affected service. L. The Vendor must provide for the possibility that SEPTA may request the contractor to make special modifications to the equipment configuration specified in the contract to satisfy changing requirements. On these occasions the contractor will be given thirty (30) days of written notice as to the desired changes. The contractor must then advise SEPTA of any financial impact, and the time required to implement the change. M. The Vendor must provide continuous power for the ROS and Hot/Cold Sites. N. The Vendor must provide physical security for the ROS and Hot/Cold Sites to include at least internal and external emergency alarms, fire protection system and 24-hour security guards. 3

II Central Computer Recovery Requirements The Hot site computer system must provide capacity to recover SEPTA s hardware configuration as described below: 1 IBM zseries Process (IBM 2818-D01) 1 LPAR 40 IBM MIPS 2 GB Memory 1 OSA Express4S GbE SX 2 ports 3 OSA-Express 3-2P 1000BASET-EN 2 ports 96 3390 Mod 9 Format Disk Volumes (reside on DS8800) 64 3390 Mod 27 (reside on DS8800) 1 1 IBM 3490 Cartridge Drive 3 IBM 3592-J1A Cartridge Drives 3 IBM 3592-E05 Cartridge Drives 1 IBM 4248 Line Printer 1 Point-to-Point T1 with access to an ASN router to connect to an ARN router at 200 W. Wyoming Avenue, Philadelphia, PA. 1 CICSO ASA 5520 Adaptive Security Appliance (Firewall). 1 Internet connection at 5MB. SEPTA utilizes IBM z/os Operating System, and z/vm to host multiple Linux Virtual Machines on a single Integrated Facility for Linux (IFL). The TCP/IP network is attached via the IBM zseries 114 OSA Adapter using QDIO. SEPTA uses IBM DF/DSS to prepare the backup tape cartridges on the IBM 3592 Model J1A/E05 Tape Drives. 4

III Network Recovery Requirements Single Point-To-Point T1 The vendor shall provide an ASN router/switch, DSU/CSU, etc., required to connect a Point-to-Point T1 to an ARN router at 200 W. Wyoming Avenue, Philadelphia, PA. 5