Data Backup and Recovery

SnapCreator 4.1 SnapVault Relation ignored

SVOLLRAT1
10,355 Views

Hi Everybody

I just did a Test-Upgrade to SC 4.1p1 on my Productive Environment just to see that SnapVault Updates are not working anymore.

The Relations that worked flawless before are suddenly ignored.

Retried the same on 4.1.0 and had the same issue.

########## Running storage discovery ##########

STORAGE-02113: Retrieving SnapVault relationships

STORAGE-02114: Retrieving SnapVault relationships on controller [esctla0009] finished successfully

STORAGE-02110: Retrieving SnapVault status

STORAGE-02111: Retrieving SnapVault status on controller [esctla0010] finished successfully.

Ignoring the snapvault relation with source esctla0009-snapcom:/vol/v_cts_onedc001/data and destination esctla0010:/vol/esctla0009_v_cts_onedc001/data with source status snapvaulted

SCF-00019: SnapVault relationship for [esctla0009]:[v_cts_onedc001] does not exist, Exiting!

Task: storageDiscovery with config:CH_CT_Tests@CH_CT_FS_OneDC failed

The first thing that bugs me is that the fitting Relation is simply ignored, trying the same with 4.0 everything is updated fine.

The second and more concerning part is that nothing is done at all, not even a snapshot on the primary Volume.

Instead everything faults right at the start, unlike with 4.0 when it at least completed with exceptions.

Any suggestsions what may be wrong or what to set to get it working again

Thanks in advance

Stefan

1 ACCEPTED SOLUTION

SVOLLRAT1
9,561 Views

Had to set up the Secondary-Interfaces Option to get it working.

Somehow SnapCreator 4.1 is not able to get the different Hostnames for the Filer-Interfaces so that they have to be defined manually.

This fixed it for me:

SECONDARY_INTERFACES=esctla0009:esctla0009-snapcom/esctla0010

View solution in original post

15 REPLIES 15

spinks
10,307 Views

Stefan,

Was this by chance a qtree SnapMirror relationship?

I am aware of QSM not working with 4.1 (It was never supported, but did work in 4.0 and older versions).

Be sure to check the case on ONTAP as well - I've had this issue if a letter is uppcase in ONTAP but lowercase in SC - ONTAP will see it as an invalid relationship.

Same thing would happen if you sent the command via the ONTAP CLI with the incorrect case.

John

SVOLLRAT1
10,307 Views

Hi John

The Relationship is based on qtree’s.

Is there some not in the Guides stating that qtree’s are not supported? I wouldn’t be aware of any.

Since the Config-File is exactly the same on Test (4.1.0, not working) and Production (4.0p1, working) I’d say we can cancel out the upper/lower-case scenario, but good to know as well.

Freundliche Grüsse / Kind Regards

Stefan Vollrath

Von: John Spinks

Gesendet: Montag, 12. Mai 2014 17:24

An: Vollrath, Stefan

Betreff: - Re: SnapCreator 4.1 SnapVault Relation ignored

<https://communities.netapp.com/index.jspa>

Re: SnapCreator 4.1 SnapVault Relation ignored

created by John Spinks<https://communities.netapp.com/people/spinks> in Snap Creator Framework - View the full discussion<https://communities.netapp.com/message/130202#130202>

Stefan,

Was this by chance a qtree SnapMirror relationship?

I am aware of QSM not working with 4.1 (It was never supported, but did work in 4.0 and older versions).

Be sure to check the case on ONTAP as well - I've had this issue if a letter is uppcase in ONTAP but lowercase in SC - ONTAP will see it as an invalid relationship.

Same thing would happen if you sent the command via the ONTAP CLI with the incorrect case.

John

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/130202#130202>

Start a new discussion in Snap Creator Framework by email<mailto:discussions-community-productsandsolutions-datastoragesoftware-dataprotectionsoftware-backupandrestore-snapcreatorframework@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=4147>

spinks
10,307 Views

Stefan,

We hit this (QSM issue) with a few customers once SC 4.1 was released.

The answer from engineering and QA was that QSM was never supported - it is great that it worked traditionally, but it was never a supported feature.

This was not widely known until QSM stopped working in SC 4.1.

Due to the major changes to support SnapVault in clustered Data ONTAP 8.2, much of the SnapMirror and SnapVault code was rewritten.

Since QSM was not officially supported it was not tested to verify that it still worked.  Once we released several customers hit the same issue I think you are hitting now.

This is covered in the 4.1 release notes in the known limitations section.

I have asked if there is a plan to resolve this issue - Waiting on a response.

John

SVOLLRAT1
10,307 Views

Hi John

I checked the Release note published here:

http://support.netapp.com/NOW/download/software/snapcreator_framework/4.1/

No word regarding SnapVault and QTree’s only, related to SnapMirror.

Also the Release-Notes for 4.1p1 do not state this as known issue.

http://support.netapp.com/NOW/download/software/snapcreator_framework/4.1P1/README

So I don’t see where this would be mentioned in the currently active documentation.

