We use blat to send out our savegroup completions as well as our bootstaps...
From the log details, I would guess your e-mail server is rejecting the message
for some reason:
Oct 29 14:48:19 server: * server:bootstrap Error: Wait a bit (possible
timeout).Message not accepted by server
This could be caused by a timeout on either end, the error does not specify
which ...
Try adding '-ti 90' (I think that's the option, not 100% sure) to your blat
command line to allow it 90 seconds before blat times it out...
If it still rejects the message, ask the mail server admin why ???
-----Original Message-----
From: EMC NetWorker discussion on behalf of Browning, David
Sent: Wed 10/29/2008 4:18 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Bootstrap Notification
Does anyone else use Blat, or something similar to email their bootstrap
notifications? We currently print them, but would love to change this to
email. We are a windows shop. I can do this manually every day via
the MMINFO command, but I would like to automate it via the notification
setup in Networker. We are testing this on 7.2 before trying it on 7.4.
I've tried blat, and it won't send the bootstrap through the networker
notification setup.
I've included the debug results (some key info changed).
If anyone has any ideas, I would love to hear them. TIA.
Command in the bootstrap notification:
blat - -debug -subject "Maple bootstrap" -to dbrown AT lsuhsc DOT edu
debug results:
Oct 29 14:48:19 server: * server: bootstrap level=full, 179 MB 00:01:00
449 files
Oct 29 14:48:19 server: * server:bootstrap Sending stdin.txt to
dbrown AT lsuhsc DOT edu
Oct 29 14:48:19 server: * server:bootstrap Subject:Maple bootstrap
Oct 29 14:48:19 server: * server:bootstrap Login name is
dbrown AT lsuhsc DOT edu
Oct 29 14:48:19 server: * server:bootstrap <<<getline<<< 220
*********.lsuhsc.edu Microsoft ESMTP MAIL Service, Version:
6.0.3790.3959 ready at Wed, 29 Oct 2008 14:47:20 -0500
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap >>>putline>>> EHLO server
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap <<<getline<<<
250-********.lsuhsc.edu Hello [123.123.123.123]
Oct 29 14:48:19 server: * server:bootstrap 250-TURN
Oct 29 14:48:19 server: * server:bootstrap 250-SIZE
Oct 29 14:48:19 server: * server:bootstrap 250-ETRN
Oct 29 14:48:19 server: * server:bootstrap 250-PIPELINING
Oct 29 14:48:19 server: * server:bootstrap 250-DSN
Oct 29 14:48:19 server: * server:bootstrap 250-ENHANCEDSTATUSCODES
Oct 29 14:48:19 server: * server:bootstrap 250-8bitmime
Oct 29 14:48:19 server: * server:bootstrap 250-BINARYMIME
Oct 29 14:48:19 server: * server:bootstrap 250-CHUNKING
Oct 29 14:48:19 server: * server:bootstrap 250-VRFY
Oct 29 14:48:19 server: * server:bootstrap 250-X-EXPS GSSAPI NTLM
Oct 29 14:48:19 server: * server:bootstrap 250-AUTH GSSAPI NTLM
Oct 29 14:48:19 server: * server:bootstrap 250-X-LINK2STATE
Oct 29 14:48:19 server: * server:bootstrap 250-XEXCH50
Oct 29 14:48:19 server: * server:bootstrap 250 OK
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap >>>putline>>> MAIL
From:<dbrown AT lsuhsc DOT edu>
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap <<<getline<<< 250 2.1.0
dbrown AT lsuhsc DOT edu....Sender OK
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap >>>putline>>> RCPT To:
<dbrown AT lsuhsc DOT edu>
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap <<<getline<<< 250 2.1.5
dbrown AT lsuhsc DOT edu
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap >>>putline>>> DATA
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap <<<getline<<< 354 Start mail
input; end with <CRLF>.<CRLF>
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap Error: Wait a bit (possible
timeout).Message not accepted by server
Oct 29 14:48:19 server: * server:bootstrap >>>putline>>> QUIT
Oct 29 14:48:19 server: * server:bootstrap
Oct 29 14:48:19 server: * server:bootstrap Error: Wait a bit (possible
timeout).
Oct 29 14:48:19 server: * server:bootstrap printing bootstrap
information failed (reproduced below).
Oct 29 14:48:19 server: * server:bootstrap
David M. Browning Jr.
IT Project Coordinator Enterprise Backups and Help Desk
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Werth, Dave
Sent: Monday, October 06, 2008 11:35 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Bootstrap Notification
If you're already receiving the bootstrap in one mail box it should
simply be a matter of adding another e-mail address to the mechanism you
use to send the message. Our bootstrap notification command (sanitized
for anonymity) is:
blat - -s "Networker Bootstrap Notification" -t email1,email2,...
One thing I have done is made arrangements with our off-site storage
provider to include them on the Bootstrap notification list so not only
do they have the tapes we need for DR but they have the bootstrap
information as well.
Dave Werth
Garmin AT, Inc.
Salem, Oregon
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of wanhyo
Sent: Monday, October 06, 2008 5:25 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Bootstrap Notification
Hello All,
I get a bootstrap notification daily. This comes to my local mailbox.
In the event of a disaster, I would not have the bootstrap details. Is
there a way to get NetWorker to send the bootstrap info to 2 e-mail
addresses?
Does it write to a file on nsr folder?
I am using NetWorker 7.3.3 on Windows Server 2003.
Thanks,
Wanhyo :?
+----------------------------------------------------------------------
|This was sent by nramcharitan AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
