PROJECT CHARTER

Backup Solution

VERSION: 1 / REVISION DATE: 06.06.2011

Project Leader name: Philippe MIRMAND

Approval of the Project Charter indicates an understanding of the purpose and content described in this deliverable. By signing this deliverable, each individual agrees work should be initiated on this project and necessary resources should be committed as described herein.

Approver Name / Title / Signature / Date
Davide Franco / Unix System
JC Bettinelli / VMware specialist

Many of these items listed will be visited in more detail when you start planning. The objective of the charter is to document the information as it is known at the beginning of the project – not to get into the planning itself.

[Project Name]
Project Charter [Version Number] | [Publication Date] iv

PROJECT CHARTER

[Project Name] [Version Number] | [Version Date]

Contents

Section 1. Project Overview 1

1.1 Business Needs 1

1.2 Project Description 1

1.3 Project Goals and Objectives 1

1.4 Project Scope 2

1.5 Critical Success Factors 2

1.6 Assumptions 2

1.7 Constraints 3

Section 2. Project Milestones 3

2.1 Major Project Milestones 1

Section 3. Project Organization 2

3.1 Project Structure / Stakeholders 2

3.2 Roles and Responsibilities 3

3.3 Project Communications 4

3.4 Project Facilities and Resources 4

Section 4. Project Risk management 5

4.1 High-level risks 5

Section 5. Appendices 6

Page 1

D-DIR-02-02_v2.0

PROJECT CHARTER

[Project Name] [Version Number] | [Version Date]

Section 1. Project Overview

1.1 Business Needs

Þ MIGBANK should have confidence in backup system. In terms of security and high data availability, new backup system should be implemented in a way that meets corporate objectives to insure respect of corporate guidelines and business needs.

In terms of business needs :

1.  Data should be available 99.9% of the time 24x5.5, independently of MetaTrader system (watch-dog system is using actually for MT4)

2.  We must be able to recover data that where inadvertently deleted

3.  We must be able to recover data for 10 years in the past.

1.2 Project Description

Þ It is important to understand that this project doesn’t call into question our current backup system for Microsoft environment but it will allow us to extend the new backup solution with new functionalities but also to re-centralize the backup management.

Currently, backups are managed by several people for different systems with different methods.
MetaTrader is not backed by our global backup system but with “craft method” who are not secured, sure and reliable for the future.
Vmware and SQL environment are backed with another system, independent of our global backup.

We used in the past a solution that was conform to the size of the company and to the management requirements.

Since this period, our needs have progress significantly by generating constraints, additional requests, IT system extension.

Part of this project is also to gather and clear out the governance and security requirements and to insure that proper policies, procedures and controls are documented and respected on the implementation is completed.

1.3 Project Goals and Objectives

Þ Here is a list of the goals and objectives we are attempting to meet with this project:

1.  Insure that governance and security requirements are clearly defined and endorsed by stakeholder

2.  Reduce exhaustive backup (running during 24 hours during weekend)

3.  Minimize complicated management : each admin have their own backup system :

i.  Etrading backups MT4

ii. Admin System backups windows environment on mig.lan

iii.  VMware admin backups VMware system and others domain

iv.  SQL admin backups Oracle and SQL

4.  Increase reliability : Lack of granularity to restore backup applications (Exchange, Oracle, SQL)

5.  Ensure data protection in the long term

1.4 Project Scope

Þ The project scope INCLUDE

  1. Policies, procedures and controls related to the operation, governance and security of the messaging infrastructure
  2. The technical aspects necessary to insure the proper hosting of the solution in a production grade infrastructure
  3. Security controls, auditing, logging and monitoring of the platform and access to its content.
  4. The management of all IT infrastructure environment : Microsoft, Meta Trader, Unix and VMware
  5. The tests to insure that objectives are met

Þ The project scope EXCLUDE

  1. High availability on MetaTrader system, SQL, Unix and VMware system
  2. Only log and datas should be backed from this new system

1.5 Critical Success Factors

