VMware Datarecovery Kernel Panic possible solution

Since May ( Post ) I was facing multiple Kernel panic’s in my VDR appliance. Now I got something like a fix which is running quite smooth in my environment.

1. Deploy a new VDR 2.0 appliance
2. SSH in or log into the console (root/vmw@re) 3. Install this kernel.
rpm -i http://elrepo.org/linux/kernel/el5/x86_64/RPMS/kernel-ml-2.6.39-4.1.el5.elrepo.x86_64.rpm
4. Set the kernel as the default one. (You can manually select this one at. The command just sets grub to boot the first kernel in the list) sed -i ‘s/default=1/default=0/’ /boot/grub/menu.lst 5. Reboot.
6. Confirm we are running on the new kernel # uname -r 2.6.39-4.1.el5.elrepo

Give it a try and if possible provide me with your experiences.

Memory leak in VDR 2.0

Yes there is a memory leak in the current Version of VDR 2.0. After some days the VDR crash’s with the Message “Out of Memory”.

Get PID of datarecovery process

ps -ef | grep datarecovery

Check with pmap to display information about the address space of a process

pmap -x PID

Search for “anon” messages. Anon messages are blocked Memory spaces.

Current workaround is to schedule an maintenace of the destinations and then restart the VDR Appliance on a daily base. It should be possible to use scheduled tasks for the automated restart.