This post is more than 5 years old
51 Posts
0
4324
August 1st, 2011 15:00
Rename File System on Celerra and implications of existing CIFS Shares
Greetings again all......
I know that you can rename a file system from the GUI or from the CLI. I believe all that needs to be done is to remount the File System under the new name once it has been renamed.
What I am unsure of is how the existing CIFS Shares will react. Will their paths change with the renaming of the file system or will they have to be deleted and recreated with the new File System name?
In the interim I will try to get my new laptop running with my Sim environment so I can test this physically. I ask here first as I am time contrained.
Thanks in advance.
Jerry
No Events found!
Rainer_EMC
4 Operator
•
8.6K Posts
0
August 9th, 2011 14:00
Hi Jerry,
I think the confusion comes from renaming a file system vs. changing its mountpoint.
These are two different things - the name is only used internally and its just the default mountpoint when a file system is created.
Later you can change the name but it wouldnt change the mountpoint.
If you change the mountpoint then you need to change or re-create the shares as well since their path is relative to the DM/VDM and includes the mountpoint.
So yes you can simply unmount the file system, create a new mountpoint and mount it there without loosing data or ACLs.
The CIFS or NFS exports (and potential CIFS share ACLs) you have to change or re-create.
Obviously during the time window when its unmounted the file system would be unaccessible for the clients.
hope that clarifies it
Rainer
jerry.reddick
51 Posts
0
August 1st, 2011 15:00
Thanks Dynamox...
I forgot to add that the existing CIFS are not on a VDM due to some of the shares being NFS exports as well. So as long as I remount them on the same DM all will be well is what you are saying?
Jerry
dynamox
9 Legend
•
20.4K Posts
0
August 1st, 2011 15:00
remount under the same mount and nothing will be affected
dynamox
9 Legend
•
20.4K Posts
0
August 1st, 2011 18:00
same mount point that's what's important.
jerry.reddick
51 Posts
0
August 9th, 2011 07:00
Dynamox, thanks again for your comments. I was not clear on my first go around. Let me set up the scenario.
Customer had File Systems with Shares. We had to migrate the file systems and recreate the shares. We used replicator within the same array to different storage.
Create Replication:
FS1 - Original File System >>> FS1_replica1
Perform a Switchover. Delete Origianl FS (Storage was in an unsupported ThinPool configured via the BE and presented to Celerra Storage Group) and recreate the shares so users can access while we reprovision original storage. Shares have a file system path of \FS1_replica1\Share1
After Reprovisioning of Original Storage with CSA is complete New Replication is created.
FS1_replica1 >>>> FS1_replica1_replica1
Perform a Switchover. Delete FS1_replica1, recreate the shares, etc. Shares have a file system path now of \FS1_replica1_replica1\Share1.
You can go into the GUI or the CLI and Rename the FS to whatever you want. This appears to be simply a symbolic name. However the underlying path still remains \FS1_replica1_replica1. (See Image if I was going to create a new share)
I guess the question I should have asked originally was, Can the underlying FS Path be renamed without losing customer data, and the shares recreated with the renamed path? Apparently the customer is having issues with some backups as the path is too long in some cases.
Thanks!
Jerry
jerry.reddick
51 Posts
0
August 9th, 2011 19:00
Thanks Rainer,
I realized I was confusing the terms and thanks for the reassuring clarification. I have my test environment set up and will test the process there first! I appreciate yours and Dynamox's time and effort in answering my questions!
Jerry