+1 This is exactly right. This is also one of the reasons I discontinued use of our Buffalo Terastation entirely. Backups with robocopy would copy the entire directory structure over again when using /mir, file attributes would change between shares as you've experienced, and you can't set file based security on the device (the one I have, don't know about yours), everything had to be at the share level.
On Tue, Jan 19, 2010 at 9:42 AM, Steven M. Caesare <[email protected]>wrote: > Chances are it’s using something samba-ish on the NAS for the CIFS > connectivity, and a filesystem that may not be FAT on the discs. > > > > I’m not sure that they support file attributes, as opposed to file > permissions. > > > > Can you re-mark it as RO once it’s on the device? > > > > -sc > > > > *From:* David Lum [mailto:[email protected]] > *Sent:* Tuesday, January 19, 2010 9:37 AM > *To:* NT System Admin Issues > *Subject:* Buffalo NAS - weird read only issue > > > > I have a client with a Buffalo NAS and if they have a file marked read > only on an PC and they move it to the NAS the read-only attribute is > stripped. Same thing for moving from folder to folder on the NAS. Has anyone > else seen this before? Any idea if there’s a way to fix it? It has to be due > to how the folder is shared or how the file system in Unix-y, but I can’t > find any kind of setting that mighty change the behavior. > > *David Lum** **// *SYSTEMS ENGINEER > NORTHWEST EVALUATION ASSOCIATION > (Desk) 971.222.1025 *// *(Cell) 503.267.9764 > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
