topic Unable to find any healthy resource on NetApp Storage in Data Protection

Unable to find any healthy resource on NetApp Storage

ChrisLumnah — Fri, 21 Jul 2017 18:45:26 GMT

When trying to create a backup job in Snapcenter 2.0 P2, we are gettign failure error messages like the below.

What are the causes to this type of error message and how do i resolve them?

Re: Unable to find any healthy resource on NetApp Storage

Ebin_SME_ORACLE — Tue, 25 Jul 2017 09:58:11 GMT

Hello,

I think you might have to detach and re-attach the ONTAP SVM with NetApp SnapCenter. If not , let me now.

Regards,

Ebin

Re: Unable to find any healthy resource on NetApp Storage

S-Sahu — Fri, 17 Apr 2020 12:00:26 GMT

Hi,

Getting a peculiar issue while backing up on snapcentre:

Controller Event:

app.log.err: XXXXXXXXXXX: SnapCenter Software 4.1.1.3201: (1002) Error: Job [3141] Activity [Creating SQL Backup] failed with error: The following activities failed:Registering invalid databases,Grouping Resources. Please check the activities for detailed error message.

Message Name:

app.log.err

Sequence Number:

264333

Description:

This event is issued when an application encounters an error condition.

Action:

(UNKNOWN)

SnapCenter error:

Failed on 'XXXXXXXXXXX':

Activity 'Registering invalid databases' failed with error: Unable to find any healthy resource on NetApp storage.

Activity 'Send EMS Messages' failed with error: Unable to find storage system for given resources. EMS message instead sent to the

storage connection accessible by this user:@@@@@@@@@@@@@@

Failed on '@@@@@@@@@@':

Activity 'Registering invalid databases' failed with error: Unable to find any healthy resource on NetApp storage.

Activity 'Send EMS Messages' failed with error: Unable to find storage system for given resources. EMS message instead sent to the

storage connection accessible by this user:@@@@@@@@@@@@@

Re: Unable to find any healthy resource on NetApp Storage

Maxar075 — Sat, 14 Nov 2020 21:17:44 GMT

I encountered the same issue - the fix for me was disabling IPv6 on the SnapCenter Server.