Skip to main content
Solved

Intellisnaps and SRM


Forum|alt.badge.img

Hi,

 

we are configuring the Intellisnap backups for the virtual machines. Configured sublcients with datastore affinity rules. Snapmirror is configured for the datastore to DR site. we want to integrate this set up with SRM, When we made the DR site volume RW and set up a backup & snapmirror to the original location, instead of replicating to the old volume, it is creating a new volume. is there any way we can configure in CV so that reverse replication will be done to the original volume instead of craeting a new volume

 

Thank you 

Jayaram

 

 

Best answer by Jordan

Not familiar with VMWare SRM but what you’re trying to do I believe can be done however requires manual modifications to OCUM DB. You’ll need to talk to NetApp about that as CV basically monitors the OCUM relationship and in your situation, OCUM is essentially creating a new relationship for new destination volume which is causing the double up. The original relationship may need changing to point to new destination volume before you trigger a replication

View original
Did this answer your question?

3 replies

Forum|alt.badge.img+11
  • Vaulter
  • 135 replies
  • May 12, 2022

Hi @Jayaram Ponnaganti 

 

Are you using OCUM or Open Replication? I believe neither will replicate back to original volume name due to NetApp requirements for snaps to not overwrite data.  Thus if an existing volume with data is detected, it will auto replicate to a new volume. 


Forum|alt.badge.img
  • Bit
  • 1 reply
  • May 13, 2022

Thanks @Jordan . 

We are using OCUM. Is there any way we can do this?. Wondering how it is possible through VMware SRM. Because it will also use Netapp snapshots only Correct?

 


Forum|alt.badge.img+11
  • Vaulter
  • 135 replies
  • Answer
  • July 6, 2022

Not familiar with VMWare SRM but what you’re trying to do I believe can be done however requires manual modifications to OCUM DB. You’ll need to talk to NetApp about that as CV basically monitors the OCUM relationship and in your situation, OCUM is essentially creating a new relationship for new destination volume which is causing the double up. The original relationship may need changing to point to new destination volume before you trigger a replication


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings