• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

2.5

VirtualCenter log files in your temp directory

Duncan Epping · Sep 8, 2008 ·

By default your VirtualCenter logfiles are stored in a temp folder(as of 2.5 they are stored in: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs). VMware Wolf wrote a nice article about all the locations these log files are stuffed. For some reason I don’t get a pleasant feeling when I store my VirtualCenter (VPXD) log files in a temporary windows directory or the profile directory for that matter(thanks for the comment!!). If there’s one thing admin’s clean up first when they tend to run out of diskspace it’s their temp directory… it’s called temp for a good reason!

So in order to prevent this you could change the location of the VPXD log files very easily. Edit “vpxd.cfg”. It’s located here: %AllUsersProfile%\Application Data\VMware\VMware VirtualCenter\.

Add the following lines in the “<config>” section and change the path accordingly:

<log>
<directory>c:\VC_Logs</directory>
</log>

What if my VirtualCenter server crashes?

Duncan Epping · Aug 5, 2008 ·

Seva, a VMware Technical Account Manager, put together a cool table with the implications of a VirtualCenter crash. This is a follow up to my blog about VirtualCenter getting more important by the minute. I think the most important thing to remember is that the VM’s keep running whatever happens to your VC Server and HA will still work if VC fails, well except for adding hosts to the cluster of course. So reinstalling the VirtualCenter server and re-adding the hosts is still possible, but in my opinion not recommended. Especially when you’ve got complex Resource Pools and Folder structures set up.

Open this link to the PDF or click on the picture below.

Follow Up: HA Change (isolation response)

Duncan Epping · Jul 31, 2008 ·

I’ve been asking around why the default isolation response has been changed from “power off” to “leave powered on”. It seems that this is done because a lot of customers had VM’s being powered off unnecessary. This happened because the service console or physical switches weren’t setup redundant and thus caused HA to kick in. In other words, for those having complete redundancy, switches and nics, change the default back to “power off” or use the new option “Shutdown VM”.

Shutdown VM requires VMware Tools to be installed. If HA is unable to shutdown the VM within 5 minutes it will be powered down. I would prefer this option, especially when you virtualized services like Exchange, SQL, Oracle etc.

VirtualCenter database

Duncan Epping · Jul 31, 2008 ·

There has always been much discussion about the VirtualCenter database if it was important enough to back it up. Most people agreed that the information that the database held was not important. A datacenter and cluster could be easily reconfigured and all other settings were saved on the host. HA wasn’t even using VirtualCenter, and DRS well a day without DRS is something most companies could afford.

VirtualCenter 2.5 already contained a feature called “Distributed Power Management”, with this feature the VirtualCenter database became more important but still one could easily do without it. But VMware just released VirtualCenter 2.5 Update 2. This update contains a new feature for HA. HA will get it’s IP info straight from VirtualCenter instead of the /etc/hosts file or DNS. With this info HA fills up /etc/FT_HOSTS. This all of a sudden makes the VirtualCenter database and the VirtualCenter server more important than ever.

I guess it’s time to start building the VirtualCenter server in a different way. Going virtual might be the best solution for having a highly available VirtualCenter server and database. But what about actually backing up the Database, via a maintenance plan or a backup engine. In time the VirtualCenter database will only get more important, especially when for instance DPM evolves. I can imagine DPM will detect trends and switch servers on and off accordingly.

Anyway, the only message I wanted to get out is start backing up that database!

Cool feature of the VMware Converter plugin

Duncan Epping · Jul 30, 2008 ·

How about backing up that dreadful application/server that you couldn’t or did not wanted to virtualize to your ESX environment? It could be useful to have a copy of a server that for whatever reason you did not virtualize. The new VMware Converter plugin for VirtualCenter gives you this option. You can create a reoccurring schedule for a p2v, you can even save several version of the converted machine. How cool is that! Seems like a great way to backup a machine!

How do I do this:

  1. click on scheduled tasks
  2. click new and pick “import a machine”
  3. select “physical” and enter the servers name/ip and username and password
  4. select the disks you want to import
  5. type a name for the VM
  6. select the destination host
  7. select a datastore
  8. select a network
  9. and schedule the task!

  • Go to page 1
  • Go to page 2
  • Go to page 3
  • Interim pages omitted …
  • Go to page 7
  • Go to Next Page »

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

May 24th – VMUG Poland
June 1st – VMUG Belgium

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in