Project Scope

This project will implement a new backup/recovery strategy. It will incorporate Oracle’s Hot backup procedure with EMC’s TimeFinder/Mirror technology to backup the production database to EMC’s BCVs. Once BCVs split, the copy on BCV will be backed up to tape. The project scope definition will be detailed in Section 3.

Project Schedule Summary

The duration of the project is expected to be four weeks from kick-off date. Below are some high level milestone dates after project starts. Days are counted in business day.

• • Day 5, Set up EMC’s SAN to connect to the database server

  • Day 7, Install EMC’s TimeFinder/Mirror software and component

  • Day 10, Set up EMC’s BCVs to mirror production volumes

  • Day 11, Establish BCVs to production volumes and split

  • Day 13, Set up jobs to backup BCVs to tape.

  • Day 14, Complete Backup/Recovery script (using Oracle hot backup and BCVs)

  • Day 18, Finish testing

  • Day 20, Finish rolling out fully to production

Project Budget Summary

The estimated budget for this project is about $50,000, which includes 500 GB EMC storage cost, EMC TimeFinder software cost and developing cost.

Quality Issues

The integrated backup/recovery strategy should produce valid oracle backups which can be used for recovery as needed. All necessary oracle database files need to be copied into BCVs and eventually backed up to tape. The integrity of Oracle Hot backup should not be changed because of this project.

Resources Required

This project requires the following resource:

• People

  • Project manager who oversees and coordinates the whole project

  • Oracle DBA who works on database related tasks and backup script

  • EMC engineer(s) who will responsible for EMC works and assist on backup script

  • Unix Administrator who will responsible for Unix work and tape backup

• Technology

  • Oracle hot backup mechanism

  • EMC TimeFinder/Mirror technology

  • Veritas NetBackup software

• Facilities

  • Current production environment in two data centers

  • Four SUN SPARC E6800 servers in one VCS cluster environment.

• Resources to be provided

  • EMC Technical Support

  • Oracle Technical Support

  • Veritas Technical Support

Assumptions and Risks

• The project assumes all above resource will be available during scheduled project timeframe. It also assumes people who participate this project have already had enough knowledge and experience about their specific areas. Therefore, technology related training is not provided for this project.

• The biggest risk involved in this project is the lack of a test environment. Due to cost and some other reasons, setting up a test environment that mimics production is not possible. As a result, all our implementation will directly happen in the production environment. This may potentially corrupt the production environment when create BCVs or test new backup script. The impact of data lost will be tremendous.

• However, not to implement this project will also cause impact to the organization. The fast growing database size makes nightly backup job takes way too long to finish. It has already exceeded business allowed daily maintenance window. Any failure of such long backup job will jeopardize the recovery of crashed production database.

Project Administration

• The project team will get together once every three days to check the status or progress. Any critical issues, constraints or unexpected accidents should be reported or escalated immediately to upper management.

• In case of modification of project scope is needed, project manager will be responsible to communicate with upper management to evaluate the impact to the project. Decision will be made based on the assessment whether to adjust related project schedule, scope and budget, etc. A formal scope change request form is needed for every scope change.

• The new backup script will be tested for its correctness and accuracy. Backups will also be recovered from both tape drive and BCVs to valid data integrity.

Acceptance and Approval

• VP, Director of IT

• CTO

• CEO

Project Execute and Control

Project Scope Statement

• Develop a new Oracle Backup/Recovery strategy that supports business’s high availability, fast growth, and flexible scalability requirement.

• Develop a mechanism that integrates Oracle “hot” (online) Backup/Recovery technology with EMC’s TimeFinder/Mirror technology.

• Integrate the new Backup/Recovery strategy with existing tape backup system.

• The new Backup/Recovery strategy only applies to production Online Trading system. It does not apply to any other environments and application systems, such as Email Messaging system or Facilities Management system.

• Technology and organizational assessment and improvement of the current environment will not be done in this project.

• Organizations involved in this project include Production Support and Infrastructure departments. Organizations not involved include Client Services, Marketing, Finance, Human Resources, etc.

• Sun SPARC database servers, tape backup servers, EMC SAN (Storage Area Network) and LAN architecture are part of the project scope. The Weblogic servers are not part of the project scope.

• Oracle software, EMC TimeFinder/Mirror and NetBackup software are part of the project scope. Online Trading Application software is not part of the project scope.

Project-Oriented Deliverables

This project will have the following deliverables:

Deliverable Definition Table

Product-Oriented Scope

The following diagram defines the features and functionality of the system to be implemented by this project.

Scope Verification

Scope definition will be carefully reviewed and must be accepted by the project stakeholders. The scope verification is to ensure both project sponsor and project team on the same page about project’s boundary, product to be produced and the project-related deliverables. The following project scope checklist will be verified.

• Is the project’s MOV clearly defined and agreed upon?

• Are deliverables tangible and verifiable?

• Are controls in place to ensure project meets specific standards?

• Are milestones defined for each deliverable?

Scope Change Control

As defined in the Project Charter to avoid scope grope, scope creep and scope leap.

 

Project Close

The project will be closed on its target date given its desired goals and objectives are achieved. The project’s acceptance will be signed by project sponsors thereafter. A final project report will be presented by the project manager. All project related documents, deliverables and resources will be completed and released.

Project Evaluation

The following steps will be performed to evaluate the project:

• Individual performance review

• Postmortem review involving reviewing of initial project’s MOV, scope, schedule, budget and deliverables, etc.

• Evaluate project success, such as assess