Asigra doesn’t technically support their DS-Client on Ubuntu.  It’s very understandable that they can’t be responsible for making sure software runs on all of the hundreds of flavors of Linux (and there are hundreds). Some of us however do really enjoy using Ubuntu.  I’ve been using it in production since 6.10 LTS. This being said, I wanted to get the DS-Client installed on it so I could use it in my own environment as well as other customer environments as a cheap (and familiar) alternative to the support and non-free Red Hat and SUSE.

One other thing I should mention is this installation is for the -console install only. I would rather not deal with a GUI on a Linux server.  That’s why we have the DS-User!

This is process is unsupported but in my experience it works brilliantly! I hope you find this step-by-step helpful!

UPDATE: It should be known this process is for a 32bit Ubuntu installation. There seem to be some issues with the 64bit install.  Hopefully I can come up with a solution.  If anyone else has one – please share!

Read the rest of this entry »

I noticed when i did some maintenance and rebooted the ESX hosts and i could not get High Availability (HA) back up and running.  I kept receiving the error:

An error occurred during configuration of the HA agent on the Host
Enable firewall failed: vim.fault.HostConfigFault

Strange.  Looks like neither ESX hosts are talking to each other.  VMWare communities suggest i run:

[root@syr-nav-esx-03 root]# esxcfg-firewall -q aamclient

And it gave me:

Can’t locate XML/DOM.pm in @INC (@INC contains: /usr/lib/vmware/esx-perl/perl5/site_perl/5.8.0 /opt/ActivePerl-5.8/site/lib /opt/ActivePerl-5.8/lib .) at /usr/sbin/esxcfg-firewall line 21.
BEGIN failed–compilation aborted at /usr/sbin/esxcfg-firewall line 21.


Turns out the problem is from the changes Asigra Televaulting DS-Client wanted me to make to each ESX host in order to get host based backups working.  The DS-Client requires Perl to be upgraded to at least 5.8.1. And in order to make sure ESX continues to function after the Perl upgrade they states on page 419 of dsuser.pdf:

After the Perl upgrade, the vmware-cmd command may no longer work since it is not compatible
with the new Perl. You will, however, need this command in order to register restored virtual
machines. To fix this problem, go to the /usr/bin/ directory and edit the vmware-cmd file as well as
the vmware*.pl files in this directory; change the first line in each file to refer to the old Perl
installation (replace #!/usr/bin/perl with #!/usr/bin/perl.old). Run vmware-cmd without
parameters to verify that it works.

So i guess they forget to mention /usr/bin/esxcfg-firewall also needs it’s perl path changed to /usr/sbin/perl.old.  This makes me wonder what else migth brake from the Perl upgrade.