Skip to main content

Easy subversion backups

Anyone using a subversion server heavily needs good backups of their code. svnadmin dump is a good way to make regular backups. Or the mirroring method may work well for you.

I found a really useful, simple, elegant and clean tool to backup SVN repos with: svnbackup by Doug Hellmann (don't let the name fool you!). His script utilizes the existing tools but adds value, which is excellent in my book. He dumps the svn repo using svnadmin, splits the repo into commits sets (100 by default) and compress them in the process. The greatest feature, IMHO, is however the ability to let the scripts scp the backups to a different server! Genius! Works likes a charm in 30 seconds!

Here is my daily cron job:

#!/bin/bash
# http://code.google.com/p/svnautobackup/
# create dump of main SVN repo(s)
/usr/local/bin/svnbackup.sh --scp userid@server:/data/users/userid /var/svn/repositories/svnrepo/
echo "***SVN io_se dumped" >> /var/log/messages


If you have more than one repo, build in a for-loop to cycle all the repos. Brilliant! The wiki also has a restore command for your convenience.

Comments

Popular posts from this blog

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.

Removing VGs or LVs from LVM

While are many excellent tutorials about creating and using LVM on Linux, not may show you how you can remove disks from LVM Volume Groups (VG) and reclaim storage or how to remove a Logical Volume (LV) from your LVM set-up. Here is what I did: Use -t to TEST ANY LVM action first! We are going to release 1 TB from LVM. The Volume group was extended with 1 TB storage to serve as a cheap NFS/CIFS file server when setting up our data center. It is now deprecated and replaced by a NAS so it's no longer needed. 1) check LVM; note the four 256 GB LUNs [root@server ~]# pvscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Walking through all physical volumes PV /dev/sdb1 VG vgdata lvm2 [50.00 GB / 0 free] PV /dev/sdc1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdd1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sde1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdf1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdg ...

Dell Linux - OMSA Hardware Monitoring

Just getting started using Dell's OpenManage Server Administrator (OMSA) on our Oracle Linux platform. There are some confusing instructions going around so it's not immediately clear what to do, hence my blogging here. :) There is a site on Dell - Hardware Monitoring , as well as a wiki with instruction on how to setup their OMSA tooling using yum or up2date. [update]My first update for their instructions: be sure your server has Internet access, as most servers will use a proxy or so. use export http_proxy=http://yourproxy.example.com:port to configure it just for the session, and setup up2date to use an HTTP proxy by editing the settings in /etc/sysconfig/rhn/up2date .