Archive

Archive for November, 2009

VMWare Data Recovery 1.1 released.

20/11/2009 Leave a comment

VMWare has released VMWare Data Recovery 1.1.

Some of the changes are:

  • GUI File Level Restore (FLR) client for Windows virtual machines.
  • Integrity Check Stability and Performance Improved
  • Integrity Checks Provides Improved Progress Information
  • Enhanced CIFS Shares Support
  • Support for backing up Windows 2008 R2 and Windows 7 virtual machines (requires upgrading to vSphere 4.0 Update 1)
  • Datarecovery.ini – this file allows customization of the VDR parameters such as how frequent integrity check and reclaim operations run, maximum concurrent backups allowed and disabling any file level restore operations.
  • Ability to add network shares using fully qualified domain name or IP address.

The updated version can be downloaded here
Documentation can be found here

I hope this release fixes all my integrity check errors which made VDR unasable so far. I’m going to try in right away and let you know!

23-11 Update: Tried i for a few days now. All went ok but now i have one backup job stuck at 99% for two days.

12-12 Update2: Backups are running ok. Only one W2K VM backup keeps getting stuck at 99%

Advertisements
Categories: VDR Tags: , , ,

Changing the block size of the local VMFS during install..

12/11/2009 Leave a comment

Finally someone (PatrickD) found out a way to change the block size of the local VMFS during install. I remembered i had tried to increase before. Nowadays i create a dedicated VMFS for the service console.

 

There isn’t an easy way of doing that right now. Given that a number of people have asked for it we’re looking at adding it in future versions.
If you want to do this now, the only way to do it is by mucking around with the installer internals (and knowing how to use vi). It’s not that difficult if you’re familiar with using a command line. Try these steps for changing it with a graphical installation:

  1. boot the ESX installation DVD
  2. switch to the shell (Ctrl-Alt-F2)
  3. ps | grep Xorg
  4. kill the PID which comes up with something like “Xorg -br -logfile …”. On my system this comes up as PID 590, so “kill 590”
  5. cd /usr/lib/vmware/weasel
  6. vi fsset.py
  7. scroll down to the part which says “class vmfs3FileSystem(FileSystemType):”
  8. edit the “blockSizeMB” parameter to the block size that you want. it will currently be set to ‘1’. the only values that will probably work are 1, 2, 4, and 8.
  9. save and exit the file
  10. cd /
  11. /bin/weasel

After that, run through the installer as you normally would. To check that it worked, after the installer has completed you can go back to a different terminal (try Ctl-Alt-F3 since weasel is now running on tty2) and look through /var/log/weasel.log for the vmfstools creation command.

Hope that helps.
–Patrick.

Categories: VMWare, vSphere Tags: ,