Background
We are in the process of migrating data from our existing two-node file server cluster (Causeway2), which provides the Users (U:/F:), Depts (O:/G:), Courses (P:/K:), Campusapps (M:), and the media storage volume used by a few departments to a new system. We have built a new Windows-based file server cluster to replace the Novell Linux cluster we've been using for the past few years.
One big change is that we will no longer be relying on the Novell client. In fact, we're going to switch campus computers to use the Microsoft networking protocols with the Novell servers, and then switch which servers are handling your files as we migrate the data. Our goal is to make this as seamless as possible,
Individual volumes, as the data is migrated and tested, will be switched out over several weekends in the near future.
There are going to be some changes. The highlights:
- Microsoft's file permissions system is very different than Novell's. The Novell tool we are using to move the data over preserves file trustee assignments as well as it can, but some of the behavior you see may be different, especially if you have given others access to subfolder in an otherwise private folder.
- The Microsoft servers do not support Apple's AFP protocol. Anyone using a Macintosh will have to connect with SMB.
- There are name (and IP address) changes.
Click here for a list of volumes, drive letters and network names.This will have an effect on how Macintosh users and Windows systems without the Novell client connect to the file servers.
Monitoring and tuning
This is a major change to our file server environment, on which many other services depend. While many of the changes to you will be cosmetic (drive letter / server name changes), the behind-the-scene changes are significant. The systems have been extraordinarily reliable over the summer, but we may need to go through another round when the system is under full load as the Spring semester begins.