%MSG in SC4.1.0c vs SC3.6.0

KOUBIC8811 — Thu, 05 Jun 2025 05:48:26 GMT

Hi guys,

do you know somebody why was changed output from variable %MSG? It was better and more clear in SC3.6 than in 4.1c as you can see below. Now I got message that snapshot have been done properly but I cannot see for which config file and which type.

This was really better output in SC3.6. We are using it for monitoring and quickly summary what was done OK/NOT OK. Is some option to have the same output from %MSG in SC4.1c as is in SC3.6?

########## Snap Creator Community Release 4.1.0c finished successfully ##########

[2013-11-29 14:59:14,502] INFO: INFO: Snap Creator finished successfully ( Action: backup )

[2013-11-29 14:59:14,750] INFO: Sending Trap message to external system /dynamiclandscape/scripts/sctrap.sh "INFO: Snap Creator finished successfully ( Action: backup )"

[2013-11-29 14:59:14,961] INFO: stdout:

########## NetApp Snap Creator Framework 3.6.0 finished successfully ##########

[Wed Oct 2 16:07:14 2013] INFO: INFO: Snap Creator finished successfully ( Action: snap )

[Wed Oct 2 16:07:14 2013] INFO: Sending Alert to external system [/dynamiclandscape/scripts/sctrap.sh "SNAPCREATOR INFO: Snap Creator finished successfully ( Action: snap ) (Config: sb1 Name: sc_ora_onl Policy: hourly)"]

Additional info:

when job failed then output is:

########## Snap Creator Community Release 4.1.0c failed ##########

[Fri Nov 29 16:04:01 2013] INFO: Pre Exit commands are not defined. Skipping !

[Fri Nov 29 16:04:01 2013] INFO: Sending Trap message to external system /dynamiclandscape/scripts/sctrap.sh "SNAPCREATOR Unexpected Error (Config: sb1 Name: sc_ora_onl Policy: daily)"

[Fri Nov 29 16:04:01 2013] INFO: stdout:

[Fri Nov 29 16:04:01 2013] ERROR: Snap Creator Community Release 4.1.0c CLI action backup failed

There are information about "Config, Name and policy". It´s strange..

Thank you

Jakub

Re: %MSG in SC4.1.0c vs SC3.6.0

ktenzer — Fri, 29 Nov 2013 14:17:01 GMT

Hi Jakub,

No we have no option to make it just like 3.6 but we will open a defect and make improvements. Thanks for bringing this up

Keith

topic %MSG in SC4.1.0c vs SC3.6.0 in Data Protection

%MSG in SC4.1.0c vs SC3.6.0

Re: %MSG in SC4.1.0c vs SC3.6.0