A migration is a series of one or more migration tasks that are performed on an Otto server. The tasks almost always involve one or more Otto servers. The server performing the migration is referred to as the "destination" or “local” server. Often, this server is your production server. The local server retrieves files from the “source” or "Remote" server, which can be a FileMaker Server or web server. Migration tasks are described using an HTTP request with a JSON payload, which is posted to the Otto server performing the migration. The Otto server responds with a Migration ID that you can use to track the progress of the migration.
Here are the steps in a typical migration:
- Files being migrated are closed and backed up on the local Otto server
- File copies are fetched from remote Otto servers (either clones or copies are fetched depending on what was specified)
- Migration tasks are performed (if specified)
- Files are reopened on the local server