Automation and tooling
Matching source and target topologies simplifies many variables that can affect migration efforts. In addition, matching topologies is a requirement for using the SAS Migration Utility. This tool assumes that every host machine, directory, and network component in the source environment will map one-to-one to its equivalent in the target environment.
You use the SAS Migration Utility to analyze and package your source environment. As the following diagram shows, the resulting package file is copied to the target system you have provisioned on AWS. It is then processed by the SAS Deployment Wizard as part of the initial SAS Enterprise BI Server software deployment on AWS.
The SAS Migration Utility is useful for migrating SAS metadata content and certain
associated files stored in the configuration directory. The bulk of the physical files (SAS data
sets, programs, external files, and so on) aren’t part of the SAS Migration Utility process and
have to be copied over to the target environment separately. To copy these physical files over,
we recommend that you explore the use of AWS
DataSync
After the majority of SAS content has been migrated to the new target system on AWS, you perform validation testing. Before you cut over to your production environment on AWS, you can perform one final promotion of any content that has been added or changed since the last migration.
For additional details on the SAS Migration Utility, see the SAS 9.4 Intelligence Platform Migration Guide
