About MSDP S3 object import
In earlier NetBackup releases, a replication storage lifecycle policy (SLP) for MSDP-Object-Store backups only replicates the NetBackup backup image and imports it into the replica domain's NetBackup catalog. The underlying S3 objects themselves were not synchronized between MSDP S3 buckets on the two domains.
MSDP S3 object import lets you keep a production MSDP S3 bucket and a disaster recovery replica bucket in sync. Data that is ingested into an MSDP S3 bucket on one MSDP instance (a Flex appliance or build-your-own MSDP server) is synchronized to a bucket of the same name on another MSDP instance in a replica domain, using your existing AIR/SLP replication. As a result, failover clients see the same objects in the replica bucket without needing to run a restore.
MSDP S3 object import reuses the existing Auto Image Replication (AIR) and storage lifecycle policy flow; it does not require a separate replication mechanism. When an MSDP-Object-Store backup image is replicated to the replica domain, NetBackup also triggers an import operation that reconstructs the bucket's objects on the replica MSDP S3 server from the replicated image's object catalog. The same flow works in the reverse direction, so either domain can act as source or target.
Note:
Synchronization between the production and replica MSDP S3 buckets is not real-time. Objects appear in the replica bucket only after the backup and replication jobs for that image have completed. Avoid writing new objects into a bucket while a backup, replication, or import operation is in progress on that bucket.
Supported platforms: MSDP build-your-own (BYO) server, NetBackup Flex Appliance.
See About S3 interface for MSDP .