We have recently updated our View v5.0 system to View v5.1 by closely following the instructions in the published upgrade guide.
Our VDI system seems to be working OK in general since this upgrade. However, we have encountered the following new issues. Just wondering if anyone else has experienced the same and/or may have any advice please ?.
2012-06-26 17:42:10,000 | 31 | INFO | CommonLib.Util.Util - Will retry after 0 seconds. The retry number is 1.
2012-06-26 17:42:10,000 | VC thread | INFO | CommonLib.VcSubsystem.PropertyCollectorUpdateTracker - Got SimVcSubsystemException RequestCanceledFault fault was thrown by the VC server: https://na-vdi-vcenter.stud.ad.eiu.edu.au:443/sdk..
2012-06-26 17:54:22,971 | 30 | INFO | CommonLib.Util.Util - Will retry after 0 seconds. The retry number is 1.
2012-06-26 17:54:22,971 | VC thread | INFO | CommonLib.VcSubsystem.PropertyCollectorUpdateTracker - Got SimVcSubsystemException RequestCanceledFault fault was thrown by the VC server: https://na-vdi-vcenter.stud.ad.eiu.edu.au:443/sdk..
Perhaps these are just some new bugs included in View v5.1 ?. Not a big deal so we are just working around them for now but it would be excellent to be able to fix these up.
No, unfortunately this delay problem was never resolved so we have just been living with this 30min delay when creating a new pool. We did place a service call with VMWare but they were unable to replicate the problem on their own test systems and in the end they were unable to assist.
We are hoping this issue will be "magically" fixed by the next View 5.2 update when it's installed.
It has been my experience over many upgrades that what you should do is not upgrade. Build a fresh environment, it is cleaner.
I have 5.1 freshly built and creating a new pool with host caching is really quick, mainly because I have the replicas and OS on SSD.
Correct this happens when host cache is enabled.
Details about host cachine is here http://communities.vmware.com/docs/DOC-19439
If you are constantly changing settings and working on the pool you may want to set a block out period, that way if it works the way I believe it does the digest should recompute during the blackout periods. Let me know how you go.
This defines recurring schedule for which the cache regeneration should not be performed. This option allows the administrator to plan the 'digest recompute' to run only during non-business hours, off-peak schedule etc. Refer figure 4. Here the cache regeneration is not performed during 9 AM to 6 PM on all week days