You cannot back up or dump new objects into a bucket while an import operation is in progress for that bucket.

Only one import operation at a time is allowed per bucket. Concurrent imports for the same bucket are serialized.

If an import fails due to a transient error, it is retried automatically. A retry starts the import over from the beginning rather than resuming.

Only replicated MSDP-Object-Store backups can be imported on the remote site. You cannot import a local backup on the same site where it was created.

You cannot retrieve objects from a bucket while an Import into S3 bucket job is in progress for that bucket. This is expected behavior as object retrieval is not allowed on a bucket during import to avoid returning inconsistent data.

If an import fails more than the maximum configured retry count (CATALOG_IMPORT_FAILED_MAX_RETRIES), NetBackup stops trying to import that specific backup image - neither the automatic replication workflow nor a manual import through the API can import it after that. Import resumes normally with the next replicated backup for the same bucket and policy.