i`ve been using intellisnap with netapp for a long time now at customers but always with the oncommand unified manager.
been trying to test a bit with the netapp open replication now to get rid of the OCUM.
so the setup is….2 netapp simulators, one cifs volume at the source, relationship set up.
snapshot and vault to one destination volume works. snapshot and mirror to another destination volume (from same source) works.
but i am getting errors, when it comes to set up one source volume to one destination volume using BOTH - vault and mirror type. this was working before with ocum - istn it supported with the open replication anymore?
thank you in advance, Sebastian
Best answer by dude
@Sebastian Kupka a few things I want to make sure we all are in the same page.
A few things from the image are not clear, for example:
Is this kl_cdot1-cifs.cv.local your PROD/Primary Cluster Source of the Volume Snaps? Is so, good if not, that is why the error. Source Cluster should be used.
Can you make sure to test
It seems to be that what you are trying to achieve is a Fan Out topology correct?
#1 - Fan Out Concept: One Volume to One or More Destinations
3.2 → Make sure you specify the Source as the Primary Snapshot (In other words your Source Cluster for both Mirror and Vault Copies.
3.3 → In addition to the above, make sure to add the SVM where the volume resides as part of the Vault/Replica copy.
→ Make sure that you have no Aux Copies Schedule running so you give time to run one at a time.
I have seen similar issues where the SVM was not correctly added as 3.3 states AND language issues as well.
The integration between Commvault and Netapp is very smooth and most of the time the issue will be on the NetApp site. I would try to create small volumes for testing as that can be a bit easier on the troubleshooting process and faster as well since the replication will be shorter.
last column - the relationship for our volume with both - mirror and volume enabled.
here the policy configuration
VAULT Copy is running fine
MIRROR is failing
Error Code: [13:226] Description: Error occurred while replicating snaps [ kl_cdot1-cifs.cv.local:SP_2_177361_2389_1615821961], for storage policy [POLICY1] copy [MIRROR] MediaAgent [cv-cs-w2k12]: Backup Job [177361]. Failed to create replica snaps for primary snap job[177361] [Failed to prepare snapshot.]. Source: cv-cs-w2k12, Process: CVJobReplicatorODS
Failed to prepare snapshot. : [No relationships found that can be used to replicate snapshots on file server:[kl_cdot1-cifs.cv.local] for source volume:[Mirror_Vault].Please create a valid relationship if one doesn't exist or wait for data transfer to complete before retrying the operation.If SVM mapping is configured on secondary snapshot copy, file server relationship must conform to the mapping.] Source: cv-cs-w2k12, Process: CVJobReplicatorODS
For open replication, the SVM mapping configured on the secondary copy (Vault or Mirror) will be used to query SVM for the relationship details.
Same destination volume cannot be used as target for both Vault and Mirror. If you are referring to relationship of type MirrorVault, it behaves like a vault copy with an additional functionality of replicating the latest point-in-time of the source volume. So, for open replication relationship of type MirrorVault would behave like a Vault relationship.
As requested by @dude , if you could get the output on the secondary cluster, that would clarify the relationship type.
@Sebastian Kupka a few things I want to make sure we all are in the same page.
A few things from the image are not clear, for example:
Is this kl_cdot1-cifs.cv.local your PROD/Primary Cluster Source of the Volume Snaps? Is so, good if not, that is why the error. Source Cluster should be used.
Can you make sure to test
It seems to be that what you are trying to achieve is a Fan Out topology correct?
#1 - Fan Out Concept: One Volume to One or More Destinations
3.2 → Make sure you specify the Source as the Primary Snapshot (In other words your Source Cluster for both Mirror and Vault Copies.
3.3 → In addition to the above, make sure to add the SVM where the volume resides as part of the Vault/Replica copy.
→ Make sure that you have no Aux Copies Schedule running so you give time to run one at a time.
I have seen similar issues where the SVM was not correctly added as 3.3 states AND language issues as well.
The integration between Commvault and Netapp is very smooth and most of the time the issue will be on the NetApp site. I would try to create small volumes for testing as that can be a bit easier on the troubleshooting process and faster as well since the replication will be shorter.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
