Each HCP namespace you create in an HCP system has an internal ID that uniquely identifies that namespace. As a result, two namespaces created on different systems are different from each other, even if they have the same name and are owned by the same tenant.
A namespace name collision occurs when the Replication service tries to replicate a namespace from one system to another system that already has a different namespace with the same name, where both namespaces are owned by the same tenant.
To recover from a namespace name collision, take one of these actions:
•Rename the namespace on one of the systems involved in the link.
•Deselect the namespace from replication.
•Delete the namespace on the receiving system.
Here’s a scenario that shows how a namespace name collision can cause the Replication service to pause replication of a tenant. In this scenario:
•System A and system B replicate to each other over active/active link AB.
•Link AB includes tenant T1, so T1 exists on both systems.
•On system A, T1 owns namespace NS1, which is not selected for replication.
These events occur in the order shown:
1.On system A, you select NS1 for replication.
2.Before NS1 is replicated to system B, you create a namespace named NS1 for T1 on system B.
3.The Replication service tries to replicate NS1 to system B. The replication is unsuccessful because a different namespace named NS1 already exists on system B. As a result, the service automatically pauses replication of T1 on link AB.
© 2015, 2020 Hitachi Vantara LLC. All rights reserved.