dfmp dataset one relationship got error

[philipp_pluess]

hello community

i have a problem with one of my dataset.

the dataset contains 15 snapvault realationships (several qtrees from two volumes)

now one of the relationships does not backup anymore.

this is what the job is telling me:

1. > replication destination cannot find a file for which the source sent data

2. > NDMP error: LRD GENERIC

there is enough space in the destination volume, so no worries about that.

i tried to rerun the protection job, but still, this relationship does not work with same error.

all the other 14 relationships work well.

can anyone help?

thanks

philipp

[argiri]

Need more information on the problem

Can you please provide the output of dry run output:

Command: dfpm dataset list -D  <datasetid>

And Dataset Relationship: dfpm dataset list -R <datasetid>

Also provide the job details, command : dfpm job details <jobid>

Does the relationship exist on filer SV src and SV dest.?

[philipp_pluess]

hi argiri

sorry, was absent for several days...

the questioned information is in the attachement.

regards

philipp

[argiri]

Dry run results and relationships status looks fine. How oftern these error messages occur, do you see any pattern.?

There are two erros meesages reorted in job logs

1.

Error Message:          phenix.bfh.ch: replication destination cannot find a file for which the source sent data

2.

Error Message:          phenix:/sv_ahb_data_01_v0_sata_enge_1: NDMP error: LRD GENERIC

Both the error messages are recived from sv destination filer. second error message is related to ONTAP NDMP.

Need to discuss with ONTAP NDMP team to know when we receive this NDMP error message. This ndmp error

message need to be addressed first.

As rightly pointed while creating the case the first error message can occur when destination volme is going out-off space.

Error Message:          phenix.bfh.ch: replication destination cannot find a file for which the source sent data

Thanks

Giridhar

[argiri]

These error messages need more investigation from ontap perspective. Please raise a Escalation burt for further investigation.

[philipp_pluess]

Hi Giridhar

*See any pattern*

Yes, the error occures every time the dataset is running.

should i open a case?

thanks

philipp

[argiri]

yes. Go ahead open a case. Thanks Giridhar

[rwelshman]

Not sure the exact cause of that issue. But if you wanted, you could attempt to remove the problem destination out of the dataset. The dataset will go non-conformant and then on conformance create a new destination and sync with the source. The old destination will still be in place until you remove it after the snapshot retention time clears.

[philipp_pluess · Accepted solution]

hello community

as netapp support helped me resolving the problem, i describe the solution provided:

1. In dfm, quiesce the relationship. (suspend)

2. stop the affected relationship.

3. delete the qtree, if stopping didn't do so.

4. start the relationship again, within dfm. (should conform the relationship again.)

tataa.

regards

philipp