Performing and scheduling migrations with a script


You can use migration scripts to create customized migrations between one or more servers, at a scheduled time. For example, you can select which objects to migrate by moving those objects from server 1 to server 2, then move all or some of the same objects to server 3. You can then schedule this script file to run at any time in the future. 

How migration scripts handle multiple servers 
MigrationScriptsHandleMultipleServers.gif

Migrations within a script are executed in server pairs , not in the order in which they are created. For example, you might have a scripted migration from two source servers (Source Server 1 and Source Server 2) to three destination servers (Destination Server 1, 2, and 3).

When the script is executed, Migrator performs the following tasks:

  • First, it gets a list of all the source servers and then a list of all the destination servers.
  • Next, it loops through each source server.
  • Lastly, it loops through each destination server for a source server to determine if any objects need to be migrated between the two servers. If so, Migrator migrates all of those objects. If not, Migrator continues to the next server pair, until all the server pair combinations have been checked.

the following topics describe the scripting process and explain how to set up and run a migration script including how you can modify, schedule, change, and delete migration scripts:

Action

Reference

Learn how to create migration scripts faster and run those scripts with the help of a few best practices.

Learn how to use the Migration Script window to make modifications to the scripts such as edit object elements and servers.

Learn how to schedule a migration script to run at a specific time.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*