SnapVault using Qtrees

[cferbrache]

I can't seem to get SnapCreator to update my SnapVaults. I have existing SnapVault relationships. When I run it through the GUI it takes snapshots but doesn't update the SnapVaults.

fas6240d:/vol/d_did_001/did_001  fas3040a:/vol/dr_tix_001/did_001    Snapvaulted    627:15:09  Idle

fas6240d:/vol/d_dil_001/dil_001  fas3040a:/vol/dr_tix_001/dil_001    Snapvaulted    627:15:09  Idle

fas6240d:/vol/d_dir_001/dir_001  fas3040a:/vol/dr_tix_001/dir_001    Snapvaulted    627:15:09  Idle

fas6240d:/vol/d_dit_001/dit_001  fas3040a:/vol/dr_tix_001/dit_001    Snapvaulted    650:17:16  Idle

Here is the SnapVault section of my config.

#########################

### SnapVault Options ###

#########################

NTAP_SNAPVAULT_UPDATE=Y

SNAPVAULT_VOLUMES=fas6240d:/vol/d_did_001/did_001,/vol/d_dil_001/dil_001,/vol/d_dir_001/dir_001,/vol/d_dit_001/dit_001

SNAPVAULT_QTREE_INCLUDE=

NTAP_SNAPVAULT_RETENTIONS=daily:3

NTAP_SNAPVAULT_RETENTION_AGE=3

NTAP_SNAPVAULT_SNAPSHOT=Y

NTAP_SNAPVAULT_NODELETE=Y

NTAP_SNAPVAULT_RESTORE_WAIT=N

NTAP_SNAPVAULT_WAIT=

NTAP_SNAPVAULT_MAX_TRANSFER=20480

[ktenzer]

Your syntax for SNAPVAULT_VOLUMES is not correct, it should be  SNAPVAULT_VOLUMES=<src filer>:<vol1,vol2,etc>

It us usually same as VOLUMES parameter, in your example something like

SNAPVAULT_VOLUMES=fas6240d:d_did_001,did_001,d_dil_001,etc

Also NTAP_SNAPVAULT_NODELETE =Y? This should be N unless you dont want SC to ever delete snapshots on secondary?

Please check AIG, the proper syntax is documented

Regards,

Keith

[cferbrache]

I tried that but then it said there was no snapvault relationship.

[andrc]

How about if you try one volume at a time and see if one in particular fails e.g.

SNAPVAULT_VOLUMES=fas6240d:d_did_001

Have you also checked that the SnapCreator server can resolve the controller hostname correctly?

[cferbrache]

Here are the new SnapVault settings:

#########################

### SnapVault Options ###

#########################

NTAP_SNAPVAULT_UPDATE=Y

SNAPVAULT_VOLUMES=fas6240d:d_did_001,d_dir_001,d_dil_001,d_dit_001,d_dia_001

SNAPVAULT_QTREE_INCLUDE=

NTAP_SNAPVAULT_RETENTIONS=daily:3

NTAP_SNAPVAULT_RETENTION_AGE=3

NTAP_SNAPVAULT_SNAPSHOT=N

NTAP_SNAPVAULT_NODELETE=N

NTAP_SNAPVAULT_RESTORE_WAIT=N

NTAP_SNAPVAULT_WAIT=60

NTAP_SNAPVAULT_MAX_TRANSFER=20148

Still getting this:

[Tue Jul 19 14:17:02 2011] DEBUG: ZAPI RESULT
<results status="passed"></results>

[Tue Jul 19 14:17:02 2011] INFO: NetApp Snapvault Status for fas6240d:d_did_001 finished successfully
[Tue Jul 19 14:17:04 2011] ERROR: [scf-00026] No Snapvault Relationship for fas6240d:d_did_001 exist! Exiting

And yes the SnapCreator server can resolve the controller hostname.

[ktenzer]

Your config is correct, well at least snapvault part is correct

Did you add fas3040a to NTAP_USERS? You need to add the secondary credentials, that is only thing I can think of, if they are missing you could get this error.

The error just means SC didnt find any relationships for volume on fas6240d, it is a configuration error somewhere.

What would help is seeing rest of config file and also the api results from snapvault-status, are we actually seeing your relationships? You can certainly investigate in the .out file SC creates further, lots of info there.

Keith

[andrc]

Does a `snapvault update` on the secondary complete successfully?

[peter_lehmann]

The error message gives you the answer...  this does not exist: fas6240d:d_did_001

You need to provide the full path with snapvault, because it is qtree related:

fas6240d:/vol/d_did_001/did_001

This will work.

Peter

[ktenzer · Accepted solution]

Yep issue here was snapvault relationships didnt exist on primary only secondary which can happen if you delete baseline snapshot on primary. Since Snap Creator goes first to primary to find secondary we got message that no relationships exist for given volume, which was 100% correct.

Thanks for the help all

Keith

[cferbrache]

After doing a "snapvault stop /vol/volume/qtree" on the secondary for all volumes. Then doing a "snapvault start -S primary:/vol/volume/qtree /vol/volume/qtree" on the secondary for all volumes I was then able to successfully do a snapvault update using SnapCreator.

Thanks to everyone for there help.