1-800-833-1132 : 1-303-449-6400 |
POST http[s]://{datapathDNSname}/_rest_/data_policy/{data policy UUID, name, or other unique attribute}[?always_force_put_job_creation=TRUE|FALSE][&always_minimize_spanning_across_media=TRUE|FALSE][&blobbing_enabled=TRUE|FALSE][&checksum_type=CRC_32|CRC_32C|MD5|SHA_256|SHA_512][&default_blob_size={64‑bit integer}][&default_get_job_priority=URGENT|HIGH|NORMAL|LOW][&default_put_job_priority=URGENT|HIGH|NORMAL|LOW][&default_verify_after_write=TRUE|FALSE][&default_verify_job_priority=URGENT|HIGH|NORMAL|LOW][&end_to_end_crc_required=TRUE|FALSE][&max_versions_to_keep={32-bit integer}][&name={string}][&rebuild_priority=URGENT|HIGH|NORMAL|LOW][&versioning=NONE|KEEP_LATEST|KEEP_MULTIPLE_VERSIONS]
Specifies the default GET job priority for the data policy. The job priority determines the resources assigned and the processing order. Jobs with priority URGENT can use up all of the resources and prevent other jobs from making progress. Use this priority sparingly. Specifies the default PUT job priority for the data policy. The job priority determines the resources assigned and the processing order. Jobs with priority URGENT can use up all of the resources and prevent other jobs from making progress. Use this priority sparingly. Values: TRUE, FALSE Specifies the default verify job priority for the data policy. The job priority determines the resources assigned and the processing order. Jobs with priority URGENT can use up all of the resources and prevent other jobs from making progress. Use this priority sparingly. Verify jobs can be interrupted every 30 minutes if a job with a higher priority is received. The number of versions of an object to keep if versioning=KEEP_MULTIPLE_VERSIONS.
§ NONE (default) — Only one version of an object may exist at any time and the version number of the object is always 1.
§ KEEP_LATEST — Only one version of the data is available at a time. When a new version of an object is written, the old version is retained until the new version is fully written in compliance with the data policy, and then the old version is deleted.
§ KEEP_MULTIPLE_VERSIONS — Multiple versions of the object, up to the number specified by max_versions_to_ keep are retained.
§ KEEP_LATEST versioning cannot be used for a data policy which uses a storage domain with ltfs_file_naming=OBJECT_NAME (see ltfs_file_naming).
§ KEEP_LATEST requires that the PUT job for the earlier version of the object complete before the PUT of the latest version of the object with the same name in order for the PUT to succeed. <Data>
<AlwaysForcePutJobCreation>
TRUE|FALSE
</AlwaysForcePutJobCreation>
<AlwaysMinimizeSpanningAcrossMedia>
TRUE|FALSE
</AlwaysMinimizeSpanningAcrossMedia>
<BlobbingEnabled>TRUE|FALSE</BlobbingEnabled>
<ChecksumType>CRC_32|CRC_32C|MD5|SHA_256|SHA_512</ChecksumType>
<CreationDate>YYYY-MM-DDThh:mm:ss.xxxZ</CreationDate>
<DefaultBlobSize>{64‑bit integer}</DefaultBlobSize>
<DefaultGetJobPriority>
CRITICAL|URGENT|HIGH|NORMAL|LOW|BACKGROUND
</DefaultGetJobPriority>
<DefaultPutJobPriority>
CRITICAL|URGENT|HIGH|NORMAL|LOW|BACKGROUND
</DefaultPutJobPriority>
<DefaultVerifyAfterWrite>TRUE|FALSE</DefaultVerifyAfterWrite>
<DefaultVerifyJobPriority>
CRITICAL|URGENT|HIGH|NORMAL|LOW|BACKGROUND
</DefaultVerifyJobPriority>
<EndToEndCrcRequired>TRUE|FALSE</EndToEndCrcRequired>
<Id>{string}</Id>
<MaxVersionsToKeep>{32‑bit integer}</MaxVersionsToKeep><Name>{string}</Name>
<RebuildPriority>
CRITICAL|URGENT|HIGH|NORMAL|LOW|BACKGROUND
</RebuildPriority>
<Versioning>NONE|KEEP_LAST</Versioning>
</Data>
Type of checksum used to verify data integrity for any operations involving this bucket unless the operation specifies a different type of checksum.
Values: CRC_32, CRC_32C, MD5, SHA_256, SHA_512 The date and time the data policy was created in the format YYYY-MM-DDThh:mm:ss.xxxZ. Values: TRUE, FALSE The number of versions of an object to keep if versioning=KEEP_MULTIPLE_VERSIONS.