and, if I only do /DAT (date attribute time) it copies fine, so there's no issue with actual write permissions.
Also, if I remove all of the content that vol copy created, and run a robocopy with /COPYALL... it also copies fine, with NTFS ACL's. So something with the way the netapp vol copy is different than when I just use robocopy to replicate the data.
Has anyone ever experienced this? The issue with just using robocopy to do everything is it introduces a middle man, taking the time to do the initial copy and increasing it severely.
Any ideas as to what might be happening? I thought the vol copy wouldn't have any affect on permissions/ownership as it was just copying blocks (regardless of what is actually in them).
Anyone have any thoughts? I've been gone for a couple weeks. It seems very strange to me that using robocopy works if there is no data in the target, and using vol copy is causing some sort of permission issues.
just closing this off. I blame the looming days before my vacation on my foggy actions...
It ended up being permissions issues. I found that I needed to add some accounts to the administrators group on the filer to allow for the proper copying of ntfs acl's. *sigh* stupid permissions. But, on a good note, luckily it wasn't a vol copy bug