nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SnapCenter 4.2 backup job triggers emergency event on NetApp Filers

storageland

Hi,

we just upgraded our SnapCenter from 4.1.1P4 to 4.2. We use Data Broker Appliance 1.0 to back up VMs on Vmware vSphere. Migration was successful and backup jobs are running, but with every successful backup we see an event of severity 'emergency' on our filers, like that:

app.log.emerg: ltnadb1: SnapCenter VMware OVA Software 4.2: (0) Info: Backup job [32], Host Name [ltnadb1], Host OS [Linux], Resource Group [Daily Backup of VMs], Resource Group Size [68], Policy [SMVI_DAILY__2], status [completed successfully], Completion Time [00:01:44]

Everything else looks fine, this may be just an informational event, but severity is of type 'emergency'. Anyone else who has seen such behavior? vCenter is 6.7U2, filer OS is Ontap 9.3P13.

Regards, Frank

Find more posts tagged with

Accepted answers

pranjith

This is resolved with Netapp databroker 1.0.1 and availble.

All comments

Ontapforrum

Hi,

Interesting case. I looked up this message in the syslog translator, and it says:

Message Name: app.log.emerg
Severity: EMERGENCY
Corrective Action: Contact NetApp technical support.
Description: This message occurs when an application encounters a fatal error and requires immediate attention.

Error reported in your snapcenter/filer side:
app.log.emerg:
tnadb1: SnapCenter VMware OVA Software 4.2: (0) Info: Backup job [32],
Host Name [ltnadb1], Host OS [Linux], Resource Group [Daily Backup of VMs], Resource Group Size [68], Policy [SMVI_DAILY__2], status [completed successfully], Completion Time [00:01:44]

Looks like the client application that generated this event, is SnapCenter VMware OVA Software 4.2, Host Name [ltnadb1]

Next suggestive action: Even though the backup jobs are not failing, but still it is worth investigating the reason behind 'fatal' eror being flagged. It is certain that it is being flagged from the application i.e tnadb1: SnapCenter VMware OVA Software 4.2.

Could you share the logs with us :

Snapcenter host agent logs
plug-in logs

This will help us determine if it's wrongly reported Or is it a genuine error.

Reference doc:
https://docs.netapp.com/ocsc-42/index.jsp?topic=%2Fcom.netapp.doc.ocsc-ag%2FGUID-3514FA2F-773A-4E73-BA0C-E5515E4F4F68.html&lang=en

How to collect SnapCenter logs
https://kb.netapp.com/app/answers/answer_view/a_id/1030193/loc/en_US

On the side note : It is worth raising a ticket with NetApp. {As far as interoperability is concerned, looks like a supproted configuration}

storageland

Hi,

thank you very much for your assistance so far. Unfortunately I can't post logs from our production environment due to security restrictions. But opening a support case is surely a good idea.

I will keep you up to date with any progress about this case.

Regards, Frank

storageland

Hi,

already got an answer from NetApp support. They confirmed this to be a known bug (bug ID 1258216, Backup EMS messages are getting generated as Emergency instead of Informational).

As a workaround, it is possible to use Unified Manager to disable EMS Subscriptions for a specific event.

Regards, Frank

Ontapforrum

Thanks for getting this confirmed from NetApp. Brilliant!!, now it feels better.

Looks like the BUG info is private, therefore it cannot be searched. There should be Kb.