Database Reference
In-Depth Information
Let's now take a step back and look at the overall virtualization implementation plan
and then review how a database virtualization implementation plan is different. In the
following outline, we show a fairly representative high-level plan for an organization
taking its first steps toward virtualization:
Phase 1: Requirements Gathering (Business and IT)
SLAs, RPOs, RTOs
Business requirements
Phase 2: Discovery
Inventory the current systems
Baseline the current nondatabase workloads
Compute requirements, memory, disk, and network
Assess the current physical infrastructure
Phase 3: Architecture and Design
License considerations
Rightsizing considerations
System configuration
Phase 4: Validation and Testing
Load-test the new environment
Validate failover/HA
Phase 5: Migration and Deployment
Physical-to-virtual conversions
Deployment plan
Phase 6: Monitoring and Management
Resource monitoring and alerting
Troubleshooting and support plan
Backup plan
As you review this plan, notice how it has all the basic elements you would expect.
Experience has taught us that when you are virtualizing databases, the plan is distinctly
different from when you are taking your first steps toward virtualization. Let's now look
at why a plan to virtualize a database is different.
How a Database Virtualization Implementation Is Different
In the following outline, we have an implementation plan that has been modified to fit
the steps you need to follow to successfully virtualize your databases. In Phase 1, you
are gathering the business and information technology requirements.
