I need to exclude a folder from sync . I am using the following parameter however this does not seems to be working
Idea is anything under folder c should be excluded. is this the correct format?
... View more
Hi @ all, we are currently migrating our DCs from w2k8 to Windows Server 2019. We have installed 2 new servers and the corresponding roles and upgraded them to DCs. They should take over the IP addresses of the two existing w2k8 DCs or this is already the case with one of them. Now the Netapp (Version 8.2.4P5 7-Mode) shows every now and then (or with cifs testdc) for the DC that has taken over the IP the message: [Filer:cifs.smb2.client.signing:error]: Connection to server:\\DC02 failed due to mismatch in signature. I have searched a lot but have not found a solution yet. Cifs signing is disabled: options cifs.smb cifs.smb2.client.enable on cifs.smb2.enable on cifs.smb2.signing.max_threads 3 cifs.smb2.signing.multiprocessing default cifs.smb2.signing.required off cifs.smb2_1.branch_cache.enable off cifs.smb2_1.branch_cache.hash_time_out 3600 (value might be overwritten in takeover) cifs.smbx_signing_required off Is this a serious problem? Does anyone have an idea or solution? Best regards André
... View more
Hi All - I've read a large number of the threads out here in detail. We are running 9.4P3 on our system and are hosting several MASSIVE shares with multiple millions of files and folders. We moved the data off a NetApp to a Windows box back in 2014 and then back to a new NetApp in 2018. I do not see any attributes on the files saying they are indexed or other obvious issues. What we are seeing is that files are not searchable. I'm not talking about not indexed (I don't believe that is supported still) as in they don't show up EVER in the search results, and the results instantly return what *appear* to be indexed results from before this content was moved to the NetApp in '18. Has anyone else run into this? Does anyone have a way to fix this? I've tried disabling Windows Search service on test machines and several other things, but nothing I've tried seems to be fixing this issue. We have to be able to search these shares, and we have users complaining for good reason. I did see the third party plugin that is for sale that allows indexing on the NetApp but we aren't going to spend $250K+ on a plugin to index the contents.
... View more
Hi, IHAC that has a CIFS volume (NTFS security style) and would like to make this volume available to Red Hat 7 and 8 clients. Linux clients currently authenticate against Active Directory. The export policy has been configured to let all hosts mount. CIFS share and volume permissions - Everyone/Full Control The RH client has mounted the export and export-policy check-access passed: cluster::*> export-policy check-access -vserver datasvm -volume cifs_testing -client-ip 10.11.109.18 -authentication-method krb5 -protocol nfs3 -access-type read-write Policy Policy Rule Path Policy Owner Owner Type Index Access ----------------------------- ---------- --------- ---------- ------ ---------- / default datasvm_root volume 1 read /cifs_testing cifs_test cifs_testing volume 1 read-write cluster::*> export-policy check-access -vserver datasvm -volume cifs_testing -client-ip 10.11.109.18 -authentication-method sys -protocol nfs3 -access-type read-write Policy Policy Rule Path Policy Owner Owner Type Index Access ----------------------------- ---------- --------- ---------- ------ ---------- / default datasvm_root volume 1 read /cifs_testing cifs_test cifs_testing volume 1 read-write Name mapping seems to be OK by shortname: cluster::*> secd name-mapping show -node cluster-03 -vserver svmcifsnfs -direction unix-win -name fflinstone 'fflinstone' maps to 'DOMAIN01A\fflinstone' But seems to be a bit off when specifying Domain\account: cluster::*> secd name-mapping show -node cluster-03 -vserver svmcifsnfs -direction unix-win -name DOMAIN01A\fflinstone 'DOMAIN01A\fflinstone' maps to 'DOMAIN01A\fflinstone' How should I be thinking about this? I'm not clear on how this architecture should be. How should RedHat clients access NTFS volumes via nfs when the usernames are managed by AD? Since RH clients auth against AD, I don't see how username mapping should come into play, but if the name maps back to itself, shouldn't that work?
... View more