Initialization Policy Using REST API
Learn how to set the initialization policy for migration jobs using the DryvIQ REST API.
Written by Andrea Harvey
Updated at May 2nd, 2025
Table of Contents
Overview
The Initialization Policy determines how the job will behave the first time it executes.
| Option | Behavior |
|---|---|
| "on_initialize": "none" | Nothing is done prior to the first job execution. (This is the default.) |
| "on_initialize": "purge_destination" | All files and folders in the destination path of the job are deleted prior to starting the file transfer. |
Job JSON Example
{
"name":"Initialization_test",
"kind": "transfer",
"transfer": {
"audit_level": "trace",
"transfer_type": "copy",
"on_initialize": "purge_destination",
"source": {
"connection": {
"id": "{{nfs_connection}}"
},
"target": {
"path":"/"
}
},
"destination": {
"connection": {
"id": "{{cloud_connection}}"
},
"target": {
"path": "/proptest1"
}
}
},
"schedule": {
"mode": "manual"
}
}