Monitoring your transfers with task reports

Task reports provide detailed information about what AWS DataSync attempts to transfer, skip, verify, and delete during a task execution.

Task reports are generated in JSON format. You can customize the level of detail in your reports:

• Summary only task reports give you the necessary details about your task execution, such as how many files transferred and whether DataSync could verify the data integrity of those files.

• Standard task reports include a summary plus detailed reports that list each file, object, or folder that DataSync attempts to transfer, skip, verify, and delete. With a standard task report, you can also specify the report level to show only the task execution's errors or its successes and errors.

Use cases

Here are some situations where task reports can help you monitor and audit your data transfers:

• When migrating millions of files, quickly identify files that DataSync has issues transferring.

• Verify chain-of-custody processes for your files.

Summary only task reports

A report that's only a summary of a task execution includes the following details:

• The AWS account that ran the task execution

• The source and destination locations

• The total number of files, objects, and folders that were skipped, transferred, verified, and deleted

• The total bytes (logical and physical) that were transferred

• If the task execution was completed, canceled, or encountered an error

• The start and end times (including the total time of the transfer)

• The task's settings (such as bandwidth limits, data integrity verification, and other options for your DataSync transfer)

Standard task reports

A standard task report includes a summary of your task execution plus detailed reports of what DataSync attempts to transfer, skip, verify, and delete.

Report level

With standard task reports, you can choose one of the following report levels:

• Errors only

• Successes and errors (essentially a list of everything that happened during your task execution)

For example, you might want to see which files DataSync skipped successfully during your transfer and which ones it didn't. Files that DataSync skipped successfully might be ones that you purposely want DataSync to exclude because they already exist in your destination location. However, a skipped error for instance might indicate that DataSync doesn't have the right permissions to read a file.

Transferred reports

A list of files, objects, and directories that DataSync attempted to transfer during your task execution. A transferred report includes the following details:

• The paths for the transferred data

• What was transferred (content, metadata, or both)

• The metadata, which includes the data type, content size (objects and files only), and more

• The time when an item was transferred

• The object version (if the destination is an Amazon S3 bucket that has versioning enabled)

• If something was overwritten in the destination

• Whether an item transferred successfully

Note

When moving data between S3 buckets, the prefix that you specify in your source location can show up in your report (or in Amazon CloudWatch logs), even if that prefix doesn't exist as an object in your destination location. (In the DataSync console, you might also notice this prefix showing up as skipped or verified data.)

Skipped reports

A list of files, objects, and directories that DataSync discovered in your source location but didn't attempt to transfer. The reasons DataSync skips data can depend on several factors, such as how you configure your task and file permissions. Here are some examples:

• There's a file that exists in your source and destination locations. The file in the source hasn't been modified since the previous task execution. Since you're only transferring data that has changed, DataSync skips that file and doesn't transfer it during your next task execution.

• An object that exists in your source and destination locations changes in your source. When you run your task, DataSync skips this object in your destination because your task doesn't overwrite data in the destination.

• DataSync skips a directory in your source location because it can't read it.

  If this happens and isn't expected, check your access permissions and make sure that DataSync can read what was skipped.

A skipped report includes the following details:

• The paths for skipped data

• The time when an item was skipped

• The reason it was skipped

• Whether an item was skipped successfully

Note

Skipped reports can be large when they include successes and errors, you configure your task to transfer only the data that has changed, and source data already exists in the destination.

Verified reports

A list of files, objects, and directories that DataSync attempted to verify the integrity of during your task execution. A verified data report includes the following details:

• The paths for verified data

• The time when an item was verified

• The reason for the verification error (if any)

• The source and destination SHA256 checksums (files only)

• Whether an item was successfully verified

Note

When you configure your task to verify only the data that's transferred, DataSync doesn't verify directories in some situations or files that fail to transfer. In either case, DataSync doesn't include unverified data in this report.

Deleted reports

A list of files, directories, and objects that were deleted during your task execution. DataSync generates this report only if you configure your task to delete data in the destination location that isn't in the source. A deleted data report includes the following details:

• The paths for deleted data

• Whether an item was successfully deleted

• The time when an item was deleted

Example task reports

The level of detail in your task report is up to you. Here are some example transferred data reports with the following configuration:

• Report type – Standard

• Report level – Successes and errors

Note

Reports use the ISO-8601 standard for the timestamp format. Times are in UTC and measured in nanoseconds. This behavior differs from how some other task report metrics are measured. For example, task execution details, such as TransferDuration and VerifyDuration, are measured in milliseconds.

Example transferred data report with success status

This report shows that an object named object1.txt successfully transferred.

{
    "TaskExecutionId": "exec-abcdefgh12345678",
    "Transferred": [{
        "RelativePath": "/object1.txt",
        "SrcMetadata": {
            "Type": "Regular",
            "ContentSize": 6,
            "Mtime": "2022-01-07T16:59:26.136114671Z",
            "Atime": "2022-01-07T16:59:26.136114671Z",
            "Uid": 0,
            "Gid": 0,
            "Mode": "0644"
        },
        "Overwrite": "False",
        "DstS3VersionId": "jtqRtX3jN4J2G8k0sFSGYK1f35KqpAVP",
        "TransferTimestamp": "2022-01-07T16:59:45.747270957Z",
        "TransferType": "CONTENT_AND_METADATA",
        "TransferStatus": "SUCCESS"
    }]
}

Example transferred data report with error status

This report shows that an object named object1.txt didn't transfer because of an S3 bucket permissions issue. (If you get an error like this, see Providing DataSync access to S3 buckets.)

{
    "TaskExecutionId": "exec-abcdefgh12345678",
    "Transferred": [{
        "RelativePath": "/object1.txt",
        "SrcMetadata": {
            "Type": "Regular",
            "ContentSize": 6,
            "Mtime": "2022-01-07T16:59:26.136114671Z",
            "Atime": "2022-01-07T16:59:26.136114671Z",
            "Uid": 0,
            "Gid": 0,
            "Mode": "0644"
        },
        "Overwrite": "False",
        "DstS3VersionId": "jtqRtX3jN4J2G8k0sFSGYK1f35KqpAVP",
        "TransferTimestamp": "2022-01-07T16:59:45.747270957Z",
        "TransferType": "CONTENT_AND_METADATA",
        "TransferStatus": "FAILED",
        "FailureReason": "S3 Get Object Failed",
        "FailureCode": 40974
    }]
}

Limitations

• Individual task reports can't exceed 5 MB. If you're copying a large number of files, your task report might be split into multiple reports.

• There are situations when creating task reports can affect the performance of your data transfer. For example, you might notice this when your network connection has high latency and the files you're transferring are small or you're copying only metadata changes.