[Dirvish] Dirvish speed and security

[Shawn (Red Mop)]

List of questions:

What kind of link are you backing up over?
Are you backing up over nfs, or rsync/ssh?
Are you using ssh (-C) or rsync (-z) compression?
Do you have the --whole-file or --checksum settings selected?
How much I/O are the drives containing the file systems in question under 
during the backup period when the backup is not running compared to how fast 
they can go?
What file systems are you using on the backup server and client?
What settings (size, journal type, mount options, block sizes, inodes, etc) 
are those file systems?
How badly fragmented are those file systems?

On Monday 26 May 2008 12:47:15 pm Leopold Palomo Avellaneda wrote:
> A Dilluns 26 Maig 2008, Keith Lofstrom va escriure:
> > On Mon, May 26, 2008 at 03:31:01PM +0200, Leopold Palomo-Avellaneda wrote:
> > > I'm using dirvish 1.2.1-1, from a debian etch. I have created my vaults
> > > and configured and running the complete system. I have a nfs mount
> > > where I put the backup. It simply works.
> > >
> > > Howeber, I have a very poor transfer rate. To create the init backup I
> > > need two days to transfer about 90G, and some days, if we have a lot of
> > > modifications, the dirvish have not finished their work, so, when we
> > > work again the backup is not finished occasioning:
> >
> > If your data rate is low, you may want to make more, smaller images. 
> > That way you can do the initialization in multiple steps.  You should
> > also arrange your data to minimize the backup effort - dateext for
> > logrotate, maildir instead of mbox mail storage, etc.  Lastly, if your
> > transfer rate is very low, consider running backups less often than once
> > a day.  If you are using smaller images, then you can run them in two
> > sets on alternate days, perhaps using two different master files selected
> > by scripts from cron.
>
> Ok,
>
> but why it's so slow? I would like to backup home and I don't want to make
> different sets. And I would like to backup once a day. There's no another
> way to do it?
>
> > > About security, the permissions to the log file are r-r-r, so everybody
> > > could read it. There's some way that I could change this mask in
> > > dirvish?
> >
> > Is this to prevent users from seeing other user's changes?
>
> yes and see the name of the files?
>
> > I keep my banks in a subdirectory accessable to root only, and unmount
> > the partition they are in when I am not doing backups.  I don't want to
> > make the dirvish banks accessable to general users - if something needs
> > to be restored, it is best if a sysadmin does it.
>
> Ok, I see. I should do it.
>
> > If you want to keep the user files accessable, but not the logs, perhaps
> > you can set up a wrapper shell script that chmods the bank to 700 during
> > backup, chmods the log files to 400 after backup, then chmods the bank
> > back to 755 at the end.
>
> Not necessary, umount that's all.
>
> Thanks,
>
> Leo