<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vcenter on Evan Hoffman</title><link>https://evan.wtf/tags/vcenter/</link><description>Recent content in Vcenter on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Tue, 19 Oct 2010 21:44:01 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/vcenter/index.xml" rel="self" type="application/rss+xml"/><item><title>vCenter Data Migration tool doesn't restore SQL Express DB - Migrating vCenter 4.0 to 4.1 (part 2)</title><link>https://evan.wtf/2010/10/19/vcenter-data-migration-tool-doesnt-restore-sql-express-db-migrating-vcenter-4-0-to-4-1-part-2-2/</link><pubDate>Tue, 19 Oct 2010 21:44:01 +0000</pubDate><guid>https://evan.wtf/2010/10/19/vcenter-data-migration-tool-doesnt-restore-sql-express-db-migrating-vcenter-4-0-to-4-1-part-2-2/</guid><description>&lt;p&gt;I&amp;rsquo;m into my second day on this project. It appears that the backup and restore procedures run to completion but on the target machine the database is empty. This is pretty easy to check; I just went in with SQL Management Studio, looked in VIM_VCDB -&amp;gt; Tables -&amp;gt; dbo.VPX_DATASTORE and did &amp;ldquo;Open Table.&amp;rdquo; On the source machine I saw all the datastores in there (as expected). On the target machine, however, the table was empty.&#10;I found &lt;a href="http://kb.vmware.com/kb/1024380"&gt;KB 1024380&lt;/a&gt; describing a failure of the migration tool with a symptom, &amp;ldquo;Data Migration Tool logs (restore.log) does not indicate any errors, but the database is blank.&amp;rdquo; The KB says:&lt;/p&gt;</description></item><item><title>vCenter Data Migration tool doesn't restore SQL Express DB - Migrating vCenter 4.0 to 4.1 (part 2)</title><link>https://evan.wtf/2010/10/19/vcenter-data-migration-tool-doesnt-restore-sql-express-db-migrating-vcenter-4-0-to-4-1-part-2/</link><pubDate>Tue, 19 Oct 2010 21:44:01 +0000</pubDate><guid>https://evan.wtf/2010/10/19/vcenter-data-migration-tool-doesnt-restore-sql-express-db-migrating-vcenter-4-0-to-4-1-part-2/</guid><description>&lt;p&gt;I&amp;rsquo;m into my second day on this project. It appears that the backup and restore procedures run to completion but on the target machine the database is empty. This is pretty easy to check; I just went in with SQL Management Studio, looked in VIM_VCDB -&amp;gt; Tables -&amp;gt; dbo.VPX_DATASTORE and did &amp;ldquo;Open Table.&amp;rdquo; On the source machine I saw all the datastores in there (as expected). On the target machine, however, the table was empty.&#10;I found &lt;a href="http://kb.vmware.com/kb/1024380"&gt;KB 1024380&lt;/a&gt; describing a failure of the migration tool with a symptom, &amp;ldquo;Data Migration Tool logs (restore.log) does not indicate any errors, but the database is blank.&amp;rdquo; The KB says:&lt;/p&gt;</description></item><item><title>Migrating vCenter 4.0 to 4.1 (part 1)</title><link>https://evan.wtf/2010/10/18/migrating-vcenter-4-0-to-4-1-part-1/</link><pubDate>Mon, 18 Oct 2010 22:28:12 +0000</pubDate><guid>https://evan.wtf/2010/10/18/migrating-vcenter-4-0-to-4-1-part-1/</guid><description>&lt;p&gt;When vSphere 4.1 was released earlier this year, I was mildly excited. Our ESX servers are still running 4.0.0 and I had been planning to upgrade to 4.0u1 for a while. When 4.1 came out it seemed to have vindicated my procrastination: now I could just upgrade to 4.1 and take advantage of whatever new features there were (I read something about memory compression&amp;hellip; whatever).&#10;I assumed the upgrade procedure for vCenter itself would be pretty simple: uninstall 4.0 and install 4.1. Well, it turns out that&amp;rsquo;s not the case! I sat down one day to create my game plan for the upgrade and right away I learned this was going to be a lot more work than I&amp;rsquo;d guessed. From &lt;a href="http://kb.vmware.com/kb/1021635"&gt;VMware&amp;rsquo;s KB&lt;/a&gt;:&lt;/p&gt;</description></item><item><title>vCenter: Error parsing the server "(server IP)" "clients.xml" file</title><link>https://evan.wtf/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file-2/</link><pubDate>Wed, 23 Jun 2010 12:18:59 +0000</pubDate><guid>https://evan.wtf/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file-2/</guid><description>&lt;p&gt;I got the above error today after running Windows Update on my XP VM a few days ago. A quick search showed that the error is caused by a Microsoft update to the .NET framework. To resolve it, remove update KB980773 (Add/Remove programs, make sure &amp;ldquo;Show Updates&amp;rdquo; is checked; KB980773 is under &amp;ldquo;Microsoft .NET Framework 2.0 Service Pack 2&amp;rdquo;). I removed it and was able to log in without problems.&lt;/p&gt;</description></item><item><title>vCenter: Error parsing the server "(server IP)" "clients.xml" file</title><link>https://evan.wtf/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file/</link><pubDate>Wed, 23 Jun 2010 12:18:59 +0000</pubDate><guid>https://evan.wtf/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file/</guid><description>&lt;p&gt;I got the above error today after running Windows Update on my XP VM a few days ago. A quick search showed that the error is caused by a Microsoft update to the .NET framework. To resolve it, remove update KB980773 (Add/Remove programs, make sure &amp;ldquo;Show Updates&amp;rdquo; is checked; KB980773 is under &amp;ldquo;Microsoft .NET Framework 2.0 Service Pack 2&amp;rdquo;). I removed it and was able to log in without problems.&lt;/p&gt;</description></item></channel></rss>