Why does Backup (Mirror) fail on Read-Only files?

[wpfreeman]

SOURCE is a WIndows 2000 Server in an AD domain.
NTFS drives with no speccial security set (just defaults)
VV job runs under administrator account

TARGET is a LaCie 500 GB NAS
NTFS drive
Profiles direct the backup to a UNC path
The SHARE on target has read/write rights for Everyone

The job seems to run fine, except for individual files that have the Read-Only attribute set - those will not copy from SOURCE to TARGET and generate this error in the VV log ...
[Can not change attributes of "< TARGET PATH \ TARGET FILENAME >". Access is denied.] [ERROR].

As soon as I cahnge the source file's R/O attribute off, the job will not cause an error on that file - it works fine.

For this job I need the R/O atrribute to remian set ... Is there a way to make this work in V

[TGRMN Software]

Hi , which ViceVersa version and build are you using? thanks!
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[Guest]

newest download of VV Pro2-Build 2014

[TGRMN Software]

Could this be related to the SAMBA / Linux issue where it is not possible to change read-only file's timestamps , differently from Windows ? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[Guest]

Hmm, it sounds like it could be related, but that characteristic is not something with which I am familiar.

Are you saying that the Linux OS on a LaCcie NAS will not allow a Read-Only file to be copied onto the Linux share even though the account being used has Read and Write permissions to that Linux share?

Can you offer a explanation of how this impacts the various types of VV jobs, and how this can be worked around for each type?

[TGRMN Software]

Please write to support@tgrmn.com, I would like to send you a special version of ViceVersa to further debug this, thanks!
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[billeuze]

I too am having this problem. Using latest version of viseversa (2015)
Source: Win2k server
Target: open-e NAS server (Samba)

Similar to above poster, I get same error message when trying to backup read only file. and when I remove Read Only attribute, backup works.

There is another way I can make it work: If I set the option: "Copy direct to destination (do not use a temporary file)", It copies just fine. Are there any possible negative impacts to using this option?

[TGRMN Software]

Hello

this is an issue with the way certain versions of Linux treat read-only files. Linux does not allow to rename read-only files and hence the failure in renaming the temp files by ViceVersa PRO ... temp files are useful for the synchronization method, you can copy 'direct to destination (do not use a temporary file)" with backup, no problem.

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[dmcintosh]

Would it be possible to offer an option to temporarily change the file permissions before attempting to move it? Archiving also fails for readonly files unless I turn off the "move" option but that is less than ideal because I'm backing up to a remote server.

[rokahn]

I've changed option to "write directly rather than to temp file" but still get access errors moving read only files during archive process. As with user dmcintosh, they're on a remote server so move is much more efficient. Any suggestions?

[rokahn]

In order to avoid all these problems, is it possible to set read-only attribute to default when mirroring?

[TGRMN Software]

Hello

did you try the latest version of ViceVersa ? This issue should be solved now.

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[Matz]