Tenant name collisions
A tenant name collision occurs when the Replication service tries to replicate an HCP tenant from one HCP system to another HCP system that already has a different tenant with the same name.
To recover from a tenant name collision, take one of these actions:
- Rename the tenant on one of the systems involved in the link.
- Delete the tenant on the receiving system.
Here are two scenarios that show how a tenant name collision can cause the Replication service to pause replication of a tenant.
Scenario 1
In this scenario:
- System A replicates to system B on link AB. Link AB can be either active/active or active/passive.
- System A has a tenant named T1 that is not on link AB.
These events occur in the order shown:
- On system A, you add T1 to link AB.
- Before T1 is replicated to system B, you create a tenant named T1 on system B.
- The Replication service tries to replicate T1 to system B. The replication is unsuccessful because a different tenant named T1 already exists on system B. As a result, the service automatically pauses replication of T1 on link AB.
Scenario 2
In this scenario:
- System A replicates to system B on link AB, which replicates to system C on link BC, where link AB is chained into link BC. Link AB can be either active/active or active/passive. Link BC is active/passive.
- System A and system C each have a tenant named T1, where T1 was created independently on each system.
These events occur in the order shown:
- On system A, you add T1 to link AB.
- T1 is replicated to system B.
- Because link BC includes link AB, the Replication service tries to replicate T1 to system C. The replication is unsuccessful because a different tenant named T1 already exists on system C. As a result, the service automatically pauses replication of T1 on link BC.