C
Charles Onaje Lucas
I got a project to analysis, the goal of the project is to move from Windows 2008R2 w/SP1 failover Cluster (Old Cluster) to Windows 2016 Standard Failover Cluster (New Cluster). Both Cluster are connected to the same SAN by a Fiber Switch.
The old cluster with over 100 different shares that are used by over a 100+ workstations (workstations are not on domain) and an third application maps the shares presented by the cluster to the workstations. The goal is to move (migrate) the data to the new cluster without changing the shared pathways so we do not have change any of the workstations.
1. Looked at In-Place upgrade but this would take forever.
2. I through about Attaching the same shares to the new Cluster and putting the OLD clusters Shares into read only. I think this is best option!
3. The last option is just create new LUN, attach the to the New Cluster and RoboCopy the data and share permission to the LUNS but it would mean recreating all the share names and paths again which what I do want to do. What is the best course of action?
This that first time someone asked me to do this.
Continue reading...
The old cluster with over 100 different shares that are used by over a 100+ workstations (workstations are not on domain) and an third application maps the shares presented by the cluster to the workstations. The goal is to move (migrate) the data to the new cluster without changing the shared pathways so we do not have change any of the workstations.
1. Looked at In-Place upgrade but this would take forever.
2. I through about Attaching the same shares to the new Cluster and putting the OLD clusters Shares into read only. I think this is best option!
3. The last option is just create new LUN, attach the to the New Cluster and RoboCopy the data and share permission to the LUNS but it would mean recreating all the share names and paths again which what I do want to do. What is the best course of action?
This that first time someone asked me to do this.
Continue reading...