crazex's Posts

I'm not familiar with the HP monitoring agents, however, you should be able to install them in ESXi. I would imagine that HP has some documentation for this. I have my Dell OpenManage agents in... See more...
I'm not familiar with the HP monitoring agents, however, you should be able to install them in ESXi. I would imagine that HP has some documentation for this. I have my Dell OpenManage agents installed on my ESXi 4.1 servers. Keep in mind, with ESXi, you're just installing the agent. You'll need a management console somewhere to view the status reports from that agent. ESXi will not allow you to host the systems management page on the ESXi server. -Jon- VMware Certified Professional
That is what I was explaining. The option, I believe, used to be called "export". I'm glad everything worked out for you. -Jon- VMware Certified Professional
If you browse the datastore, where you have your virtual machines, you will see that there is an option to export them. I would unregister them first, then browse the datastore and use the expor... See more...
If you browse the datastore, where you have your virtual machines, you will see that there is an option to export them. I would unregister them first, then browse the datastore and use the export option. -Jon- VMware Certified Professional
If you're planning to do an upgrade, and you've scheduled down time, why not just export the virtual machines to a file server or external drive? This will take VCB, and converter, out of the e... See more...
If you're planning to do an upgrade, and you've scheduled down time, why not just export the virtual machines to a file server or external drive? This will take VCB, and converter, out of the equation. You can then upgrade your hosts to ESX/ESXi 4.1 and in then import the virtual machine files once you have everything setup. To me VCB is just adding an unneccessary step to your upgrade. If you were using shared storage it would make your upgrade much easier, as you could migrate the VMs to the other host, and do an in place upgrade. -Jon- VMware Certified Professional
If you have an active support contract, with VMware, your licenses should have already been upgraded to the vSphere model. There is not reason that you cannot upgrade to ESXi; however, it won't ... See more...
If you have an active support contract, with VMware, your licenses should have already been upgraded to the vSphere model. There is not reason that you cannot upgrade to ESXi; however, it won't be and "in place" upgrade, the way that ESX is. However, if you're going through the upgrade process now, you may as well move to ESXi, as VMware has stated that 4.1 is the final version that will use ESX. All future version will run on ESXi. Another thing to keep in mind is that you'll need to upgrade to vCenter 4.1, which requires a 64bit version of Windows. -Jon- VMware Certified Professional
Unless VMware has changed something recently, the quorum disk needs to be be a Physical RDM. I blieve that iSCSI will work, but I know that Microsoft wants FC. I've actually been looking to set... See more...
Unless VMware has changed something recently, the quorum disk needs to be be a Physical RDM. I blieve that iSCSI will work, but I know that Microsoft wants FC. I've actually been looking to setup something similar, however, I've been planning to do have 1 VM and 1 Physical server for my SQL cluster. -Jon- VMware Certified Professional
I think that your best bet would be to use something like vReplicator, from Vizioncore. I know this won't do real-time replication, but it is meant specifically for DR purposes. Also, if your S... See more...
I think that your best bet would be to use something like vReplicator, from Vizioncore. I know this won't do real-time replication, but it is meant specifically for DR purposes. Also, if your SAN as some form of replication, you could attempt to use that to replicate the data. The only problem that I could see with that would be the file system would need to be quiesced to ensure that your data is consistent. -Jon- VMware Certified Professional
These licensing models were implemented with Server 2k3 R2 and SQL 2005 SP2. I agree that the Windows Data Center license is a must, but 40k for SQL proc licenses will take a ton of SQL VMs... See more...
These licensing models were implemented with Server 2k3 R2 and SQL 2005 SP2. I agree that the Windows Data Center license is a must, but 40k for SQL proc licenses will take a ton of SQL VMs to break even.
You are correct. This was a feature that Microsoft announced with the launch of SP2 for SQL 2005. I had looked into this, as my company uses SQL pretty heavily. I decided against this licensin... See more...
You are correct. This was a feature that Microsoft announced with the launch of SP2 for SQL 2005. I had looked into this, as my company uses SQL pretty heavily. I decided against this licensing model is it costs almost $40k per ESX host, and I'm not sure I could run enough instances of SQL on a host to offset that cost. -Jon- VMware Certified Professional
Restarting the mgmt services was the first thing that I tried. When I get some time, I'm going to reboot the host, and see if the problem clears itself up. If not, I'll try reinstalling ESX. ... See more...
Restarting the mgmt services was the first thing that I tried. When I get some time, I'm going to reboot the host, and see if the problem clears itself up. If not, I'll try reinstalling ESX. -Jon- VMware Certified Professional
The server only has 1 x6 backplane. It has spots for 6 3.5" SAS drives. The server is a Dell PowerEdge 2950. The firmware on this machine is identical to that of my other hosts, which are also... See more...
The server only has 1 x6 backplane. It has spots for 6 3.5" SAS drives. The server is a Dell PowerEdge 2950. The firmware on this machine is identical to that of my other hosts, which are also 2950s, and none of them have this problem. The 4 SAS drives in the server are located in bays 0-3. Also, as stated above, the drives are configured in a RAID 5. The only place I see this error is in VC. The server reports no problems with any of the drives. -Jon- VMware Certified Professional
This happens to me, when I install updates to my hosts. Since DRS is based on active resources, not allocated resources, it doesn't move the VMs back to the other server, even though it seems li... See more...
This happens to me, when I install updates to my hosts. Since DRS is based on active resources, not allocated resources, it doesn't move the VMs back to the other server, even though it seems like you've overloaded the other host. When the machines start to become more active DRS will move them accordingly. If you're really worried just manually migrate them to the other host. -Jon- VMware Certified Professional
I've recently applied Update 4 to my VI3 cluster. The upgrade went smooth, and everything has been running fine for about 3 weeks now. I noticed yesterday that one of my hosts was reporting a... See more...
I've recently applied Update 4 to my VI3 cluster. The upgrade went smooth, and everything has been running fine for about 3 weeks now. I noticed yesterday that one of my hosts was reporting a critical state. When I use VC to check the health status I see that the critical alert is coming from Storage. The alert that I get is: Disk Drive Bay 1 Drive 1: in Critical Array - Assert This message appears for Drive 1 - Drive 7. The host does not have 7 disks. It has 4x73GB 15k SAS drives configured in a RAID5, in slots 0-3. The server is not reporting any errors, and Open Manage also reports no errors. I tried searching the community, but I wasn't able to find a post with a similar issue. Any help would be greatly appreciated. This problem does't seem to be affecting the server, but I'd like to get it cleared up. I've attached a screen, of the alert, from VC. -Jon- VMware Certified Professional
Argyle is correct. The reason you need to license both processors, is that a VM can grab either processor to perform operations. Just because the VM has 1 vCPU doesn't mean that it is tied to j... See more...
Argyle is correct. The reason you need to license both processors, is that a VM can grab either processor to perform operations. Just because the VM has 1 vCPU doesn't mean that it is tied to just 1 pCPU. Also, keep in mind, if this VM will leverage HA/VMotion/DRS, you will need proc licenses for all of your ESX hosts. This licensing model can get VERY pricey. I guess it makes sense if you are running a ton of SQL servers. -Jon- VMware Certified Professional
Our environment consists of many virtual andy physical servers. We sync our Windows time server to external sources, and sync everthing in AD to this server. We also have NTP setup on our ESX h... See more...
Our environment consists of many virtual andy physical servers. We sync our Windows time server to external sources, and sync everthing in AD to this server. We also have NTP setup on our ESX hosts, and sync them to the same external source as our Windows time server. Really the only reason that we use this model, is that we started with all physical servers, so the time server configuration was already in place. When we added VI3 we decided to keep the time sync the same. I'm not sure that sync with Windows Time vs. VMTools makes much of a difference though. As long as your time servers sync to a good external source, you should be fine. -Jon- VMware Certified Professional
I agree that Compellent is a great product. It is a bit more expensive than the solutions originally listed (Equalogic, AX150, etc). That being said, it does offer quite a bit more feature wise... See more...
I agree that Compellent is a great product. It is a bit more expensive than the solutions originally listed (Equalogic, AX150, etc). That being said, it does offer quite a bit more feature wise. We've had our Storage Center for almost 3 years now, and it has run flawlessly. We've already gone through an upgrade, so we now have 3 tiers of storage (FC, FATA, SATA). We run both our VI3 envrionment and our Lab Manager environment on the Storage Center and it works great. Our VI3 cluster is connected via FC and our Lab Manager is connected via iSCSI. One feature that goes by the wayside, at least until vSphere 4 is released, is the thin provisioning of the disk. All in all, I wouldn't hesitate to recommend the Compellent solution to anybody, but I'm just not sure how much the OP is looking to spend. -Jon- VMware Certified Professional
Are you using iSCSI or FC connections to the SAN. If FC, did you zone the storage to the ESXi host? If iSCSI is you HBA recognizing the storage location? Also, when after you created the volum... See more...
Are you using iSCSI or FC connections to the SAN. If FC, did you zone the storage to the ESXi host? If iSCSI is you HBA recognizing the storage location? Also, when after you created the volume in Storage Center did you map it to the ESXi host? Did you map it using an existing LUN number? -Jon- VMware Certified Professional
The other thing that your forgetting, which is the reason most people opt to go with VMware, is TCO. Yes, the VMware VI licensing is a bit on the pricey side, but if you look into it, and calc... See more...
The other thing that your forgetting, which is the reason most people opt to go with VMware, is TCO. Yes, the VMware VI licensing is a bit on the pricey side, but if you look into it, and calculate TCO, it is a huge savings. Take your example, 1 server is $2k. If you needed to run 8 servers, given this model, it would cost you $16k. If you leverage the full scale VI3 Enterprise license, it will cost you $2k for 1 server and $6850 for the VI3 license, which equals $8850. With the specs of your servers, running 8 virtual machines would be very simple, and save you roughly 50% of the costs of physical servers. I do think that your best bet is to give ESXi a try. It will give you a great introduction to the VMware offerings. Granted you will lose some of the enterprise functionality, but for the price (free), I don't believe there is a better entry level virtualization product. -Jon- VMware Certified Professional
As mostly everyone has already stated, yes, you can build a VM from scratch and then load XP. To build the VM, you'll need to download one of the VMware products. Either Server or Workstation... See more...
As mostly everyone has already stated, yes, you can build a VM from scratch and then load XP. To build the VM, you'll need to download one of the VMware products. Either Server or Workstation. From there, you'll need to load it onto your existing computer, or another one that you have access too, and then configure the VM. Once that is done, you'll need to install XP, and do all of your guest configuration. Once you are done with the guest configuration, you can compress all the VM files and store it somewhere, in case of a disaster. You will, however, need to have another machine which is running a VMware product, to launch this VM. I know VMware gives their users a laptop/desktop, and then a VM on a DVD, which contains the build that can access their enterprise network, but they don't do any special customization to the laptops/desktops. -Jon- VMware Certified Professional
Are the apps on these servers experiencing any problems which you would normally attribute to paging? Here of late, I've come to question the accuracy of Task Manager, as I've even been on the p... See more...
Are the apps on these servers experiencing any problems which you would normally attribute to paging? Here of late, I've come to question the accuracy of Task Manager, as I've even been on the phone with M$, and had them tell me, that info in Task Manager is not necessarily correct. They tend to lean towards perfmon reports showing a more "accurate" number. Have you tried loading Process Explorer on the VM, and checking for any difference in your results? -Jon- VMware Certified Professional