Who do these replica folders belong to?

Cleaning up some LUNs so I can resize them and after rebalancing all the pools the LUN I was going to remove still had some folders on it.  Most of the folders only contained a .hlog file, but a few replica folders still existed and those are a reason for concern.  Using the following SQL commands you can determin if the VM associated with the replica folders still exist, and what VM it is or was in some cases.

 

SELECT *

FROM [vmwvdb].dbo.VPX_ENTITY

where [NAME] ='replica-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'

 

Copy the ID for use in the next query as 'VM-###'

 

SELECT *

FROM [vmwv composer db].dbo.SVI_REPLICA

where [REPLICA_MOID] = 'VM-###'

 

Copy the Replica_ID for use in next query

 

SELECT [VM_NAME]

,[GUEST_COMPUTER_NAME]

,[REPLICA_ID]

FROM [vmwv composer db].dbo.SVI_SIM_CLONE

where [REPLICA_ID] ='11111111-aaaa-1111-aaaa-111111111111'

 

You should now have the VM name if it still exists in the database.

MySQL Backup script

Doing this on FreeBSD so you might need to modify the bash location for other OS choices

#!/usr/local/bin/bash
backupdir=/home/backup/
backupfile=`date +backup-%d-%m-%y_%H.sql`
tarfile=mysqlbackup.tar
cd $backupdir
mysqldump --opt -A -h localhost --password=***** -u root > $backupfile
gunzip "$tarfile".gz
tar rf $tarfile $backupfile &> /dev/null
gzip $tarfile
rm $backupfile

VMworld 2011 EUC3163 VMware View Performance and Best Practices Notes

  • vSphere 5.0 for VDI

    • 30% performance improvement measured by consolidation rati
    • Better out of the box CPU scheduling for VDI workloads
    • No special tuning required
  • Memory

    • Per VM allocation reduced significantly
    • Allows better memory over-commit/higher consolidation ratios
    • 60% less book keeping memory per 1GB RAM VM
    • transparent page sharing
  • Graphics

    • 3D support

      • 3D graphics is rendered using CPU resources
      • Eliminates cost for GPUs and special devices
      • Good for light 3D apps/Aero
      • PCoIP Server offload cards w/Teradici

        • Improved performance
        • better consolidation from offloading
  • Protocol Enhancements

    • WAN Bandwidth optimizations
    • Lossless CODEC for text improvement
    • 30% bandwidth improvement
    • client side caching
    • Build to lossless

      • Render initial image
      • Build up to lossless
      • Build until fully lossless
      • Up to 75% bandwidth improvement if disable build to lossless
  • CPU optimizations

    • Negligible PCoIP overhead for idle VMs
    • Optimizations of algorithms and core functions at a lower level
    • Reduced compression library overheads
    • Better Session Resilience

      • Session recovery during loss of network up to 30 seconds is seamless to users
    • PCoIP performance counters for session stats/performance monitoring

      • WMI based
  • Provisioning

    • Faster operations in 5.0
    • More parallelism with config parameters
  • Loading boot drives from SSD is a major performance improvement to combat boot storms




1 2 3 4 5 6 7 8 9 10 11 »