1. 1 Storage Position

2. 2 ITSD EA Challenges – Near and Far  DC Migration  DR Position and Asynch Replication  Existing LUN Sizing – Volume groups created through adding many small luns  Storage Constraints - Significant demand for new disk – Project - Last request 500 – 800 TB to facilitate N + 4 landscape approach  Size and number of Disk Pools constraining disk capacity  Performance limitations in SAP Non prod landscapes on SATA disk  Need to remain operationally flat over the next 5 years (SW Licensing & maintenance)  Growth projections increasing beyond the expected 3% - Volatile  Need to be agile for unexpected demand - SAP Near Zero Downtime - ? Late 2014 (undefined approach)

3. 3 ITSD EA VMAX Proposal Two EMC Enterprise class (6x9’s of availability) arrays consisting of: WLDC – 6 engine with 745TB usable capacity and 1.15TB Cache CIDC - 6 engine with 650TB usable capacity and 1.15TB Cache Capacity on demand – fully populated arrays to provision unexpected Array based licensing for : *reference slide 2 under financial benefits -Fully Automated Storage Tiering/ Symmetrix Mgmt Suite -SRM Suite -TimeFinder Clone/Snaps -SRDF (Array Based replication) EMC Advanced Performance, Dynamic Caching software and Priority Controls Software 5 years hardware & software maintenance (7x24x365) x2 Brocade DCX8510-8B w/ 4-16GB 48 port cards (5yrs maintenance) Professional Services (data migration, design and implementation & T/E) EMC 6 Month dedicated Storage resident for migration and transition purposes

4. 4 ITSD EA VMAX Approach High Level Migration steps : Install VMAX at CIDC and Edmonton Install Swing box at Shaw Establish SRDF/A replication between the two VMAX’s At CIDC IBM configures host based lpar migration from VSP to VMAX As the data is mirrored in host based lpar migration to VMAX it will be replicated to VMAX in Edmonton Migrate hosts from VSP to VMAX at CIDC using host based LVM migration to VMAX. During the migration data is protected because it's a host based mirror so if something fails they could simply restart. Shaw Migrate data using array based tool Once data is migrated shut down host and zone it to Swing box All hosts on Shaw are running off if the Swing box Configure replication (SRDF) or open replicator live migration from Swing box to VMAX in Edmonton. The hosts stay online so the migration can take as long as it takes Once the migration is complete,shut down the host in Shaw, do the final incremental push and then the data is in Edmonton Zone and mall the new hosts in Edmonton to the migrated volumes Ship VSP to Edmonton and set it up as FTS

5. 5 ITSD EA Migration and Replication

6. 6 RISKS : DC Relocation with additional EMC Storage using LVM to Migrate –Pros Provides ATB additional capacity needed at CIDC/SHAW and new EMC at WLDC –Cons Additional HW must be installed and Configured -> EMC LUNs need to be created on EMC arrays VIOs need additional drivers and reboot is required which affects all LPARs on the p780s. Would require careful planning and LPAR co-ordination with VIOs reboots to minimize impact LPARs need to be configured with LVM to migrate storage to XIV by writing to 2 copies at the same time Replication is now between EMC at Shaw/CIDC to WLDC which represents new storage and new technology and DR Presence of Core Banking will not be validated until Sep/Oct with this new technology –Impact to timeline Based on high level estimate this would add approximately 2-3 months to the overall timeline –Impact to Risk Affects overall risk to timeline as we are injecting additional storage arrays, new driver requirements, migration to the arrays as dependencies to DC Relo