The transition to NetApp MS Azure AD B2C is complete. If you missed the pre-registration, you will be invited to reigister at next log in.
Please note that access to your NetApp data may take up to 1 hour.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Data Backup and Recovery

move snapvault destination using dfm

Eric_x_Leonard

Hello,

 

We are using two HA pairs running 8.2.4P5 7-mode.

The current disk space is becoming sparse and 2 shelves of 8Tb disks have been added to the system to cope with the snapvault destinations.

The current setup is managed through DFM 5.2.0.

We added the storage config for 8.2.4 in the dfm.

 

What we are trying to do is to move the current snapvault destination from an aggregate to another one.

A snapmirror has been performed to recreate the snapvault destination, after the initial transfer the snapmirror relation has been broken-off.

The new destination has been defined as secondary volume within dfm

We then associated the existing primary volume to the new secondary volume.

This operation completes, with a message

 

"Importing backup relationship between secondary FILER2:/Vault_1 and primary FILER1:/vol1/Qtree1"

 

We then associate the same schedule as the existing snapvault relation

 

The issue is that the new snapvault relation doesn't update and the lag keeps increasing.

When trying to manualy perform an update of the relation, i got the following error message

 

"Could not configure ip_address_of_filer_1as defined in options ndmp.prefered_interface as the transfer interface for filer1:/vol1/qtree1: NDMP communication error: NDMP_SVS_MODIFY_RELATIONSHIP: 0x20500306 (SV NO RELATIONSHIP)"

 

When performing a simple snapvault update on the destination filer, the snapvault relation comes back to an updated state but as the snapshots are created by dfm, this is not a solution.

 

Any idea why this is happening ?

 

PS : I also tried to recreate the relation to a brand new volume, and in this case the dfm can update the relation without problem.

 

Thanks

 

1 ACCEPTED SOLUTION

Sahana

Hi,

 

Refer Kb https://kb.netapp.com/support/s/article/ka11A0000001NEPQA2/um-fails-to-update-snapvault-could-not-configure-ip-address-as-the-transfer-interface?t=149...

(Requires login,)

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

View solution in original post

3 REPLIES 3

Eric_x_Leonard

It indeed solved the issue

It will allow us to increase our capacity 4 weeks earlier 🙂

 

 

Many thanks about this.

 

Eric_x_Leonard

Hello,

 

I just tested this.

I did the snapvault update through dfm/um and the status of the job is failed, BUT the snapvault relation is transfering.

Will wait for the scheduled transfer to check the job status

 

So far so good anyway

 

Thanks

 

 

Sahana

Hi,

 

Refer Kb https://kb.netapp.com/support/s/article/ka11A0000001NEPQA2/um-fails-to-update-snapvault-could-not-configure-ip-address-as-the-transfer-interface?t=149...

(Requires login,)

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

View solution in original post

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public