I believe that we will be unable to recognize the replication relationship in this configuration because it is defined in RecoverPoint.
Engineering is currently working to define how RecoverPoint might be supported in a future release. It would be a good idea to make sure your use case is described in detail in an IFR.
There are always two approaches available to accommodate repliation in chargeback. The first is to measure capacity at both the primary and secondary and associate it with the charged entity. One drawback to this approach is that OCI must understand the replication relationship, which is challenging if the replication paradigm involves regularly breaking off the secondary, or if replication is defined off of the array.
The second is to measure only on the primary side. In this approach you have some additional options:
- estimate secondary capacity information based on prior knowledge of the replication paradigm; or
- price replication services into the storage tier
If you do estimate the secondary or its cost, you do need to make sure you don't accidentally include some secondary storage in the measurements that are used for chargeback.