OK. So let’s say we have a lets say we have a filesystem that is on a virtual fileserver 1 assigned to Tenant 1 and a different one on VIRTUAL fie Server 2 assigned to Tenant2. The two tenants as business functions get merged and for compliance reasons you need to reassign (change) the Tenant on Virtual Fileserver 2 to Tenant 1. Or simply remove the Tenant settings from the Virtual File server since there is no business case for them.
NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety.
Unity, and other NAS systems don't have tenants, they have CIFS/SMB or NFS Servers, which have filesystems which contain data. Those are made accessible to users using NFS exports or SMB shares, or in some cases both. The access to the data is controlled by filesystem permissions, either POSIX permission bits, NTFS ACLs or both in some cases.
Now:
In most M&A situations you're going to do a few things.
1. You're going to do a directory services migration, moving users from AQUIREDCOMPANY\jsmith to PARENTCORP\Joe.smith, or something along those lines.
2. You're going to consolidate datacenters and hardware where it makes sense.
3. You'll eventually end up likely merging File services together, which I assume is what you're asking about.
When you merge together 2 CIFS servers, let's say CIFS01.AQUIREDCOMPANY.NET into NAS05.PARENTCORP.NET you'll need to first check to see if there are any overlapping share names. Is there a share called Legal on the source, and another one called Legal on the target? If so, that'll be a problem for login scripts, manual drive mappings, etc. Unless you're able to say that they both now belong to the same team, so it's OK to collapse the 2 together. But then you have to be really careful, and use a tool to do the migration that's capable of doing so.
Goals:
The end goal of a consolidation is to simplify long-term administration of file services. But as you can hopefully start to pick up on above, it's a rough road to traverse, and it's not as easy as a technical Q&A, many of the questions are about your organizational structure, you're security standards, your authentication configuration, and a number of other variables.
But that's not to say that you can't run multiple NAS servers on the same unity box, you certainly can. You could even keep the network configuration the same if you can trunk in both VLANs to the target device, and make it all look pretty seamless. You're left with a mess long-term, but if we're just talking about a couple of NAS Servers / CIFS Servers, sometimes the consolidation isn't worth the hassle.
In Summary:
Hope this makes sense, and FWIW shameless plug, my company Datadobi, does make the best file migration software on the market, that is API Integrated with DellEMC Unity and other systems, can re-permission data like this during the migration, and consolidate top-level directory structures together, like the 2 legal shares example I mentioned above. Anyway reach out if you'd like to explore how it may be helpful in such a situation.
Sure but that's again talking about multiple NAS Servers in multiple networks (likely trunked in with 802.1Q), and trying to move data between them. (Not sure if they're even on the same physical box right now). The only nuance of the Unity multi-tenancy is isolated management as well, and that replication goes across the tenant's network. As you pointed out you can't move a filesystem between NAS Servers besides just copying the data off and back on.
It is a single Unity 400 service CIFS (SMB) Shares. A previous admin set up several business units as separate tenants with separate IP ranges. Each BU has their own Virtual File head in their respective Tenant IP range. I need to either combine these or remove the tenant. I am trying to avoid standing up a new file head and copying the data over since there are applications that address these shares.
NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety.
Have you reviewed the Dell EMC Unity: NAS Capabilities white paper that Rainer stated to review?If you haven’t then here is the link to that white paper. https://dell.to/3ve2DCg
simplest thing would be to remove all shares from the file system - that way clients cannot access it Or disable CIFS/NFS protocol for the NAS server
IF you are sure that the complete NAS server and all of its file systems should be inaccessible you could manually put the NAS server in destination mode (replDest=yes) through CLI
mhaysaz
3 Posts
0
September 10th, 2018 07:00
OK. So let’s say we have a lets say we have a filesystem that is on a virtual fileserver 1 assigned to Tenant 1 and a different one on VIRTUAL fie Server 2 assigned to Tenant2. The two tenants as business functions get merged and for compliance reasons you need to reassign (change) the Tenant on Virtual Fileserver 2 to Tenant 1. Or simply remove the Tenant settings from the Virtual File server since there is no business case for them.
NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety.
Rainer_EMC
4 Operator
•
8.6K Posts
0
September 10th, 2018 07:00
could you explain in more detail what you mean ?
crklosterman
450 Posts
0
September 11th, 2018 07:00
First, let's get some terms straight:
Unity, and other NAS systems don't have tenants, they have CIFS/SMB or NFS Servers, which have filesystems which contain data. Those are made accessible to users using NFS exports or SMB shares, or in some cases both. The access to the data is controlled by filesystem permissions, either POSIX permission bits, NTFS ACLs or both in some cases.
Now:
In most M&A situations you're going to do a few things.
1. You're going to do a directory services migration, moving users from AQUIREDCOMPANY\jsmith to PARENTCORP\Joe.smith, or something along those lines.
2. You're going to consolidate datacenters and hardware where it makes sense.
3. You'll eventually end up likely merging File services together, which I assume is what you're asking about.
When you merge together 2 CIFS servers, let's say CIFS01.AQUIREDCOMPANY.NET into NAS05.PARENTCORP.NET you'll need to first check to see if there are any overlapping share names. Is there a share called Legal on the source, and another one called Legal on the target? If so, that'll be a problem for login scripts, manual drive mappings, etc. Unless you're able to say that they both now belong to the same team, so it's OK to collapse the 2 together. But then you have to be really careful, and use a tool to do the migration that's capable of doing so.
Goals:
The end goal of a consolidation is to simplify long-term administration of file services. But as you can hopefully start to pick up on above, it's a rough road to traverse, and it's not as easy as a technical Q&A, many of the questions are about your organizational structure, you're security standards, your authentication configuration, and a number of other variables.
But that's not to say that you can't run multiple NAS servers on the same unity box, you certainly can. You could even keep the network configuration the same if you can trunk in both VLANs to the target device, and make it all look pretty seamless. You're left with a mess long-term, but if we're just talking about a couple of NAS Servers / CIFS Servers, sometimes the consolidation isn't worth the hassle.
In Summary:
Hope this makes sense, and FWIW shameless plug, my company Datadobi, does make the best file migration software on the market, that is API Integrated with DellEMC Unity and other systems, can re-permission data like this during the migration, and consolidate top-level directory structures together, like the 2 legal shares example I mentioned above. Anyway reach out if you'd like to explore how it may be helpful in such a situation.
~Chris Klosterman
Principal SE, Datadobi
chris.klosterman@datadobi.com
crklosterman
450 Posts
0
September 11th, 2018 08:00
Sure but that's again talking about multiple NAS Servers in multiple networks (likely trunked in with 802.1Q), and trying to move data between them. (Not sure if they're even on the same physical box right now). The only nuance of the Unity multi-tenancy is isolated management as well, and that replication goes across the tenant's network. As you pointed out you can't move a filesystem between NAS Servers besides just copying the data off and back on.
Rainer_EMC
4 Operator
•
8.6K Posts
0
September 11th, 2018 08:00
Chris,
actually Unity does have a concept if tenants IF you use the IP multi-tenancy feature - which is similar to what another vendor calls ipspaces
See the Unity NAS capabilities white paper for more details.
Not sure if mhaysaz really has this configured
If that is the case then AFAIR its not supported - for security reasons - to move it or remove the tenant association from the NAS server
Also - in Unity a file system cannot be "moved" to another NAS server
Rainer
mhaysaz
3 Posts
0
September 11th, 2018 12:00
So to clarify:
It is a single Unity 400 service CIFS (SMB) Shares. A previous admin set up several business units as separate tenants with separate IP ranges. Each BU has their own Virtual File head in their respective Tenant IP range. I need to either combine these or remove the tenant. I am trying to avoid standing up a new file head and copying the data over since there are applications that address these shares.
NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety.
Sumit.gupta.maersk.com
2 Posts
0
March 10th, 2021 07:00
Hi,
My Requirement is little different .
I have one file server , 2 File system which are configured as NFS share with the file server.
Currently None of them are in use.
Ultimately I want to remove all. But just to on safer side , we first want to unmap the file sever and file system and delete after 1 month.
So my Questions are :
* How we can unmap file system from file server? .
*Is there any impact on data of file system?
*As a backup plan, can we and how we can map this file system with file server with same data in case required?
Early reply will be more appriciated.
Regards,
sumit gupta
DELL-Sam L
Moderator
•
7.8K Posts
0
March 10th, 2021 10:00
Hello sumit gupta,
Have you reviewed the Dell EMC Unity: NAS Capabilities white paper that Rainer stated to review? If you haven’t then here is the link to that white paper. https://dell.to/3ve2DCg
Rainer_EMC
4 Operator
•
8.6K Posts
0
March 11th, 2021 07:00
we dont expose manual umount/mount on Unity
simplest thing would be to remove all shares from the file system - that way clients cannot access it
Or disable CIFS/NFS protocol for the NAS server
IF you are sure that the complete NAS server and all of its file systems should be inaccessible you could manually put the NAS server in destination mode (replDest=yes) through CLI