We're having a filesystem being used by NFS and CIFS clients.
We would like to archive some old stuff from this filesystem using the FMA but looks like it can only do either CIFS or NFS. So it can't copy the NFS credentials if using CIFS, which makes the offline files inaccessible for the NFS clients.
So is the FileMover API a one protocol only per filesystem solution.
FileMover can perfectly fine archive multi-protocol files - the stubs remain all the CIFS and NFS attributes
what protocol is used to write to archive is a different matter
You should *only* have to re-stub if you deleted your stub file - then yes you would loose the CIFS attributes if it was archived with NFS
That should be a very rare occurance - before re-stub'ing you should try to recover the stub or file from a checkpoint or a backup if the CIFS attribs are important to you
Yes, so if we're using CIFS to archive files, we will loose the NFS credentials on the archived file on the destination.
The stub still has the NFS and CIFS credentials so only when we need to restub a lost stub we will loose the NFS credentials.
But when we have a VBB NDMP backup, using EMC_OFFLINE=N, of our production FS which holds the stub, we should be able to restore the stub so we're having also our NFS credentials back.
jjgrinwis
48 Posts
271
0
Posted January 6th, 2011 06:00
used online chat and according to EMC support this is not supported.
The Celerra to DataDomain FMA doc is telling me this:
If using NFS, only NFS metadata is being written to archived file. So it can only recover NFS metadata if your're re-stubbing an archived file.
So I guess stub file has still CIFS ACL when archived via NFS but when you try to re-stub, your stub, CIFS permissions will be gone.
Regards,
John