Contents

Pausing, Resuming and Canceling Migration

In UCS 9.1 you can:

Pause a migration job gracefully, which preserves its context, and resumes it later from the point of the interruption. This enables you to respond to external circumstances, like network issues, production constraints, and so on.

Cancel a migration job completely, which deletes its context. No resumption is possible.

Pausing and resuming

There are two steps:

Pausing the migration job—this uses a pause command and the job ID of a running migration job.

Resuming the migration job—this uses a submit command and a RESUME_ID parameter.

UCS 8.5 database host name or IP address. Set to localhost by default.

-p UCS8_PORT

Yes

UCS 8.5 database TCP port.

-p UCS8_USER

Yes

UCS 8.5 database user name.

-p UCS8_PWD

No

UCS 8.5 database password.

-p UCS9_HOST

Yes

hostucs9

-p UCS9_PORT

Yes

7050

-p START_DATE_FROM

No

The start of the date range for exporting items. Format is yyyy-MM-dd HH:mm:ss.SSS and must be surrounded with quotation marks. This start date is included in the selection. Example to migrate only objects created in 2017:

The end of the date range for exporting items. Format is yyyy-MM-dd HH:mm:ss.SSS and must be surrounded with quotation marks. This end date is excluded from the selection. Example to migrate only objects created in 2017:

Specify a paused job ID to resume its processing where it left off. If the specified ID does not exist in GDPS, an error is returned.

-p DURATION

No

Specify a time window in minutes for running a resumed migration. When the time elapses, migration stops gracefully and may be resumed later by using RESUME_ID parameter. The value must be greater than 0.

Multiple Resumptions

When a migration job is started, an initial job ID is generated. When a job is paused and resumed the first time, you use the job ID to both pause and resume the job.

But when a job is paused and resumed a second time, a second job ID is generated for the resumed job. To stop the job a second time, you use the second job ID. But to resume it a second (or subsequent) time, you must re-use the initial job ID.

Canceling a migration job

Any migration job already submitted can be canceled by using the following ucs-job script syntax: