Modifying a Pull Task

Procedure

1. Choose Resources > Dataflow > SmartSync > Pull Tasks.
2. Select a desired account from the Account drop-down list in the upper left corner.
3. Click More on the right of a desired pull task in the list and choose Modify.

   The Modify SmartSync Pull Task page is displayed.

4. Modify parameters of the SmartSync pull task. Table 1 describes related parameters.

   Table 1 Parameters of a SmartSync pull task

   Parameter	Description
   Task Name	Name of the SmartSync pull task.
   Auto Start	Whether the task is automatically started after being created. The value can be Start now or Start later. Start now The task is started and executed immediately after being created. Start later The task is not started until the manually set target time is reached. When the target time arrives, the system executes the task immediately. NOTE: This function is disabled by default. After a task is created, you need to manually start the task. After this function is enabled, the task will be started and executed based on the customized rule for starting after being created.
   Log Scope	Scope of logs to be recorded. Exception logs Only operation logs about task execution failures are recorded. All logs All logs are recorded, including operation logs about successful task execution and task execution failures.
   Consistency	Whether to verify data consistency at the local end. After this function is enabled, the local end can check the consistency between the digest values carried by cloud objects and those calculated based on real-time data. You can select either the MD5 or SHA-256 algorithm for consistency check. NOTE: Enabling this function will affect data transmission performance. Consistency check is not performed for multipart objects. The MD5 algorithm is used by default for consistency check. To use the SHA-256 algorithm for verification, you need to run CLI commands to enable it. For details, see SmartSync Feature Guide for Object > FAQs > How Do I Query and Modify the Consistency Check Algorithm Type? in the feature guide of the corresponding version. The cloud objects must carry the x-amz-checksum-sha256 HTTP header.
   Retain Local Object ACL	Whether to assign the ACL of a local object to the object with the same name pulled from the cloud. NOTE: Enabling this function will affect replication performance. You are advised to disable this function if no ACL is configured for local objects.
   Max. Speed per Node	Maximum transmission speed of a storage node. [Value options] Low (150 MB/s) Medium (300 MB/s) High (450 MB/s) Highest (10240 MB/s) Custom Enter a value to customize the maximum speed. The value ranges from 1 MB/s to 10240 MB/s. NOTE: Total node speed = Maximum speed per node x Number of nodes. The smaller value between the "maximum bandwidth in the QoS policy configured for the heterogeneous device" and "total node speed" is the maximum data transmission speed of the task. This speed affects foreground services. When the foreground service load is heavy, a smaller value is recommended.
   Max. Speed for Specified Period	You can set the maximum transmission speed for a specific period. Start and End Dates Set a start date and an end date (format: YYYY-MM-DD). The start date must be earlier than the end date. Start and End Time Set start and end time based on the start and end dates (format: HH:MM:SS). The start time must be earlier than the end time. Max. Speed per Node Set a maximum transmission speed based on the start date, end date, start time, and end time. Value range: 1 MB/s to 10240 MB/s. NOTE: You can set a maximum of three time segments and their respective maximum speed per node. In the period specified by Start and End Dates, the task is executed based on Max. Speed per Node set in the period specified by Start and End Time every day.

5. Click OK.