C
Charles Onaje Lucas
I have a project 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). These are clustered File Servers, both clusters 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 a domain) a third-party 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 Windows shares (UNC path) pathways so we do not have change any of the workstations. I thought about Looked at In-Place upgrade but this would take forever and I thought about attaching the same LUNs to the new Cluster and putting the OLD clusters Shares into read only. I think this is best option.
OLD Cluster (File Servers) ------| |----New Cluster (File Servers)
|-- Fiber Switch------|
|
Fiber SAN
Quick Question, I know this is not recommend and it is not supported.
The last time I did this years ago was single file server not Clustered Windows 2003 Server with iSCSI SAN and LUNs and the new file server was Windows 2008.
I just move the iSCSI LUNS, to the new file server disconnected the LUNS from old file server and shutdown the sharing old server.
On the new File Server and Merge an export lanmanServer registry keys (HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver) to the new server’s registry.
I noticed that the data above the Shares is located under "HKEY_LOCAL_MACHINE\Cluster\Resources."
1. Export the registry HKEY_LOCAL_MACHINE\Cluster\Resources
2. Attach the LUN to the New Cluster, Shutdown sharing on the old cluster.
3. Merge the exported registry keys to the new cluster (two each server).
4. Then start sharing on the new cluster.
This company is not using DNS Alias for UNC Paths at all as far as I can tell.
Charles Lucas
Continue reading...
The old cluster with over 100 different shares that are used by over a 100+ workstations (workstations are not on a domain) a third-party 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 Windows shares (UNC path) pathways so we do not have change any of the workstations. I thought about Looked at In-Place upgrade but this would take forever and I thought about attaching the same LUNs to the new Cluster and putting the OLD clusters Shares into read only. I think this is best option.
OLD Cluster (File Servers) ------| |----New Cluster (File Servers)
|-- Fiber Switch------|
|
Fiber SAN
Quick Question, I know this is not recommend and it is not supported.
The last time I did this years ago was single file server not Clustered Windows 2003 Server with iSCSI SAN and LUNs and the new file server was Windows 2008.
I just move the iSCSI LUNS, to the new file server disconnected the LUNS from old file server and shutdown the sharing old server.
On the new File Server and Merge an export lanmanServer registry keys (HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver) to the new server’s registry.
I noticed that the data above the Shares is located under "HKEY_LOCAL_MACHINE\Cluster\Resources."
1. Export the registry HKEY_LOCAL_MACHINE\Cluster\Resources
2. Attach the LUN to the New Cluster, Shutdown sharing on the old cluster.
3. Merge the exported registry keys to the new cluster (two each server).
4. Then start sharing on the new cluster.
This company is not using DNS Alias for UNC Paths at all as far as I can tell.
Charles Lucas
Continue reading...