The way to up the number of threads is to edit the /var/lib/nza/prod.cfg from a shell. First start up Putty and ssh to the nexenta IP, and log in with the root password. If you have not already set up expert mode

Now we need to get into a shell.

Now lets edit the file

Find the line that says

and change it to something higher (the nexenta docs recommend setting it no higher then 10

Now we need to restart the NMS service for things to take effect

This tends to knock me off the ssh session, and I have to go and reconfigure the network interface from a terminal.

This made the NICs show up in XenCenter.

This will connect to ssh running on port 1234 on the remote $host.

If you try changing $sshPath to include the switch, BackupPC tries to escape the arguments when using them, and that results in weird errors.

I recently set up BackupPC , and although it took a little bit of setting up and getting used to, I'm pretty happy with it. One thing that I didn't realize right away is that it doesn't do transfer compression, as the perl RSync library it uses doesn't support it.

The way to enable compression is to use ssh compression and to backup using method 'rsync'.

Here is the configuration option that I used to enable it.

-C enables compression and -o CompressionLevel=9 sets the compression level to 9 (same as gzip). According to the man page, the default level is 6, and you should probably leave it at 6, unless you've got CPU power to spare.

The man page also mentions that for backups on a fast network, ssh compression will probably slow things down instead of speeding them up.

Decided to set it up using svnserve with sasl, as 1.5 supports that. Following the SVN Book, I set up my svnserve.conf file as follows

I had set up the /etc/sasl/svn.conf file as follows

Unfortunately, I kept getting the "Could not obtain the list of SASL mechanisms" error in TortoiseSVN and other clients. Nobody seemed to be able to help, until I finally figured it out - the DIGEST-MD5 plugin wasn't installed for cyrus by default on CentOS 5.2. All I had to do was run the following command and everything started working.