Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Verify the current upload statistics.This repeats every 5 s for 60 iterations. "Out" and "writes" counters are incrementing showing that data is being written to cloud target. # isi statistics cloud list –long –i 5 -r 60 Timestamp Account Policy Cluster-GUID In Out Reads Writes Deletions Cloud A-Key P-ID Node ------------------------------------------------------------------------------------------------------------ 1722419028 XXXXXXX 1.7GB 0.0B 5543 0 0 ECS 5 0 3 1722419028 XXXXXXX 1.7GB 0.0B 7501 0 0 ECS 5 0 5 1722419028 XXXXXXX 280.5MB 0.0B 143 0 0 ECS 5 0 1 1722419028 XXXXXXX 23.6MB 0.0B 111 0 0 ECS 5 0 9 Verify the current running job. See the below example. Clustername-2# isi cloud job v 198 ID: 198 Description: Effective State: running Type: archive Operation State: running Job State: running Create Time: 2024-XX-23T21:37:55 State Change Time: 2024-XX-31T17:50:57 Completion Time: - Job Engine Job: 139852 Job Engine State: succeeded Total Files: 51636073 Total Canceled: 8821 Total Failed: 0 Total Pending: 26476633 Total Staged: 0 Total Processing: 148 Total Succeeded: 25150471
There are SyncIQ read-only paths as part of the CloudPools file pool policy base-path. Since these are read-only directories, the file cannot be replaced with a stub or SmartLink file as it has CBM_RESTRICTED_MODIFY flags.
List the SyncIQ read-only domains with the below command: isi sync target list | grep -i writes_disabled Modify the CloudPools file pool policy to skip the path which is read-only. isi filepool pol modify couldpoolpolicyname --begin-filter –path=”existingpath” --and --path=”readonly_path which needs to be skipped” --operator=ne --end-filter Bring CloudPools file pool policy to the top of the order in policy priorityStart the CloudPools job manually by specifying the path or start the SmartPools job isi cloud archive --recursive yes --policy As the path is specified manually, the starting path can be explicitly specified. All that is needed is for the path to be part of the path that is listed in the file pool policy. CloudPools initiates the scan of the files listed under the path and matches them against the file pool policy. Matching files are added to the queue for CloudPools to process, and the Archive job created. Note: There are requirements that the file under the read-only path cannot be skipped and must go to cloud target. In such cases, remove the SyncIQ domain such that the files are returned to a read/write state with the below command: isi sync target break --target-path SyncIQreadonlypath Breaking a policy's target association results in requiring a full synchronization of all data on the next sync. Are you sure? (yes/[no]): Yes