A Dimecres 28 Maig 2008, Shawn (Red Mop) va escriure:
> On Wednesday 28 May 2008 12:58:07 pm Leopold Palomo Avellaneda wrote:
> > A Dimecres 28 Maig 2008, Shawn (Red Mop) va escriure:
> > > A pair of workaround options:   These options are similar in result,
> > > but differing in implementation.
> > >
> > > Option 1:  Maintain a mirror of the data on the server, say, rsync from
> > > /home to another local disk, then run dirvish on that data.  This is
> > > expensive on disk space, but easiest to setup.
> >
> > Ok, but then I have my backup in the same box.
>
> You take that mirrored data and use dirvish to back it up to the icy box.
> This way, it won't matter that the backup takes a long time to run because
> it's not backing up live data.

ummm interesting.

> > > Option 2:  Take an LVM snapshot /home, then back up from the snapshot.
> > >
> > > Neither fixes the speed problem, but both allow backing up of
> > > unchanging data.
> >
> > I don't understand very well this. Please, could you explain it and what
> > is for?
>
> http://tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html
>
> I've not actually set this up myself yet, it's on my wish list though.
>
> http://wiki.edseek.com/howto:dirvish
>
> What this does is creates a snapshot of what the partition looked like at
> midnight, but lets things still change on the live file system.  You then
> backup this snapshot.  Thus, it doesn't matter that something changes on
> the live file system during the (long) backup period.

ok.

> > > Some more things to try
> > > if the icy box isn't mounted by anything else, try mounting nfs with
> > > nolock. You can also no_subtree_check on the icy box.
> >
> > Ok, but if I could execute rsync in the icy box, it would be better?
>
> Of course.  These options are only for working around the fact that it
> currently does not have rsync.

well, I have a console and a develop environment, maybe the debian maintainer 
that read this list could help me. The icy box has an arm (like others) I 
could investigate, but i think that he said that as this kind of boxes has a 
few ram (128Mb) and a cpu:

ulises> cat /proc/cpuinfo
Processor       : FA526id(wb) rev 1 (v4l)
BogoMIPS        : 230.19
Features        : swp half
CPU implementer : 0ulises> cat /proc/cpuinfo
Processor       : FA526id(wb) rev 1 (v4l)
BogoMIPS        : 230.19
Features        : swp half
CPU implementer : 0x66
CPU architecture: 4x66
CPU architecture: 4


I don't know....

> > > This also suggests making your rsize/wsize smaller...
> > > http://osdir.com/ml/nfs/2003-03/msg00119.html
> >
> > uff, ok. The question is it worse while.
> >
> > Really, this thread have done a lot of material!!!!
> >
> > Thanks.
> >
> > Leo
> >
> > PS. the options in the mount and export doesn't do much more :-(
>
> Doing a file copy might not be effected much by those mount options.  Since
> you have a lot of data, but not much of it changes, dirvish makes A LOT of
> hard links on the nfs mount.  These options may help speed up the backup. 
> If you want to test it, make a file that's a meg or so in size, then time
> how long it takes to make 10,000 hard links to it over nfs

Ok, I will try. Otherwise, although I have seen the giga switch, tomorrow I 
will try to change to another. Maybe the Lynk? switch doesn't like the icy 
box.

Regards,

Leo

-- 
--
Linux User 152692
PGP: 0xF944807E
Catalonia

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish

Reply via email to