|
Closed
|
Case #
|
10018
|
|
Affiliated Job:
|
New Trier Township District 2031
|
|
|
Opened:
|
Monday, June 1, 2009
|
|
Closed:
|
Monday, August 31, 2009
|
|
Total Hit Count:
|
29677
|
|
Last Hit:
|
Friday, April 19, 2024 4:21:54 PM
|
|
Unique Hit Count:
|
8672
|
|
Last Unique Hit:
|
Friday, April 19, 2024 4:21:54 PM
|
|
Case Type(s):
|
Server, Vendor Support
|
|
|
Case Notes(s):
|
All cases are posted for review purposes only. Any implementations should be performed at your own risk.
|
|
|
|
Project:
|
|
Summer 2009 project was to implement a four server clustered vSphere version 4.0 infrastructure. This was to include vCenter, Update Manager and VMware Data Recovery Manager. We used the services of a consulting company to assist with the server acquisition , best practice deployment of this environment, build and follow through. My role was to perform the migration while the consulting group planned, carved out the data in the SAN and supervised/instructed the process.
|
|
|
Action(s) Performed:
|
|
Total Action(s): 1
|
|
Action #
|
Recorded Date
|
Type
|
Hit(s)
|
User
|
Expand Details
|
|
10067
|
2/16/2010 3:54:53 PM
|
Server
|
3377
|
contact@danieljchu.com
|
We purchased the servers through Dell, extended our already existing EMC SA Collapse ...
|
Last Hit: Friday, April 19, 2024 4:21:47 PM
We purchased the servers through Dell, extended our already existing EMC SAN to a CX4-120 which EMC performed the upgrade and configuration, the lead from the consulting group planned out the data and we began our deployment of the first two VM host servers.
| - | The first two were deployed as ESX version 3.5 with Navisphere multi-path and Dell OpenManage 6.01, | | - | vCenter was deployed as a guest with Update Manager and Converter on the vCenter instance, | | - | Templates were created 2003 Std. 32-bit; 2008 Std. 32-bit; 2008 Std. 64-bit; and 2008 Ent. 64-bit, | | - | Physical servers were p2v'ed (Physical to Virtual) (these were being performed by the consultant and a colleague), | | - | The consultant indicated best practice was to rebuild as many of the servers to be brought voer as possible, rather than P2V'ing them; therefore, I was tasked to rebuild: | | | o | 3 Domain Controllers 2003 32-bit Std. [CA/IAS/DHCP/DNS] Rebuilt as 2 2008 64-bit Std. & 1 2008 64-bit Ent. [CA/NPS/DHCP/DNS] | | o | Exchange Client Access Role 2007 on 2003 64-bit Std. Rebuilt at Client Access Role 2007 on 2008 64-bit Std. | | o | Exchange SC Clustered Mailbox Role 2007 on 2003 64-bit Ent. Rebuilt as Non-Clustered, Single Mailbox Role 2007 on 2008 64-bit Ent. | | o | Primary Shared SQL 2005 32-bit on 2003 32-bit Std. Rebuilt as SQL 2005 64-bit on 2008 64-bit Std. | | o | Couple IIS 6.0 Web Servers on 2003 32-bit Std. Rebuilt as 1 IIS 7.0 on 2008 64-bit Std. & 1 IIS 6.0 on 2003 32-bit Std. | | o | DMZ Microsoft DNS on 2003 32-bit Std. Rebuilt as M.S. DNS on 2008 64-bit Std. | | o | DMZ Microsoft Media Services on 2003 32-bit Std. Rebuilt as M.S. Media Services on 2008 64-bit Std. | | o | 2 File & 2 Print Servers on 2003 32-bit Std. Rebuilt as 2 File Servers on 2008 64-bit Std. & 2 Print Servers on 2008 32-bit Std. | | o | As well as deploying two new servers for Library (2008 64-bit Std.) & Finance (2003 32-bit Std.) services |
| | - | After completion of the SAN carving, Infrastructure/vCenter/vMotion/Update Manager/Resource Groups/DRS/HA design & build, P2V'ing and Server Rebuilding. We integrated the two remaining servers as vSphere version 4.0 into the cluster, migrating systems onto these new VM hosts to review the newly released host operating system. We believed the new revisions to be adequate and followed up by upgrading VM host Server 1 & 2 to vSphere version 4.0 and upgraded all the VMTools & and virtual hardware of each guest to the latest VMTools and virtual hardware version 7.0 releases. The OpenManage version was upgraded to pre-released 6.1 due to the 64-bit nature of the newly released vSphere version 4.0 OS. |
|
|
|
|
|
Outcome:
|
Following completion of the prior activities and our contract with our consultants, we began to experience issues with the server hardware acquired from Dell. Power redundancy failures on the R710 servers were popping up and in the end we replaced an entire system which required me to rebuild that system from scratch and re-introduce it into the 4 server cluster.
In the end we have experienced a number of issues with the newly released version 4.0 of vSphere and the Dell PowerEdge R710 servers. Everything operating well while under ESX 3.5, following the upgrade to vSphere we have encountered numerous issues which has been both hardware and software related. As we come close to U2 of vSphere version 4.0 I feel we are finally arriving at a point where we can operate adequately at this revision.
|
|
|
|
|
|
|
|
