topic Re: Snapvault may not work using IP address and it is not recommended in Data Protection

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

SPLUNKOR88 — Thu, 05 Jun 2025 05:52:23 GMT

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

Arora_Kapil — Tue, 08 Oct 2013 12:35:05 GMT

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

ktenzer — Tue, 08 Oct 2013 13:06:26 GMT

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

SPLUNKOR88 — Tue, 08 Oct 2013 13:07:08 GMT

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

Arora_Kapil — Tue, 08 Oct 2013 13:24:04 GMT

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

ktenzer — Tue, 08 Oct 2013 13:26:12 GMT

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

SPLUNKOR88 — Tue, 08 Oct 2013 14:42:32 GMT

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

SPLUNKOR88 — Tue, 08 Oct 2013 14:51:32 GMT

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

Arora_Kapil — Tue, 08 Oct 2013 15:01:22 GMT

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

SPLUNKOR88 — Tue, 08 Oct 2013 15:04:45 GMT

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

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

Arora_Kapil — Tue, 08 Oct 2013 15:12:45 GMT

This looks correct.

Are you still using IPs or you switched to hostnames?

Which version of Snap Creator is this?

Your NTAP_USERS should look something like this

NTAP_USERS= hwducsnetapp01:username/password;ascnetapp1:username/password

VOLUMES=hwducsnetapp01:vol_iso

SNAPVAULT_VOLUMES=hwducsnetapp01:vol_iso

is this correct?

If you still have IPs I would suggest replacing them with names and adding entry to etc/hosts or nameserver.

Thanks,

Kapil

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

SPLUNKOR88 — Tue, 08 Oct 2013 15:17:21 GMT

When I was using IP addresses, I was getting an error earlier than this. Everything is configured via DNS now.

NTAP_USERS=HWDUCSNETAPP02:root/2f6778472f766f467536696548766c486a6752644d413d3d0a;HWDUCSNETAPP01:root/2f6778472f766f467536696548766c486a6752644d413d3d0a;HWDNETAPP1:root/724a75644e513068447370616c465437534e335961413d3d0a;HWDNETAPP2:root/724a75644e513068447370616c465437534e335961413d3d0a;ASCNETAPP2:root/724a75644e513068447370616c465437534e335961413d3d0a;ASCNETAPP1:root/724a75644e513068447370616c465437534e335961413d3d0a

SNAPVAULT_VOLUMES=HWDUCSNETAPP01:vol_iso

VOLUMES=HWDUCSNETAPP01:vol_iso

I verified there are no IP addresses. SC version 4.01p

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

SPLUNKOR88 — Tue, 08 Oct 2013 15:19:45 GMT

Sorry, I meant to say everything is configured by hostname now. It is all resolvable and I fixed my DNS issues. Nothing is configured by IP address in SC.

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

Arora_Kapil — Tue, 08 Oct 2013 15:25:15 GMT

I am not very sure but his might be an issue with the host-name being in capital letters in the config and small letters on the controller.

This may be a bug in Snap Creator 4.0p1 but I will need to ask the Snap Creator team to verify.

I will check with them and in the mean time you can try replacing capital letters with small letters in the config file and let me know.

Thanks,

Kapil

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

SPLUNKOR88 — Tue, 08 Oct 2013 15:32:57 GMT

Thanks. Please let me know. I think so too… I am converting the names now.

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

SPLUNKOR88 — Tue, 08 Oct 2013 15:35:21 GMT

Thanks for your help! It’s case sensitive. The issue happened because I scanned in the NetApp storage systems in System Manager using lower cased names. When I created the SV relationship in System Manager, it made those relationships in lower case. In SnapCreator, the NetApp storage systems were capitalized and couldn’t detect the relationship.

The update works now.

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

Arora_Kapil — Tue, 08 Oct 2013 15:38:56 GMT

I am happy it finally worked for you.

I will raise a bug for 4.1 release if it is not already present.

Thanks for your patience.

Please close this thread if you don't have any more question.

Kapil