Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Backup issues

On Mon, Nov 10, 2003 at 10:50:47AM -0500, Jerry Feldman wrote:
> Hash: SHA1
> On Mon, 10 Nov 2003 10:04:03 -0500
> nmeyers at wrote:
> > I'd guess Samba isn't closing files quickly enough after you touch
> > them - no idea why.
> > 
> > Rsync is a great backup solution, but I think a move to a different
> > protocol would be a help. You could run an rsync server on the Linux
> > box and use the native rsync protocol, or tunnel rsync through rsh or
> > ssh - either one would take Samba out of the loop. Here's how it might
> > look in ssh (assuming something like a cygwin bash shell):
> > 
> >   RSYNC_RSH=ssh rsync [...all your usual options...]
> >   /windoz/wifecdrive wifeuserid at mylinuxhost:/path/to/backup/directory
> > 
> > You can set up cert-based ssh authentication for that account that'll
> > let this work without having to type a password, if that's desirable.
> I was thinking of doing this since I have cygwin on my wife's machine. 

Funny... I didn't even realize from the question that you were driving
this from the Linux side. So /windoz/wifecdrive is an smbmount-ed
filesystem and /backup (if I recall the name of your destination)
is local.

Yes, I think pushing from the Windows side and avoiding Samba should get
you past this problem. I doubt there's anything fundamentally broken with
Samba... you're just touching a lot of files quickly and it's apparently
(possibly for protocol reasons) not freeing file resources quickly enough.


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /