This section describes how to create a SmartSync pull task to pull objects from the cloud to the local end.
Prerequisites
- The local account and cloud account are both in normal status.
- The local account has the write permission on namespaces and objects of the namespaces.
- The local account has the write permission on log namespaces and objects of the log namespaces.
- The cloud account has the access permission on the target bucket and objects of the target bucket. For details about the interface requirements, see SmartSync Feature Guide for Object > Feature Description > Availability in the Feature Guide of the corresponding version.
- The local namespace is in normal status.
- The object protocol has been enabled for the local namespace.
- The local log namespace is in normal status.
- The target bucket on the cloud is in normal status and the object protocol has been enabled.
- The node connection between the local end and the cloud is in normal status.
Procedure
- Choose Resources > Dataflow > SmartSync > Pull Tasks.
- Select a desired account from the Account drop-down list in the upper left corner.
- Click Create.
The Create SmartSync Pull Task page is displayed.
- Set basic information about the SmartSync pull task. Table 1 describes related parameters.
Table 1 Basic parameters of a pull task Parameter
Description
Task Name
Name of the SmartSync pull task.
NOTE:The name can contain only letters, digits, special characters !"#$%&'()*+,-./:;<=>?@[\]^_`{|}~, and spaces, and cannot start or end with a space.
Namespace
Namespace created by the local cluster account.
Heterogeneous Device
Cloud device.
NOTE:If no heterogeneous device is available, add one by following the instructions provided in Adding a Heterogeneous Device.
AK Alias
Alias of the service access user of the heterogeneous device.
NOTE:- After you select a heterogeneous device, the AK alias of the heterogeneous device will be displayed in the drop-down list.
- After you select the AK alias, the AK of the account (account or object user AK of the heterogeneous device, used for the local storage to connect to the heterogeneous device) will be automatically displayed in the lower part.
Target Bucket Name
Name of the target bucket of the heterogeneous device.
NOTE:- The target bucket name consists of 1 to 255 characters, including only letters, digits, hyphens (-), underscores (_), and periods (.). It must contain at least one letter or digit.
- If the heterogeneous device is an OceanStor Pacific series product, the target bucket is an OceanStor Pacific series namespace.
Execution Mode
Execution mode of the task. Only One-off is supported. That is, the task pulls the target data from the cloud only once.
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 Namespace
Namespace for storing task execution logs.
NOTE:- The log namespace cannot be the same as the namespace.
- The log namespace cannot be the audit log namespace.
Log Path
Path for storing logs in the log namespace, which is used to distinguish logs of the task from logs of other tasks.
NOTE:The value can contain only letters, digits, underscores (_), periods (.), slashes (/), and hyphens (-).
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.
- (Optional) Enable Filter Policy. You can select Custom or By file list as required.
- Custom: List target data by object prefix.
- By file list: List target data by importing a customized object name list.
The file list supports only the UTF-8 format.
- Click OK. The SmartSync pull task is created.