Essay on Sample of Ieee Test Plan for P2V Conversion
DIVSS160 Server P2V Action Test Documentation (IEEE Standard)
(ANSI/IEEE Standard 829-1983)
Server Name: | DIVSS160 | Change Action: | P2V (Physical to Virtual Conversion) | Server Impact On Business In Failure: | High | Incident Number: | | Change Reference Number: | CRQ000000018241 | Author Name: | Andrew McLintock | Author Designation: | Solutions Architect / Team Lead | Project: | SQL Compliance | Proposed Date Of Change Action: | 10 November 2012 | Create Date: | 12 October 2012 | Last Revised Date: | 1 November 2012 | Current Version: | 2.1 | Document Path: | C:\Users\Amclintock1\Documents\IEEE-Testplan-DIVSS160-V2.1.Docx |
`Contents …show more content…
The VIRTUAL DIVSS160 server is being allocated 4 x 3Ghz Virtual Processors with 64Gb of RAM.
Failover clustering is vastly enhanced with Windows Server 2008 and is a core feature in your virtualized environment. The clustering technology is now easier to configure, self-validating, more reliable (quorum resource is no longer a single point of failure), and better integrated with your storage solution. The storage features include adding disks to the cluster while the resources are online, better performance and stability, larger disk partitions, and the ability to perform storage maintenance with less disruption to the cluster.
Currently there is NO DR (Disaster Recovery) measure in place should there be any form of failure on the DIVSS160 Server, which is one of the most business-critical reporting servers in the SAB collective.
The end-state DIVSS160 Virtual Server is to be hosted on a 7-Node Cluster with full O/S level failover in the event of disaster.
High-Level Processes & (Pre and Post Change) Tasks
During the analysis of the DIVSS160 server, in preparation for this P2V change, a few things have come to light that have caused us to propose preparatory