UNSOLVED

MichaelLJay

updated

11 years ago

0

710

June 8th, 2015 15:00

MS Cluster migration to VNX CIFS

So, we have 4 MS cluster nodes running 3 MS cluster services (srv01-03).  As I try and wrap my head around the whole EMC/VNX CIFS stuff I’m wondering if it matters how the data ends up once migrated off of the MS cluster to the CIFS.  Would like to make the whole EMC/CIFS thing as easy to manage as possible.

For example –

I could create 3 virtual CIFS servers (all riding on VMD01) and try and match the shares with what is existing  - meaning share1 on MS srv1 goes on share1 on CIFS srv 1, etc.

OR

I could create 1 virtual CIFS server and multiple giant file system (16 TB Limit is my understanding) that can hold all the MS cluster data

OR

I could create 1 virtual CIFS server and lots of smaller file systems to break up what is existing already on the MS cluster (drive S=8TB so create one FS of 8 TB, for example)

OR

I could get a new job!

We are using DFS Namespace – so if all I have to change is the underlying referrals or folder targets than I can live with that!

I have to also implement quota's and we've purchased NTP software but it will not be as good or as easy as was the MS Quota setup and because of how the NTP software works I'm leaning toward the 3rd option just to help with the quota stuff.  In other words lots of smaller file systems (dedicated to various groups) so that the over all quota (FS size) is kept small (knowing I can increase fs size when needed).

Help!

Thanks.

  • dynamox

    11 Legend

    20419 Posts

    87439 Points

    369

    0

    Posted June 8th, 2015 20:00

    what's the backup/recovery plan ?

  • cadencep45

    4 Apprentice

    318 Posts

    369

    0

    Posted June 8th, 2015 23:00

    backup/recover is important. If you coalesce fs to a single large fs, then there are at least 3 things;

    1. You are saying you will never need more than 15 TB as this is the fs largest size limit. If you look at your data growth historically, can you say this ?

    2. NDMP, depending on your hardware, you can have 4 or 8 concurrent NDMP sessions. NDMP sessions cannot be stopped and restarted in EMC, so think  long and hard will you get good backups with a single large FS.

    3. Your saying ( unless your using FAST ), that all your data access speed requirements are the same. Are they ?

    Finally in terms of performance, do a Proof Of Concept before committing to migrating all data that your CIFS server performance in EMC land is acceptable as MS cluster environment, as all CIFS server implementations are not created equal.

  • 369

    0

    Posted June 9th, 2015 14:00

    Thanks.  Backup software (handled by another team) is Symantec NetBackup.  After we did the initial setup and the backup guys did their thing (I'm trying to find out details now about what their thing was) they just told us that they would have to restore to CIFS.  Nothing else has been discussed regarding backup/recover and/or performance. (Attempting to get more info from them on the subject of backups/restore).

    Regarding going over 16 TB in size for a  single file system - if there are ways around this that could be needed in the future but for sure is not needed now or anytime very soon because of how are storage has been broken up between the various groups we support.

    Yes, I would say all the data requirements are the same - bulk of data is file server data (user data, group data, PST's, etc.) and smaller subset is Citrix User Profile Data.  No applications, no SQL, etc.

    Thanks again for your feedback...it is much appreciated.  For sure we'll start off slow and I just hope to get started off on the right step.  My thinking is to just do smaller file systems that line up with our current setup.  For sure more info is needed from our backup unit so will work closer with them.

  • dynamox

    11 Legend

    20419 Posts

    87439 Points

    369

    0

    Posted June 9th, 2015 17:00

    also consider using SnapSure to "supplement" your traditional backups, great for self-restores but of course does not replace off-array backups.