Running Asigra Televaulting on CentOS 4

I’m setting up a VM on my VMware server to manage network backups. Asigra Televaulting is an agentless backup client that stores the data on offsite disk rather than on tape or local disk. Your backups are pretty useless if they burn up in the same fire that destroys your PC. The idea is for the VM to be in suspend until needed, thus not impacting performance of the other VMs. A command in the crontab will resume the VM in time to hit the schedule. I’ll then use Asigra’s pre/post job scripting functionality to suspend the VM when the backup is finished.

Asigra supports Fedora Core, Red Hat ES and SUSE ES. I don’t like Fedora for a number of reasons, and this is for home use so I’m not paying for RH or SUSE, so I’ll use CentOS, the free clone of RHES. I’ve allocated a 4GB disk file for the VM. The OS itself should fit under 1GB, but the Postgresql database can hit 2GB, so I need the space. I’ve allocated 256MB RAM to the VM, but backups will run a lot faster with more.

At the OS “Installation Type” screen, you select “custom” to keep the disk footprint as small as possible. Disable the firewall and SELinux. On the Package Group Selection screen, tick the box for minimal install and complete the installation.

The application requires Postgres, so firstly you install it with:
yum install postgresql-server postgresql-jdbc

You need to run it once to build the database and create the config files
/etc/init.d/postgresql start
does the trick.
To make postgresql launch at boot, I use “chkconfig –add postgresql“, “chkconfig –level 345 postgresql on” and to confirm “chkconfig –list postgresql“. Postgres needs some minor tweeks for Asigra. you must add the line “tcpip_socket = true” to postgresql.conf and “host all all 127.0.0.0 255.255.255.255 trust” to pg_hba.conf. You then need to restart postgres to load the new config by running “/etc/init.d/postgresql restart“.

The client has some other dependencies that get resolved by installing “yum install compat-libstdc*” The client installer must be run with the “-console” switch unless you’ve installed X. Agree to the EULA and accept the default install path of “/usr/local/DS-Client”. We’re only going to install the DS-Client on this box, with the Java DS-User UI to be installed elsewhere. We’ll select a normal installation. The self contained install is an evaluation mode where everything is stored locally. We enter “localhost” for the DB host, and “postgres” as the username. We can put in anything for the password. We also want the service to start at boot time. It is normal for the client to give a warning about a missing database during an initial install. At this stage you get prompted for username, client ID and server location. These would be provided to you by your service provider.

The next thing is the encryption level. Asigra supports everything from DES (very weak, avoid) right up to military grade AES256. AES is slow, and the higher the key length, the slower the progress. I usually go for AES128. It’s significantly faster than 256, and it will take millions of years to break, rather than trillions, so it’s still good enough. Asigra uses two encryption keys; a key specific to the PC and an account key shared amongst all backup clients on the WAN. This enables common files to be encrypted and stored once, with this common key, rather than multiple copies being stored with individual keys (inefficient), or all sites sharing a single key (insecure).