We are currently using amanda 2.4.5p1 to backup a mix of Unix + Linux hosts. Now, we need to backup HUGE (100 Gb) subversion repositories that reside on a Windows XP box. From what I have read, the S
Author: Graeme Humphries <graeme.humphries AT vcom DOT com>
Date: Wed, 05 Jul 2006 13:59:47 -0600
What we tend to do is create a share (via Samba) on a Linux server, and do our backups from the Windows servers to there. This sidesteps a lot of these kinds of issue for us, but you may not have a L
Author: Joshua Baker-LePain <jlb17 AT duke DOT edu>
Date: Wed, 5 Jul 2006 16:08:10 -0400 (EDT)
We are currently using amanda 2.4.5p1 to backup a mix of Unix + Linux hosts. Now, we need to backup HUGE (100 Gb) subversion repositories that reside on a Windows XP box. From what I have read, the
2006/7/5, Joshua Baker-LePain <jlb17 AT duke DOT edu>: If it were me, I'd look at using subversion's various internal backup scripts (e.g. 'svnadmin dump', 'hotbackup') and putting the resulting imag
Obvious choice (probably not suitable, but no harm in suggesting it): Is there space available (or can be made available) on the tape server? If so, the second backup is local to the Amanda tape serv
Specific shares is probably a better use of amanda for windows backup than attempting to do total system backups. Five come to mind. 1. use some windows based software to actually do the backups into
Author: Graeme Humphries <graeme.humphries AT vcom DOT com>
Date: Wed, 05 Jul 2006 15:33:39 -0600
One thing you can do to reduce this is to use rsync to copy the data from the subversion server to the samba server. Chances are that lots of that subversion data *isn't* changing every day, and so t
Author: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Thu, 06 Jul 2006 02:12:04 +0200
And again from the samba server to the tape server. I wanted to avoid that. One thing you can do to reduce this is to use rsync to copy the data from the subversion server to the samba server. Chance