We will be transitioning the Orca academic file server to Windows 2012. There are a handful of reasons for doing this, including the fact that Orca is currently a 32bit Windows 2008 server and uses Windows dynamic disks for the programs share. Additionally, once the data is on Server 2012 we can take advantage of data deduplication which should reduce the total disk space consumed by at least 10-20%. This space savings is important as Orca is our largest file server.
The transition is intended to be as seamless and unnoticeable to end users as possible. The new server will assume the same name and IP address. Much of the data that needs to be copied from the dynamic disk will be copied over beforehand in order to reduce the necessary downtime. At this time I expect the final cutover to require the server to be unavailable for up to 2 hours. There was a prerequisite for this project of upgrading our ESXi infrastructure to version 5.5.
Project Manager: Josh Jordan
Team: Network Services
- Josh Jordan
- Network Services
- Academic Computing (to help schedule the cutover and provide notification to students)
- Client Services (to help schedule the cutover and provide notification to staff/faculty)
Start: Feb 2014 (with prerequisite work done in Jan)
Jan: Upgrade ESXi to version 5.5 in order to support large virtual disks
End of February: Build replacement server
March 10th-24th – The programs share will be copied (at a slow rate so as not to interfere with normal access) to the new server.
Mar 24th – Apr 11th – Verify that disk quotas, quota templates, the pfcc program, and the various clients supported at Evergreen can connect properly. Also, make sure that DUC can properly provision and delete home directories.
April-May –Schedule cutover with client services and academic computing. This will be dependent on when downtime is acceptable for the server.
Any updates will be added to the documentation here: \\hurricane\PCCommon\Computing and Communications\Orca_Server2012_Migration