# Using DM - Check and Initiate Tasks

__*Using DM*__
__*DM Task Initiated*__

```
start-task [ -s "mysql-replica-01"] ./task.yaml

{
    "result": true,
    "msg": "",
    "sources": [
        {
            "result": true,
            "msg": "",
            "source": "mysql-replica-01",
            "worker": "worker1"
        }
    ]
}
```
-------------------------------------------------------------
-s:
selectable
Specify to execute task.yaml on a specific MySQL source
If set, only start subtasks of the specified task on this MySQL source
config-file:
Must choose
Specify the file path for task.yaml
remove-meta:
selectable
If set, the metadata that existed before the specified task is removed when the specified task is started
start-time:
Optional, format '2021-10-21 00:01:00 'or 2021-10-21T 00:01:00
For incremental tasks, you can roughly specify the starting position of the task with this parameter, which has a higher priority than the binlog location in the task configuration file and the binlog location in the downstream checkpoint
When a checkpoint exists for the task, if the task is started in this way, the DM will automatically turn on safe mode until the checkpoint is synchronized to avoid duplicate data errors when resetting the task to an earlier position. When resetting the starting position forward, if the table schema of the starting position is inconsistent with the current downstream table schema, an error may be reported during synchronization; when resetting the starting position backward, be careful that the skipped binlog may have dirty data downstream
If you specify a time that is too early, the synchronization starts with the earliest binlog
Error start-time {input-time} is too late, no binlog location matches it when you specify a time that is too late