Considerations for cross-release replication

HCP release 9.x systems support replication with other release 9.x systems and with release 8.x systems. HCP does not support replication between 9.x systems and systems earlier than 8.0.

Cross-release replication and erasure coding topologies

Erasure coding topologies cannot include HCP systems at a release earlier than 8.0.

Cross-release replication and multipart objects

HCP cannot replicate multipart objects between a 9.x system and an 8.x system. As a result:

When you add a tenant to a cross-release replication link, HCP automatically pauses replication of that tenant if both of the following are true for any of the tenant's namespaces:

oThe namespace has replication enabled.

oThe namespace contains one or more multipart objects.

When you select a namespace for replication, HCP automatically pauses replication of the tenant that owns that namespace if both of the following are true:

oThe replication link on which the tenant is being replicated is a cross-release link.

oThe namespace contains one or more multipart objects.

When a multipart upload is completed on a namespace, HCP automatically pauses replication of the tenant that owns that namespace if both of the following are true:

oThe namespace has replication enabled.

oThe replication link on which the tenant is being replicated is a cross-release link.

© 2015, 2020 Hitachi Vantara LLC. All rights reserved.