...

source is a debian build, share is a readynas. i've been getting rsync: mkstemp 'filename goes here' failed: Not a directory (20) errors. rsync is v3.0. i believe this is related to the dovecot
file naming convention that includes characters such as ':' in the filename. anyone else seeing similar behavior? a workaround? i
can go to different backup strategies, but rsync is cheap and effective
for my needs. thanks,

The problem I encountered with cifs is that could not be compatible
with unix permissions and sometimes also fails setting directory date/time

When I backup on cifs either I use rsync and disable those features
or I tar-gzip each mailbox and copy it.

thanks for the feedback. i see the same problems w/ cifs. scripting
this is turning out to be slightly more subtle than i thought.
various combinations of rsync --delete, rsync --dry-run, tar, etc.
_may_ be viable. unfortunately it looks like cifs also barks at some
of the unix tar permissions, so i may turn the whole process around
and run it from the rsync server on the NAS, though that also has
issues.

-SM-

Ed W schrieb:

Scott Murman wrote:

...

i'm trying to backup the dovecot Maildir files over a cifs share.
source is a debian build, share is a readynas. i've been getting rsync: mkstemp 'filename goes here' failed: Not a directory (20) errors. rsync is v3.0. i believe this is related to the dovecot file naming convention that includes characters such as ':' in the filename. anyone else seeing similar behavior? a workaround? i can go to different backup strategies, but rsync is cheap and effective for my needs. thanks,

Is backup over ssh an option?

Alternatively could you run an rsync server at one end or the other (which then also avoids using cifs in the middle)?

Ed W

i ll do backups with rsync on maildirs with courier ( which has also : in filenames ) without any problems, as well i backup whole machines including sockets etc without any problems so the problem cant be dovecot here check your rsync version and script i would guess, maybe cifs has problems ..., use ssh ,ftp, nfs etc instead, or backup rsync in a local dir first then tar it followed by copy over cifs just one tar file

-- Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

thanks, as i noted i am using rsync v3, so the problem lies elsewhere
(maybe the ',' character?). i ended up starting an rsync daemon on
the remote server and using that. so far so good. i can't say too
many nice things about cifs, but it's a necessary evil here.

On Oct 9, 2009, at 7:06 AM, David Favor wrote:

Yes. Be sure to check your rsync version.

As I recall the 2.x series has bugs related to this.

I had a similar problem on MacOS until I upgraded to 3.0.6 and all is well with ':' on MacOS & Ubuntu at this level.

Robert Schetterer wrote:

...

...

Scott Murman wrote:

...

i'm trying to backup the dovecot Maildir files over a cifs
share. source is a debian build, share is a readynas. i've
been getting rsync: mkstemp 'filename goes here' failed: Not a directory (20) errors. rsync is v3.0. i believe this is related to the dovecot file naming convention that includes characters such as ':' in the filename. anyone else seeing similar behavior? a workaround? i can go to different backup strategies, but rsync is cheap and effective for my needs. thanks,

Is backup over ssh an option?

Alternatively could you run an rsync server at one end or the other (which then also avoids using cifs in the middle)?

Ed W i ll do backups with rsync on maildirs with courier ( which has also : in filenames ) without any problems, as well i backup whole machines including sockets etc without any problems so the problem cant be dovecot here check your rsync version and script i would guess, maybe cifs has

Ed W schrieb: problems ..., use ssh ,ftp, nfs etc instead, or backup rsync in a
local dir first then tar it followed by copy over cifs just one tar file

-- Love feeling your best ever, all day, every day? Click http://RadicalHealth.com for the easy way!

tomas@tuxteam.de schrieb:

On Fri, Oct 09, 2009 at 03:41:40PM +0200, Robert Schetterer wrote:

[...]

...

i ll do backups with rsync on maildirs with courier ( which has also : in filenames )

Stupid question: with CIFS as target filesystem?

no never, why should i do this, nfs , ssh etc should be faster and more secure etc

Because there are some chars which are AFAIK taboo on Windows file systems (colon being one, AFAIR -- luckily my memory on that is hazy :)

jo as i said cifs may not like some stuff, but i see no reason what force using cifs, after all you can rsync the maildir dir to another dir on the source server, tar it afterwards and copy it over cifs, as workaround this should work ever, and easy scriptable

Regards -- tomás

-- Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

tomas@tuxteam.de wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Tue, Oct 13, 2009 at 04:15:02PM +0200, Robert Schetterer wrote:

...

tomas@tuxteam.de schrieb:

...

On Fri, Oct 09, 2009 at 03:41:40PM +0200, Robert Schetterer wrote:

[...]

...

i ll do backups with rsync on maildirs with courier ( which has also : in filenames )

Stupid question: with CIFS as target filesystem?

no never, why should i do this, nfs , ssh etc should be faster and more secure etc

Nor would I, for that. But I can afford the luxury to see CIFS once a couple of years :)

My experience is that cifs is *faster* than nfs... Also, I personally find it simpler to administrate than NFS. Probably this is due to ignorance of how to setup NFS to do user based ID mappings, etc, but there you go...

(Much as it pains me to like an MS derived product, I have to stick up for it here... I think you will find a bunch of benchmarks in favour of either solution if you search the net, but the point being that at least some benchmarks also put cifs ahead of nfs in terms of performance...)

The end result is still in favour or rsync+ssh though... Do have a look at snapback2 for a fairly simple backup solution which works very nicely for me

Ed W