Subscribe
Accepted Solution

Snapvault may not work using IP address and it is not recommended

[ Edited ]

Hello,

I'm trying to take a snapshot on the primary and then snapvault it to the secondary. I've already created a snapvault relationship between the source and destination. All I want to do is run the backup, then SnapVault update to the secondary.

I'm getting the following error:

Snapvault may not work using IP address and it is not recommended

I've scanned in the controllers using IP address in SnapCreator. System Manager created the SnapVault relationships.

Re: Snapvault may not work using IP address and it is not recommended

Hi,

We don't recommend using IP addresses for configs with SnapVault or SnapMirror updates enabled.

But if you would still like to use them you can set ALLOW_IP_ADDR=Y in the configuration.

Thanks,

Kapil

Re: Snapvault may not work using IP address and it is not recommended

Using IPs will only work if when you do snapvault status on controllers you also only see IPs.

SC cant translate IP to name yet

Regards,

Keith

Re: Snapvault may not work using IP address and it is not recommended

Where is SnapCreator pulling this “Ip address from”. I created the SnapVault relationship through System Manager. Is it checking SnapCreator that it detects an IP address is being used or on the NetApp storage system itself. Can you point me in the right direction so that I can have it use the host name.

Regards,

Re: Snapvault may not work using IP address and it is not recommended

Snap Creator is complaining because you are using IP address in your configuration files in NTAP_USERS parameter which stores controller credentials.

If you use only host-names in your configuration for both NTAP_USERS, VOLUMES and SNAPVAULT_VOLUMES parameter everything should work fine.

Kapil

Re: Snapvault may not work using IP address and it is not recommended

SC simply looks at what controller name is in config parameters VOLUMES and SNAPVAULT_VOLUMES. Then it does snapvault status on secondary. It then compares, if it finds relationships for volume that match controller name from config and it does update if not it sends error that no relationships were found.

Keith

Re: Snapvault may not work using IP address and it is not recommended

Thanks guys! I got past the initial problem.

I created a SnapVault relationship in System Manager and when I run the SC backup, it goes to perform a SnapVault update. When it runs, I get the following error:

I see the SnapVault relationship in an idle state in System Manager.

ERROR: SCF-00019: No Snapvault Relationship for :[vol_iso] exist! Exiting

Re: Snapvault may not work using IP address and it is not recommended

Does SC automatically perform a SnapVault initialize? Should I have not created the relationship outside of SC?

It looks like it’s picking up the relationship.

Error log:

0:13:33,466] INFO: STORAGE-02110: Retrieving SnapVault status.

INFO: STORAGE-02111: Retrieving SnapVault status finished successfully.

INFO: Ignoring the snapvault relation with source hwducsnetapp01:/vol/vol_iso and destination ascnetapp1:/vol/SC_ISO/SC_ISO_sv with source status source

ERROR: SCF-00019: No Snapvault Relationship for :[vol_iso] exist! Exiting

Re: Snapvault may not work using IP address and it is not recommended

Please can you copy and paste the results of command 'snapvault status' on both primary and secondary controllers so that we can analyze the problem.

Thanks,

Kapil

Re: Snapvault may not work using IP address and it is not recommended

Thanks!

Source:

hwducsnetapp01> snapvault status

Snapvault is ON.

Source Destination State Lag Status

hwducsnetapp01:/vol/vol_iso ascnetapp1:/vol/SC_ISO/SC_ISO_sv Source 03:17:18 Idle

hwducsnetapp01>

Destination:

ascnetapp1> snapvault status

Snapvault is ON.

Source Destination State Lag Status

HWDSMSP1:APPS-NC.HWDSMSP1.1381167154 ascnetapp1:/vol/NSB_HWDSMSP1/[HWDSMSP1]HWDSMSP1@APPS_ Snapvaulted 21:28:21 Idle

HWDSMSP1:.HWDSMSP1.1381167154 ascnetapp1:/vol/NSB_HWDSMSP1/[HWDSMSP1]HWDSMSP1@ Snapvaulted 21:28:30 Idle

HWDSMSP1:.HWDSMSP1.1381167154 ascnetapp1:/vol/NSB_HWDSMSP1/[HWDSMSP1]HWDSMSP1@ Snapvaulted 21:28:12 Idle

HWDSYNCSORT1:APPS-NC.NSB_MASTER.1381155594 ascnetapp1:/vol/NSB_MASTERSERVER/[NSB_MASTER]HWDSYNCSORT1@APPS_ Snapvaulted 24:41:10 Idle

HWDSYNCSORT1:.NSB_MASTER.1381155594 ascnetapp1:/vol/NSB_MASTERSERVER/[NSB_MASTER]HWDSYNCSORT1@ Snapvaulted 24:40:43 Idle

HWDSYNCSORT1:.NSB_MASTER.1381155594 ascnetapp1:/vol/NSB_MASTERSERVER/[NSB_MASTER]HWDSYNCSORT1@ Snapvaulted 24:41:01 Idle

HWDSYNCSORT1:.NSB_MASTER.1381155594 ascnetapp1:/vol/NSB_MASTERSERVER/[NSB_MASTER]HWDSYNCSORT1@ Snapvaulted 24:40:52 Idle

hwducsnetapp01:/vol/vol_iso ascnetapp1:/vol/SC_ISO/SC_ISO_sv Snapvaulted 03:17:49 Idle