Previous Page | Next Page

Performing Pre-migration Tasks

Create the Migration Package

In addition to creating migration analysis reports, the SAS Migration Utility creates migration packages. These packages contain all of the SAS 9.1.3 content--data and configuration--residing on a machine. Later in the migration process, the SAS Deployment Wizard uses these migration packages to populate your SAS 9.2 deployment.

Note:   If you downloaded the SAS Migration Utility before receiving your SAS 9.2 order, you should now use the migration utility that is provided in your order. The version of the SAS Migration Utility that is included with your SAS 9.2 order is guaranteed to be compatible with the versions of the SAS products that you have ordered.  [cautionend]

If you have multiple machines in your SAS deployment, then you have to run the migration utility once on each machine. (Always run the migration utility on the metadata server first.)

To create a migration package, follow these steps:

CAUTION:
The migration utility pauses the metadata server when it creates a migration package, so any attempts to use your SAS 9.1.3 system during this period will be unsuccessful. Therefore, you should plan accordingly.   [cautionend]

  1. Review the migration utility requirements. (See SAS Migration Utility Requirements.)

  2. Make sure that you have backed up your SAS 9.1.3 Metadata Repository.

    For more information, see Back Up the SAS 9.1.3 System.

  3. If you haven't already, complete a migration utility checklist. (See Complete a Migration Utility Checklist.)

  4. Make sure that you have prepared your metadata repositories before you create a migration package on the metadata tier. (See Prepare Your Metadata Repositories.)

  5. Verify that the SAS 9.1.3 Metadata Server is running.

  6. Log on to the SAS 9.1.3 machine (the target machine) whose SAS content you want to migrate.

    Note:   On SAS multiple machine deployments, run the migration utility first on the machine hosting the SAS Metadata Server.  [cautionend]

  7. If the version of the migration utility that you are using has changed from one that you have used previously, then be sure to delete the migration utility's output directory. (For example, in the past, you might have downloaded and run an earlier version of the migration utility to create an analysis report. If so, delete the output created by the older migration utility.)

  8. Change to the SAS Migration Utility executable directory. By default, this is the utilities directory in your SAS Software Depot.

  9. Use the common migration utility properties file and the common connection profile you have developed, unless the target machine requires any special modifications.

    (For example, SAS is installed on a nonstandard path.)

    For more information, see Develop a Common SAS Migration Utility Properties File.

  10. Add any necessary product-specific migration utility properties to your properties file. (See Review Product-Specific SAS Migration Utility Properties.)

  11. If you have migration packages from any earlier migration utility invocations, delete or move these packages before rerunning the migration utility.

  12. If you have a multi-tier SAS 9.1.3 deployment, you will need to run the migration utility once on each machine. (Do not run the migration utility on machines that only contain SAS 9.1.3 clients.) There are specific options, depending on the tier (for example, -davtier). For more information, see SAS Migration Utility Reference.

    Note:   You cannot run the migration utility on more than one machine simultaneously, because the migration schema might be updated by more than one process at the same time.  [cautionend]

  13. Invoke the migration utility, using the following command from an operating system prompt or command line.

    Note:   On UNIX and z/OS, if you have not already, remember to assign file execute permissions to smu.sh before attempting to run the migration utility. For more information, refer to your UNIX or z/OS documentation.  [cautionend]

    Use the -replace option if the migration utility writes to the output directory used in earlier invocations. If you are migrating on the WebDAV machine, make sure that you specify -davtier on the command line or use the appropriate WebDAV properties:

    • Windows:

      smu -s -a -properties absolute pathname to property file -replace
    • UNIX:

      ./smu.sh -- -properties absolute pathname to property file -replace
    • z/OS:

      ./smu.zos -- -properties absolute pathname to property file -replace
    • For more information about migration utility commands, see SAS Migration Utility Reference.

      For more information about migration utility properties files, see Develop a Common SAS Migration Utility Properties File.

  14. Review the migration analysis report to ensure that the migration package was properly created. Point a Web browser to AnalysisReport.xml in the AnalysisReport subdirectory underneath the output directory you specified in the migration utility properties file.

  15. After you have created the migration package, make a backup of the package. Backups are especially recommended in multi-tier deployments. If the package creation fails for one tier, you can restore the package to the last successful version, without having to rerun the migration utility on every tier again.

  16. If you have a multi-tier SAS 9.1.3 deployment, you will need to create a migration package for each machine. (Do not run the migration utility on machines that contain only SAS 9.1.3 clients.) There are specific options, depending on the tier (for example, -davtier). For more information, see SAS Migration Utility Reference.

    Note:   You cannot run the migration utility on more than one machine simultaneously, because the migration schema might be updated by more than one process at the same time.  [cautionend]

Previous Page | Next Page | Top of Page