This question pertains to a migration from SAS version 9.4M4 to 9.4M6. We are planning a SAS migration to a different data center. We would like to build up the new server stack and then cut over gradually. Unfortunately we have a lot of metadata, and we're finding that when using the SAS Migration Tool (SMU), it only comes into play at install time on the target servers. So if we install in advance of the cutover, the metadata of the new environment gradually grows stale as users continue to live in the old environment prior to cutover. This suggests that we not build in advance: that we pick a weekend and migrate by shutting everything down in the source environment, running SMU there to collect everything, then build the target environment using SMU, and bringing everything back up on the target. We find that when trialing this process, it's challenging to fit in the space of a single weekend, given multiple servers involved and validation/testing steps to follow installation. I was wondering how other have worked around this problem, or if the only resolution is to extend the weekend work window for "migration weekend"? Insights appreciated.
... View more