150 likes | 323 Views
VMware at SWFWMD. Jack Garvey. What is SWFWMD. One of five regional water management districts for the state of Florida Four broad areas of responsibility: Water supply Flood protection Water quality Natural systems management. Where we where. Where we were:
E N D
VMware at SWFWMD Jack Garvey
What is SWFWMD • One of five regional water management districts for the state of Florida • Four broad areas of responsibility: • Water supply • Flood protection • Water quality • Natural systems management
Where we where • Where we were: • 10 ESX servers in Brooksville • 2 ESX Servers in Tampa • Approximately 130 VM servers and about 60 VM workstations • The version of ESX server was 3.0 • Vranger was in a state of constantly not backing up correctly
Where we are • Where we are: • 16 ESX servers in Brooksville • 4 ESX Servers in Tampa • 2 ESX Servers in Bartow • 2 ESX Servers in Sarasota • 20 750 gig luns presented from San to Brooksvile, 4 to Bartow, 3 to Sarasota and 4 to Tampa. • Each service office has its own San. Tampa, Bartow, and Sarasota are ISCSI • 2 Vranger Servers in Brooksville and 1 at each service office • Cont..
Where we are • Where we are (cont): • Approximately 268 VM servers and about 75 VM workstations • We have 9 clusters of Esx Servers across all service offices • The version of ESX server is now 3.5.0 Update 1 • Vranger has been updated to version3.2.4.2 and is now working very well with Data Domain • Vranger has been loaded and tested on a Vm server with version 3.2.5.6 So far has tested well getting same results as physical server. • HA and DRS are now configured for all ESX servers • Update manager has been installed and configured
How we got to Where we are. • How we got to where we are: • New projects requiring more servers, Production, Development and acceptance • Update manager was installed for virtually no downtime when pushing updates to the ESX servers • San connectivity was needed for the amount of space we required. • Data Domain was acquired to cut down on the amount of space and time needed to complete backups.
Data Domain Configuration • Data Domain Data Flow Overview • In this configuration there is no need for a physical server for Vranger.
Data Domain Configuration • Using Data Domain:: • Had to set up a VMkernel port on each ESX server to communicate with Vranger. Must be in same subnet as Data Domain and ESX servers. • Directory structure had to be setup on Data Domain. • In Virtual Console you added the Data Domain share as an NFS storage device. • CIFS (Common Internet File System) is used to be able to view the directory structure in windows. This is used for file level restores from Vranger. • File level restores are now a matter of a few minutes as opposed to 20 – 40 minutes before. • .
Data Domain Compression On bkvdd01: Total files: 5,703; bytes/storage_used: 16.9 Original Bytes: 15,487,321,427,962 Globally Compressed: 1,580,860,214,777 Locally Compressed: 911,374,049,611 Meta-data: 5,225,289,304 On bkvdd02: Total files: 8,930; bytes/storage_used: 17.7 Original Bytes: 16,384,582,995,066 Globally Compressed: 1,496,833,113,939 Locally Compressed: 921,967,281,592 Meta-data: 5,022,873,216
Data Domain Compression On bardd01: Total files: 183; bytes/storage_used: 20.1 Original Bytes: 443,793,410,089 Globally Compressed: 35,970,881,615 Locally Compressed: 21,971,571,152 Meta-data: 117,670,936 On sardd01: Total files: 150; bytes/storage_used: 27.5 Original Bytes: 460,414,079,515 Globally Compressed: 27,881,649,808 Locally Compressed: 16,650,270,865 Meta-data: 93,066,352
Lessons learned • Lessons Learned: • When updating virtual center it is recommended to put all ESX servers in maintenance mode. We did not and had problems with HA. Had to create a new cluster and remove the ESX servers from the original cluster. Then applied HA to the new cluster. Once that was done we could move the ESX servers back to the original cluster. Tech support said this pushes a new HA client to the machine, if it already had HA in its cluster it may not update the HA client on each ESX server. • Setting up ISCSI sans, it is easier for the San Administrator to identify and give names to the connections, and then let virtual center find them and configure for each server. • Cont.
Lessons learned • Lessons Learned (cont) • Using Data Domain for file level restores it is important to give full rights to the directory you are wanting to do a file level restore from. As it needs to write back to that directory, by default there are only read rights. Data Domain is working on this with Vizioncore • EVC (Enhanced Vmotion capability) When using HP servers there is a setting in the bios that needs to be changed in order for it to work. The setting is under the advanced CPU options in the bios. You need to enable the No Execute Memory option. This will allow EVC to work This is not documented anywhere that we had seen..
Where we are going • Where we are going: • Virtualizing as many servers as possible. We have about 14 more physical servers we can virtualize. • Evaluating a monitoring and reporting tool for VMware. • Creating less clusters and adding ESX servers with the new CPU compatibility in 3.5.0 Release 2. • Getting all ESX Server up to version 3.5.0 Release 3. • Converting Ranger servers to VM’s
Questions and Comments • Questions and Comments