Þ Here are the critical success factors for this project as we see them at the moment:

  1. Before implementing technical measures, clearly defined governance and security requirement must be endorsed by stakeholders
  2. When migrating on new solution, all old backup (implemented with HP Data Protector) should be import in the new system in case of restoring data.
  3. The migration should be transparent to end users
  4. No backup system cannot be interrupted during the process establishment

1.6 Assumptions

Þ The assumptions for this project are the following :

  1. Bandwidth between Neuchatel and Zurich should be up and rapid.
  2. Hardware components, such has the Storage Area Network, are available and performing to industry standard
  3. New physical server should be dedicated for implement this new solution (no VM is acceptable)

1.7 Constraints

Þ The project constraints are:

1.  Much of the migration work might have to be conducted off hours due

2.  The current bandwidth between Neuchatel and Zurich is better than before but we should carefully plan technical activities to insure as an impact as possible to other enterprise services that depend on the availability of this bandwidth during the night.

3.  Those migration projects are normally handle by consulting companies that carries them multiple time per year, we are planning to do this internally to gain experience, in collaboration with consulting company, better understanding and better control over the process but we might be lacking technical competencies (will be addressed in the Risk section)Section 2. Project Milestones

Page 1

D-DIR-02-02_v2.0

PROJECT CHARTER

[Project Name] [Version Number] | [Version Date]

2.1 Major Project Milestones

Page 1

D-DIR-02-02_v2.0

PROJECT CHARTER

[Project Name] [Version Number] | [Version Date]

Page 1

D-DIR-02-02_v2.0

PROJECT CHARTER

[Project Name] [Version Number] | [Version Date]

Section 3. Project Organization

3.1 Project Structure / Stakeholders

Describe the organizational structure of the project team and stakeholders, preferably providing a graphical depiction. Think also about project sponsor, project manager, project team members, project contributor, project delivery customer. Who will be on the team? Who is the project sponsor? What other stakeholders have already been identified?

Þ MIGBANK team :

1-  Philippe MIRMAND, in charge of backup solution at MIGBANK, will choose, along with the team responsible for the project, the final supplier and ensure that the budget is met according to the instructions requested. He will take part in different tests throughout the facility.

2-  Davide Franco, Unix admin, ensured that the proposed solution is compatible with the systems it is charging. He will take part in different tests throughout the facility.

3-  Jean Christophe Bettinelli, vmWare specialist, ensured that the proposed solution is compatible with the systems it is charging. He will take part in different tests throughout the facility.

Þ Software Suppliers :

1.  IBM for Tivoli Solution

2.  Symantec

3.  CommVault

4.  NetApp

Þ Hardware Suppliers :

1.  EMC for Data Domain appliance

3.2 Roles and Responsibilities

Summarize roles and responsibilities for the project team and stakeholders identified in the project structure above. Are there some roles/responsibilities that need to be clarified now before the detailed planning begins?

Role / Responsibility /
Project Sponsor / Admin System Team ( VMWare and Microsoft team) – Martin Dion
Project Manager / Philippe MIRMAND
Project Manager Substitute / Davide Franco – Jean-Christophe Bettinelli
Financial part / Wissam Mansour
Business Expert / Final Supplier

3.3 Project Communications

Þ Backup system stakeholder

First meeting will be setup with all suppliers who choose in section 3.1 to evaluate this project and to structure the implementation of the project.

3.4 Project Facilities and Resources

Þ Resource equipment

To maintain this project, we need to add 2 appliances to store data at Zurich and at Neuchatel from synchronizations, additional to quote supplier

Section 4. Project Risk management

4.1 High-level risks

Þ The only risk that we need to clarify with final stakeholder is to have possibility to re-use :

1-  Library to extract tape to external safe supplier

  1. We need to have access to them in case of data restore

2-  IDB in our actual backup system should be import in the new system to find all backup inventories since the beginning.

Section 5. Appendices

Include any relevant appendices.

Þ

Page 1

D-DIR-02-02_v2.0