Local Streamed Desktops

Very cool option with Citrix XenDesktop

In fact, local streamed desktops have the potential to drastically reduce the costs of a desktop virtualization solution.  If you have no idea what a local streamed desktop is, then STOP.  Read about how local streamed desktops can extend virtual desktops and also look at the different FlexCast models.

http://community.citrix.com/display/ocb/2010/03/23/Question+about+Setting+up+Local+Streamed+Desktops

VMware Backups using NetBackup 7

Configuring NetBackup 7 for VMware backup (using vStorage API)

Configure VMware backup host in Netbackup

wpid745-media_1268169003053.png

right-click on master server, select “Properties”

wpid746-media_1268169032231.png

Add VMware Backup Host

wpid747-media_1268169068352.png
wpid748-media_1268169100577.png
wpid749-media_1268169133115.png

Configure Credentials on vCenter

wpid750-media_1268169159126.png
wpid751-media_1268169176234.png
wpid752-media_1268169196136.png
wpid753-media_1268169227149.png
wpid754-media_1268169251033.png

Create the backup policy for Virtual Machine Backup

wpid755-media_1268169558017.png
wpid756-media_1268169599531.png
wpid757-media_1268169638301.png
wpid768-media_1269641712723.png
The parameters shown are not the default but reflect a configuration that seems to be optimal for test environment. Your mileage may vary.
These specific parameters have been changed from the default
Client Name Selection determines how Virtual Machines are identified to Netbackup.  VM Display name option matches the VM name as identified in vCenter
Transfer type determines how VM data is transfered to Netbackup host.  The san option uses Fibre Channel or iSCSI SAN (Note:, LUNs containing VMWare Data Stored must be presented to Netbackup host).  The nbd option resorts to a network copy, should the san option fail.
Existing snapshot handling, when set to Remove NBU, will remove stray NetBackup snapshots from VMs if encountered but ignore all other snapshots.
wpid758-media_1268169703636.png
wpid759-media_1268169735435.png
wpid760-media_1268169765662.png
wpid761-media_1268169782724.png

Configure remaining backup policy options based on backup windows etc.

wpid762-media_1268169805026.png
wpid763-media_1268169823906.png
wpid764-media_1268169840241.png
wpid765-media_1268169856070.png

If options need to be changed (‘cuz mine didn’t work in your environment ;) ) , change on the policy’s attributes window

wpid766-media_1269640695368.png
wpid767-media_1269640972034.png

How to Upgrade the vCenter (VirtualCenter) SQL 2005 Express Database

VM /ETC has a great article that helped me while onsite to perform an upgrade of the vCenter SQL database from 2005 express edition to a licensed version of SQL 2005 (in my case it worked on SQL 2008).

Normally, using SQL Express for the vCenter database isn’t a bad thing necessarily, however as VM /ETC mentions in his article, VMware only supports SQL Express as the vCenter Database if your VMware environment is 5 hosts or under, 50 virtual machines or under. Also of note is that SQL express databases can only get to 4 GB in size, so if your database is getting that large, then you’ll need to upgrade for that reason too.

Here’s the link to the VM /ETC article:
http://vmetc.com/2009/01/11/how-to-upgrade-the-virtualcenter-sql-2005-express-database/

Here’s a copy/paste from his article for easy reference:

  1. Take a backup of the VC server.  If you have VC running as a Virtual Machine, it’s best to take a snapshot of it so that you have a nice clean restore point in case anything goes wrong.
  2. Shutdown any VMware services that may be using the SQL Express database.  For instance, the License service, VC service, or Update Manager.
  3. Start the SQL Installer with an argument of SKUUPGRADE=1 (e.g. setup.exe SKUUPGRADE=1) for more information about using this command argument, have a look here .
  4. When you reach the point where the installer asks if you wish to upgrade the default instance or a named instance, select named instance. Then browse to the instance named “SQLEXP_VIM” Then you can just accept the defaults for the installation.

VM /ETC’s article also has links if  you want to move your vCenter Database to another SQL server and if you want to move databases between computers that are running SQL server.

Changing or Resetting a Lost Root Password on ESX or vSphere

This lesson describes how to reset a lost password on vSphere 4 and ESX 3.x. This information is based off of VMware KB article 1317898 which can be found here:
http://kb.vmware.com/kb/1317898.

vSphere 4

1.Reboot the ESX host.
2.When the GRUB screen appears, press the space bar to stop the server from automatically booting into VMware ESX .
3.Use the arrow keys to select Service Console only (troubleshooting mode).
4.Press the ‘a’ key to modify the kernel arguments (boot options).
5.On the line presented, type a space followed by the word single.
6.Press Enter. The server continues to boot into single-user mode.
7.When presented with a bash prompt such as sh-2.05b#, type the command passwd and press Enter.
8.Follow the prompts to set a new root user password.
9.When the password is changed successfully, reboot the host using the command reboot and allow VMware ESX Server to boot normally.

ESX 3.x

1.Reboot the ESX host.
2.When the GRUB screen appears, press the space bar to stop the server from automatically booting into VMware ESX .
3.Use the arrow keys to select Service Console only (troubleshooting mode).
4.Press the ‘e‘ key to modify the kernel arguments (boot options).
5.On the line presented, type a space followed by the word single.
6.Press Enter then press the ‘b‘ key to boot the ESX host in single-user mode.
7.When presented with a bash prompt such as sh-2.05b#, type the command passwd and press Enter.
8.Follow the prompts to set a new root user password.
9.When the password is changed successfully, reboot the host using the command reboot and allow VMware ESX Server to boot normally.

ESX 2.x

1.Reboot the ESX Host.
2.When the LILO screen appears, press the space bar to stop the server from automatically booting into VMware ESX.
3.At the LILO prompt select linux, adding the -s to the end of the line. For example: linux -s.
4.Press Enter. The system begins to boot. The server continues to boot into single-user mode.
5.When presented with a bash prompt such as sh-2.05b#, type the command passwd and press Enter.
6.Follow the prompts to set a new root user password.
7.When the password is changed successfully, reboot the host using the command reboot and allow VMware ESX to boot normally.