Hope this can be updated so that others won’t have to learn the hard way that the 4.1x release is not usable for certain deployments.

Freundliche Grüsse / Kind Regards

Stefan Vollrath

Von: John Spinks

Gesendet: Montag, 12. Mai 2014 17:53

An: Vollrath, Stefan

Betreff: - Re: SnapCreator 4.1 SnapVault Relation ignored

<https://communities.netapp.com/index.jspa>

Re: SnapCreator 4.1 SnapVault Relation ignored

created by John Spinks<https://communities.netapp.com/people/spinks> in Snap Creator Framework - View the full discussion<https://communities.netapp.com/message/130204#130204>

Stefan,

We hit this (QSM issue) with a few customers once SC 4.1 was released.

The answer from engineering and QA was that QSM was never supported - it is great that it worked traditionally, but it was never a supported feature.

This was not widely known until QSM stopped working in SC 4.1.

Due to the major changes to support SnapVault in clustered Data ONTAP 8.2, much of the SnapMirror and SnapVault code was rewritten.

Since QSM was not officially supported it was not tested to verify that it still worked. Once we released several customers hit the same issue I think you are hitting now.

This is covered in the 4.1 release notes in the known limitations section.

I have asked if there is a plan to resolve this issue - Waiting on a response.

John

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/130204#130204>

Start a new discussion in Snap Creator Framework by email<mailto:discussions-community-productsandsolutions-datastoragesoftware-dataprotectionsoftware-backupandrestore-snapcreatorframework@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=4147>

spinks
10,307 Views

Stefan,

I agree that it should be clearer, but I verified - It's in the release notes.

From the link above click the release notes link: http://support.netapp.com/NOW/download/software/snapcreator_framework/4.1/

Direct link:  https://library-int.corp.netapp.com/ecm/ecm_get_file/ECMP1305840

Go to Page 11 - Known Limitations.

Listed as the last bullet under:

Snap Creator does not support the following Data ONTAP features and functionality:

Performing SnapMirror on qtree

Note:  deduplication and compression are listed in the release notes just because there aren't a full suite of QA test cases around them.  I asked for test cases including failure cases with clear error messages.  Since these don't yet exist they were listed as a doc issue and added to the release notes.

Sorry for the trouble.

John

SVOLLRAT1
10,309 Views

Hi John

The direct Link doesn’t work, probably internal use only.

The following is in the Release-Notes in the first link and it is the same I was referring to before.

I don’t see what you mean, maybe you can elaborate:

Known limitations identify platforms, devices, or functions that are not supported by Snap Creator

4.1, or that do not work correctly with Snap Creator. Review these limitations carefully.

The following list specifies which functions Snap Creator does not support :

• Snap Creator does not create or manage SnapVault and SnapMirror relationships. >> known, not the issue

• Snap Creator does not support the following on clustered Data ONTAP 8.1:

◦ OnCommand Unified Manager server as a proxy

◦ Consistency group Snapshot

• Snap Creator does not support vCenter heartbeat and linked mode.

• Snap Creator does not support the Fujitsu Data ONTAP-v platform.

• Consistency group Snapshot with vFilers is not supported.

• The Infinite Volumes feature for clustered Data ONTAP is not supported.

• Clustered Data ONTAP and Data ONTAP operating in 7-Mode do not support backup on

Snaplock Volume.

• Snap Creator does not support SnapVault operation on secondary clones. >> for me another feature, than qtree-snapvault

• Snap Creator does not support the following Data ONTAP features and functionality:

◦ Volume compression

◦ Deduplication

◦ Infinite volume

◦ Load Sharing Mirror (LSM)

◦ Performing SnapMirror between 7-Mode and clustered Data ONTAP (TDP)

◦ Performing SnapMirror on qtree >> stated for SnapMirror but no mention to SnapVault

• OSSV is only supported with Snap Creator Agent, and is recommended to enable the Agent. The

following OSSV features and functionality are not supported:

◦ Restore for OSSV (primary and secondary)

◦ OSSV with DFM proxy

◦ OSSV with OnCommand Unified Manager Core Package 5.1 and 5.2, which includes the

NetApp Management Console protection and provisioning capabilities

◦ OSSV volumes (primary and secondary) LUN clone and Volume clone operations

◦ Performing with clustered Data ONTAP

◦ Performing with the VOLUME_GROUPS parameter

• VOLUME_GROUPS is only supported for backup operations. The following

VOLUME_GROUPS parameter features and functionality are not supported:

◦ Use with LUN clone and Volume clone operations

◦ Use with primary and secondary clone operations

◦ Performing with OnCommand Unified Manager

Freundliche Grüsse / Kind Regards

Stefan Vollrath

Von: John Spinks

Gesendet: Montag, 12. Mai 2014 18:21

An: Vollrath, Stefan

Betreff: - Re: SnapCreator 4.1 SnapVault Relation ignored

<https://communities.netapp.com/index.jspa>

Re: SnapCreator 4.1 SnapVault Relation ignored

