Hi we should migrate a NetApp with CIFS form new domain to a new domain. All the sid's and account info will be migrated using Quest tools and I can do the cifs terminate and cifs setup. My question is what happens to the CIFS share permissions? Will be permissions be retained or should I do anything else?
I am assuming that your filer is now joined to one Domain.If you now want to join it to another domain,here are the steps
1) Make sure the AD server of the new domain is reachable from this filer
2)Run CIFS setup
3)Fill in the questionnaire that CIFS setup gives you - making appropriate entries for the new Domain.It should also create a new object for this filer in this Domain Database
4) Delete all the existing CIFS shares (This is to ensure that all the residual CIFS sessions get terminated and its gets flushed from the cache as well
5)Recreate all the shares once again
6)Since all the user accounts are being migrated (at the AD level),when the filer connects to the Domain to lookup for the objects and SID.these should be available(Honestly we have not done this step till now but basic windows AD knowledge and common sense tell me this)
The above steps should work fine.
Also there is no case of data migration here from your question so the AD is the most important part of the migration.
All this becomes much much simpler if there is a trust relationship between both the domains.
I would suggest to run a POC first for few test users and then plan the migration phase-by-phase.
Hi thanks for the reply. I have couple of questions
1) should I first do the AD migration and then do the CIFS setup on Netapp or first do Cifs set up on Netapp and then do AD migration or it doesn't matter
2) How can I do a test or a POC. I don't have a test NetApp. I have only one NeApp and it's on production. I cannot have downtime to do the CIFS setup. The only time I can have downtime is during the realigns toon from one domain to another
Yes we do have trust between both domains
Also if I follow your below procedure the share permissions will be intact right?
You should definitely make sure that the AD migration happens first.All the objects,user ID,permissions etc should be replicated and available in the new AD controller database.
Since you dont have a test netapp your only and best shot would on the production device itself.
One question - do you still want any dependency on your old Domain Controller (i.e domain) from which you are disconnecting or you are planning to decomission or removing it?
We had an activity in our team wherein the objects were changed within the same DC - so in our case a CIFS TESTDC /RESETDC worked fine.
Please note that CIFS RESETDC will disconnect the connection(read it as all CIFS shares losing connectivity for some time) and then try to establish it back (provided the DC is reachable)
In your case - best bet I feel would be CIFS setup only -Because during the downtime - when you will momentarily drop the connection to the old DC (say for shutting it down and rediecting to new DC) - when you run CIFS setup it will query you for domain controller for new details and it would be re-run again.
SO I would say this is disruptive .Make sure you have all the details handy and all AD objects are migrated fine - because typically only the authenticating body changes.The administrator account and password in the new domain to authenticate the user to add the filer to the domain should be handy before running "CIFS Terminate" and "CIFS SETUP"
Also all the additional checks mentioned by other contributor "CCOLEMAN_ " are also relevant and helpful.
Note - there is no need for recreating the CIFS shares which I mentioned before.