On This Page
| Table of Contents |
|---|
Overview
This policy determine what DryvIQ should do when it encounters duplicate content names.
| Info |
|---|
Move jobs always use Warn and Skip regardless of the duplicate name policy that is set due to the nature of the job type and the expected behavior. |
Option | Behavior |
|---|---|
"duplicate_names": "rename" | Rename duplicate content. The file name will be appended with (1) to indicate it is the renamed file. This is the default option. |
"duplicate_names": "warn" | Log a warning for duplicate names. |
| Note |
|---|
Ensure to configure this policy when using Bulk Migration API | Batch Mode. |
Duplicate Folder Names
If there are duplicate folder names, DryvIQ will only create the child job for the first folder it encounters and skip the duplicate folder even if the "duplicate_names" policy is set to "rename." Therefore, it is important that you verify there are no duplicate folder names before creating your folder mapping job.
Job JSON Example
| Code Block |
|---|
{
"name":"Simple Transfer Job with Duplicate Name Policy",
"kind": "transfer",
"transfer": {
"duplicate_names": "rename",
"transfer_type": "copy",
"source": {
"connection": { "id": "{{nfs_connection}}" },
"target": {
"path": "/SourcePath"
}
},
"destination": {
"connection": { "id": "{{cloud_connection}}" },
"target": {
"path": "/DestinationPath"
}
}
},
"schedule": {
"mode": "manual"
}
} |
...