Hi HabibG2,

Then, why the original bootstrap is ok?

I think, the field 'action' is ok, because, other notifications are sent by mail.

Thanks.

Inma Bernabe.

I think you are missing the recepient name see below;

an example would be...

smtpmail -s "boostrap information" -h x.x.x.x account1@domain.com -f account2@domain.com

where x.x.x.x is the IP address of your mail server
account1 is the address you are sending to and
account 2 is the email address it will send from

I am not sure.
Check the sender name in you original Notif, it will probable have come from the administrator or backup administrator and try to add the same sender in your statement.

Or try the same statement in your Client config and test.

Check you statement word for word!!!

Hi HabibG2,

My customer made a new notification, which, did not send by mail, then, he copy 'action' field of new notifiaction, and paste in original notification bootstrap.

Why is original notification bootstrap ok when in new notification is not ok?

Too, say that all values are equal.

Do you know if this a issue NetWorker 7.3.3?

Thanks very much.

Inma Bernabe.

I am not aware of any such issue reported. You can always create a case with EMC support.

Did you compare the event and priority fields of the new notification you created against the original one? The problem may not be the action field, but the notification may not be triggered as you expected.

Hi Daniel,

Yes, the priority, events and action are like original notification.

Now, I am waiting for a request of my customer. He has to launch the notification with the value:

smtpmail -s "boostrap information" -h ip_mailserver -f NetWorker fdelo@jcm.es

I will say something when my customer inform to me.

Thanks.

Inma Bernabe.

Hi HabibG2,

I have been looking for by the KnownleadgeBase, and I saw the next:



"By design, the bootstrap notification is not based on the event "savegroup"

and priority "critical", it's based on the name, "Bootstrap".


Since each notification name needs to be unique, one cannot even create multiple

true "Bootstrap" notifications.


Why bootstrap notification is designed with this limitation?

(1) If this behavior were changed to be based on event and priority,

then the bootstrap would always be send to the "Log default" notification

as well, which it was not designed to do so.


(2) The bootstrap notification is not processed via the usual notification code; if it were, the "Printer" attribute of the savegrp resource would stop functioning. "

It cannot to be two notifications bootstrap. It is not supported.

Thanks very much.

Inma Bernabe

I was not aware of this fact as I never had to do it. However if you still want both notification my initial suggestion should work.

I use mminfo to send my "Bootstrap" information to another server just in case my server goes down, see example below;

mminfo -B -s -t "7 days ago" >> \\ \folder\Bootstraps.txt