Namespace compliance issues

Different HCP systems can have different definitions for service plans with the same name. When an HCP tenant or namespace is replicated, the name of its associated service plan, not the service plan itself, is replicated with it. As a result, the service plan that applies to a namespace can differ on the two HCP systems involved in a link on which the namespace is being replicated.

Service plans can be compliant or noncompliant. However, the service plan that applies to a namespace in compliance mode must be compliant. A namespace compliance issue occurs when replication of a namespace in compliance mode would cause a noncompliant service plan to apply to the namespace on the receiving system.

To recover from namespace compliance issue, you can take any of these actions:

Redefine the noncompliant service plan on the receiving system to be compliant.

If the service plan is assigned to the tenant that owns the namespace, assign a different service plan to the tenant on the sending system, where that service plan is complaint on both systems involved in the link.

If the service plan is assigned to the namespace, have the tenant administrator assign a different service plan to the namespace on the sending system, where that service plan is complaint on both systems involved in the link.

Deselect the namespace from replication.

Release 6.x systems do not have the concept of compliant or noncompliant service plans. As a result, namespace compliance issues do not occur with cross-release replication where the replica is the 6.x system.

Here are two scenarios that show how a namespace compliance issue 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.

Link AB includes tenant T1, so T1 exists on both systems.

On system A, T1 owns namespace NS1, which is in compliance mode. NS1 not selected for replication.

The service plan that applies to NS1 is named SP1. SP1 is compliant on system A and noncompliant on system B.

These events occur in the order shown:

1.On system A, you select NS1 for replication.

2.The replication service tries to replicate NS1 to system B. The replication is unsuccessful because it would cause NS1, which is in compliance mode, to have a noncompliant service plan 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. Link AB can be either active/active or active/passive.

Link AB includes namespace NS1, which is owned by tenant T1, so NS1 exists on both systems.

NS1 is in enterprise mode, not compliance mode.

The service plan that applies to NS1 is named SP1. SP1 is compliant on system A and noncompliant on system B.

These events occur in the order shown:

1.On system A, you change NS1 to be in compliance mode.

2.The replication service tries to replicate the change to system B. The replication is unsuccessful because it would cause NS1 to be in compliance mode with a noncompliant service plan on system B. As a result, the service automatically pauses replication of T1 on link AB.

Trademark and LegalDisclaimer

© 2016 Hitachi Data Systems Corporation. All rights reserved.