Subscribe

Snapvault configuration

[ Edited ]

Hi,

I have installed Snapcreator for windows and run it against a Oracle database. Snapshoting works fine and now I try to configure the Snapvault part.

I have created Snapvault relations between the primary and secondary filer.

nafiler3> snapvault status

Snapvault is ON.

Source                          Destination                          State          Lag        Status

172.20.5.6:/vol/dnfs_bfuarch/-  nafiler3:/vol/sv_dnfs_bfudb/bfuarch  Snapvaulted    00:14:54   Idle

172.20.5.6:/vol/dnfs_bfudb/-    nafiler3:/vol/sv_dnfs_bfudb/bfudb    Snapvaulted    00:14:12   Idle

172.20.5.6:/vol/dnfs_bfuredo/-  nafiler3:/vol/sv_dnfs_bfudb/bfuredo  Snapvaulted    00:14:32   Idle

When running a backup I see in the console log that snapshots are taken and Snapvault relation status is checked and are marked as OK:

[Wed Sep 28 09:06:37 2011] INFO: Getting NetApp Snapvault Status for 194.1.1.236:dnfs_bfudb

but then the backup job is finnished without  updating the snapvault relations.

There are no error messages in the console log  but these entries can be found in the error log file:

Wed Sep 28 08:41:42 2011] cannot find storage executor for nafiler3 at /<C:\Program Files\Netapp\NetApp_Snap_Creator_Framework\scServer3.4.0\snapcreator.exe>SnapCreator/ZAPIExecutor.pm line 200.

[Wed Sep 28 08:59:29 2011] cannot find storage executor for nafiler3 at /<C:\Program Files\Netapp\NetApp_Snap_Creator_Framework\scServer3.4.0\snapcreator.exe>SnapCreator/ZAPIExecutor.pm line 200.

[Wed Sep 28 09:06:58 2011] cannot find storage executor for nafiler3 at /<C:\Program Files\Netapp\NetApp_Snap_Creator_Framework\scServer3.4.0\snapcreator.exe>SnapCreator/ZAPIExecutor.pm line 200.

I suspect it is some problems with the comunication/login to the secondary filer but I want to make sure I havn't missed anything in the setup.

Thank's in advance

/Fredrik

results status="passed"

[Wed Sep 28 09:06:45 2011] INFO: Getting NetApp Snapvault Status for 194.1.1.236:dnfs_bfuredo

<results status="passed">

[Wed Sep 28 09:06:48 2011] INFO: NetApp Snapvault Status for 194.1.1.236:dnfs_bfuredo finished successfully

[Wed Sep 28 09:06:45 2011] INFO: Getting NetApp Snapvault Status for 194.1.1.236:dnfs_bfuarch

<results status="passed">

[Wed Sep 28 09:06:48 2011] INFO: NetApp Snapvault Status for 194.1.1.236:dnfs_bfuarch  finished successfully

[Wed Sep 28 09:06:40 2011] INFO: NetApp Snapvault Status for 194.1.1.236:dnfs_bfudb finished successfully

Snapvault configuration

What is VOLUMES and NTAP_USERS parameters set to? Do you have nafiler3 in NTAP_USERS?

It looks like you are communicating w/194.1.1.236 however the snapvault relationship is 172.20.5.6?

If this is case you can try setting:

SECONDARY_INTERFACES=194.1.1.236:172.20.5.6/nafiler3

Please explain in detail network setup this seems rather complex

Regards,

Keith

Re: Snapvault configuration

Hi Keith,

I don’t have access to the system now but this is the output from the log showing the parsing of the volume, user and interface parameters:

                    1. Parsing Environment Parameters ##########

DEBUG: Parsing VOLUMES - filer: 194.1.1.236 volume: dnfs_bfudb

DEBUG: Parsing VOLUMES - filer: 194.1.1.236 volume: dnfs_bfuredo

DEBUG: Parsing VOLUMES - filer: 194.1.1.236 volume: dnfs_bfuarch

DEBUG: Parsing NTAP_USERS - filer: 194.1.1.236 user: root

DEBUG: Parsing NTAP_USERS - filer: nafiler3 user: root

DEBUG: Parsing SECONDARY_INTERFACES - filer: 194.1.1.236 Primary Interface: 172.20.5.6 Secondary Interface: nafiler3

The network configuration is that we have the primary filer nafiler2. Nafiler2 has two interfaces, one “public” 194.1.1.236 and one “backup net” 172.20.5.6

The primary filer nafiler2 is connected to the secondary filer on the backup net. 172.20.5.6 < -- > nafiler3

The snapcreator server is communicating with nafiler2 on 194.1.1.236.

Best regards

/Fredrik

Re: Snapvault configuration

Ok if a different interface is used for snapvault you need to use SECONDARY_INTERFACES param as I mentioned above, otherwise things look good.

Regards,

Keith

Re: Snapvault configuration

I did that as this says:

DEBUG: Parsing SECONDARY_INTERFACES - filer: 194.1.1.236 Primary Interface: 172.20.5.6 Secondary Interface: nafiler3

//Fredrik

Re: Snapvault configuration

Can you try this with SC 3.3.0 just unpack 3.3.0 and copy config and run it?

This looks like a bug

Keith

Re: Snapvault configuration

I’m not at the customer now but I will do this tomorrow and let you know of the result.

I attach the logfile from the snap backup.

Regards

/Fredrik

Re: Snapvault configuration

Ok great please collect all logs and config file, that will help us debug further.

We have another customer w/similar issue so we may have a bug w/3.4.0. In 3.3.0 in other customers env it works so crosding fingets

Thanks for the help!

Regards,

Keith

Snapvault configuration

I did some testing today and was able to reproduce this error when not using the storage systems hostname for volumes. For example my storage system is known as cuba2 so I specified IP in VOLUMES and then mapped to name using SECONDARY_INTERFACES, I got same error you see. Could it be that 194.1.1.236 is not the storage systems hostname?

Can you please run following commands on storage systems:

hostname

rdfile /etc/hosts

snapvault status - we only have snapvault status for secondary I need to also see primary.

Also a network diagram with the connectivity would be helpful. I am pretty sure your issue is 194.1.1.236 isnt the default hostname. SC requires you always use the default hostname, so whatever the filer is known as.

Regards,

Keith

Re: Snapvault configuration

Hi Keith,

Yes you are right. We are running Direct NFS on a Windows server so 194.1.1.236 is the address on the dedicated storage net (NFS).

So it might work if I change the ip in the volume config to the actual IP of nafiler2 ?

Best regards

/Fredrik