created by John Spinks<https://communities.netapp.com/people/spinks> in Snap Creator Framework - View the full discussion<https://communities.netapp.com/message/130205#130205>

Stefan,

I agree that it should be clearer, but I verified - It's in the release notes.

From the link above click the release notes link: http://support.netapp.com/NOW/download/software/snapcreator_framework/4.1/

Direct link: https://library-int.corp.netapp.com/ecm/ecm_get_file/ECMP1305840

Go to Page 11 - Known Limitations.

Listed as the last bullet under:

Snap Creator does not support the following Data ONTAP features and functionality:

Performing SnapMirror on qtree

Note: deduplication and compression are listed in the release notes just because there aren't a full suite of QA test cases around them. I asked for test cases including failure cases with clear error messages. Since these don't yet exist they were listed as a doc issue and added to the release notes.

Sorry for the trouble.

John

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/130205#130205>

Start a new discussion in Snap Creator Framework by email<mailto:discussions-community-productsandsolutions-datastoragesoftware-dataprotectionsoftware-backupandrestore-snapcreatorframework@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=4147>

spinks
10,312 Views

My mistake - I thought you were asking about qtree SnapMirror per my original question.  I misunderstood.

I'll have to inquire about qtree with SnapVault as I haven't heard anything about this not working.

It was the qtree SnapMirror that is not supported and is documented.

I'll send a query now.

Sorry!

John

spinks
10,308 Views

Stefan - can you let me know if you are using 7-Mode or clustered Data ONTAP?

We're looking into this.

Thanks!

John

SVOLLRAT1
10,308 Views

Hi John

We are still using 7-Mode.

Freundliche Grüsse / Kind Regards

Stefan Vollrath

Von: John Spinks

Gesendet: Montag, 12. Mai 2014 19:45

An: Vollrath, Stefan

Betreff: - Re: SnapCreator 4.1 SnapVault Relation ignored

<https://communities.netapp.com/index.jspa>

Re: SnapCreator 4.1 SnapVault Relation ignored

created by John Spinks<https://communities.netapp.com/people/spinks> in Snap Creator Framework - View the full discussion<https://communities.netapp.com/message/130209#130209>

Stefan - can you let me know if you are using 7-Mode or clustered Data ONTAP?

We're looking into this.

Thanks!

John

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/130209#130209>

Start a new discussion in Snap Creator Framework by email<mailto:discussions-community-productsandsolutions-datastoragesoftware-dataprotectionsoftware-backupandrestore-snapcreatorframework@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=4147>

spinks
9,515 Views

Stefan,

If you are using 7-mode this should work.

I recommend opening a support case to get this resolved.

Sorry I couldn't be of more help.

John

MARC_EGGENBERGER_BWO
9,515 Views

Stefan,

I hit the same issue when trying to implement SC4.1 with the VMware Plugin. Did you open a case and did you already get some more useful information? I'm about to open a case also.

Regards,

Marc

SVOLLRAT1
9,515 Views

Hi Marc

No Case open so far, so no further Details available. Sorry.

Freundliche Grüsse / Kind Regards

Stefan Vollrath

Von: MARC.EGGENBERGER.BWO

Gesendet: Mittwoch, 14. Mai 2014 13:17

An: Vollrath, Stefan

Betreff: - Re: SnapCreator 4.1 SnapVault Relation ignored

<https://communities.netapp.com/index.jspa>

Re: SnapCreator 4.1 SnapVault Relation ignored

created by MARC.EGGENBERGER.BWO<https://communities.netapp.com/people/MARC.EGGENBERGER.BWO> in Snap Creator Framework - View the full discussion<https://communities.netapp.com/message/130334#130334>

Stefan,

I hit the same issue when trying to implement SC4.1 with the VMware Plugin. Did you open a case and did you already get some more useful information? I'm about to open a case also.

Regards,

Marc

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/130334#130334>

Start a new discussion in Snap Creator Framework by email<mailto:discussions-community-productsandsolutions-datastoragesoftware-dataprotectionsoftware-backupandrestore-snapcreatorframework@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=4147>

MARC_EGGENBERGER_BWO
9,515 Views

I did find a solution for my problem. The SnapVault relationship was with a full qualified domain name (FQDN - filer01.internal.company.com). In SnapCreator I only specified the hostname (filer01). Changed that to the FQDN and now it works.

Might want to check if it matches the exact spelling in the SV relationship.

Regards,

Marc

albert_netapp
9,516 Views

Hello All,

I found out official installation and administration guide for SC 3.3.0

Where in point 1.3 “Snapcreator functions” QTREE SNAPMIRROR is supporting.

https://library.netapp.com/ecm/ecm_get_file/ECMM1278894

Could somebody explain why it is not anymore supported in 4.1 version?

SVOLLRAT1
9,562 Views

Had to set up the Secondary-Interfaces Option to get it working.

Somehow SnapCreator 4.1 is not able to get the different Hostnames for the Filer-Interfaces so that they have to be defined manually.

This fixed it for me:

SECONDARY_INTERFACES=esctla0009:esctla0009-snapcom/esctla0010

Public