如果 nbmail.cmd 存在的话，NetBackup 会传递三个参数给这个 CMD 文件：

• %1 is the recipient's address
• %2 is the subject line
• %3 is the message file name

NetBackup 推荐使用 BLAT 这个免费工具发送邮件通知。这个工具的安装很简单，将 blat.exe 放在 system32 目录下即可。设定方法：
blat -install <smtp server address> <sender's address>

完整语法如下：
-install <server addr> <sender's addr> [<try n times> [<port> [<profile> [<username> [<password>]]]]]

nbmail.com 调用 BLAT 的语句是：

@blat %3 -s %2 -t %1 -i NetBackup -server WARTHOG -q

其中：

1. -i 参数后面跟的是发送者的名称，对应邮件里面的 From。如果在安装 blat 的时候已经设定了发送者，这个参数此处可以不配置。
2. -server 参数后面跟的是 smtp server 的名称。如果不配置这个选项，默认使用 blat 安装时候的配置。
3. -q 表示 Tell Blat to be quite when storing install settings in the registry.

Attention!!!

总结：nbmail.com 调用 BLAT 的语句可以简写为：
@blat %3 -s %2 -t %1 -i
其余参数可以采用 blat -install 时候的设置。

NetBackup 和邮件通知相关的批处理脚本（部分）

For example,

• Original Blat command from the nbmail.cmd script:

  	@blat %3 -s %2 -t %1 -i NetBackup -q
  	

• Modified Blat command used for troubleshooting:

  	@blat %3 -s %2 -t %1 -i NetBackup >C:\nbmail_test.txt
  	

This change will output exactly what the Blat utility is sending to the mail server and should return any errors that the server returns.

Below is an example of the output:

Sending C:\WINNT\TEMP\nb_AC6.tmp to email_address@veritas.com
Subject:NetBkup on test client - 150 started
Login name is user.name@veritas.com

1. BLAT is commented out in the nbmail.cmd script — remove the ‘@rem’ from in front of the BLAT command.
2. No email address configured or email address incorrectly configured on Universal Settings tab.
3. The BLAT line in nbmail.cmd is not correctly configured; syntax has changed in the later versions — check the readme for your version of BLAT.
4. BLAT is not on the path, and no path was specified in nbmail.cmd — place the blat.exe program in a directory on your path, or add the path before BLAT in the script.
5. BLAT version is greater than 1.84, and no profile was created — see the BLAT readme for details on profiles.
6. Mail account did not exist on email server — create the account.
7. Mail server required authentication for Simple Mail Transfer Protocol (SMTP), and the account used for VERITAS NetBackup ™ client process is not authorized — change user account for NetBackup Client Service (default is local system, which may not have permission to send mail).
8. BLAT sometimes needs the -ti <n> timeout parameter if there are delays in the system — <n> is in seconds.
9. Command line extensions are not enabled — The registry key HKEY_CURRENT_USER\Software\Microsoft\Command Processor\EnableExtensions should be set to 0×1.
10. BLAT binary is corrupt or incompatible with email system — download a newer version.

如何查看 NetBackup 程序调用了 nbmail.cmd 呢？

答案是通过setting up the BPCD log。具体步骤如下：

1. Select Client sends mail on Universal Settings tab (properties on the master server). The option Server sends mail does not log anything in the BPCD log, so even if you require this option, test it with the Client setting first.
2. Make sure that an email address is configured on the Universal Settings tab.
3. Make sure the call to BLAT is uncommented in the nbmail.cmd script.
4. Make sure that a directory called BPCD exists in NetBackup\Logs on the master server.
5. a. For NetBackup 3.4 only: Launch the NetBackup client, click Actions | Configure and go to the Troubleshooting tab. Enter 2 for General and 9 for Verbose.
   b. For NetBackup 4.5 only – Launch the Backup, Archive and Restore program, click File | NetBackup Client Properties and go to the Troubleshooting tab. Enter 2 for General and 5 for Verbose.

6. Re-start the NetBackup Client Service to make sure these settings take effect.
7. Run a backup of a directory on the master server.
8. The BPCD log should contain something similar to the following:
   07:34:04.128 [3864.4052] <2> bpcd main: BPCD_SEND_MAIL_RQST
   07:34:04.128 [3864.4052] <2> bpcd main: mailaddr = joe.bloggs@veritas.com
   07:34:04.128 [3864.4052] <2> bpcd main: subject = Backup on MYMASTER – 0 started
   07:34:04.128 [3864.4052] <2> bpcd main: message = Backup on client MYMASTER by root succeeded.

   File list
   ———
   C:\WINNT\system32\drivers\etc

   07:34:04.128 [3864.4052] <2> sendViaScript: attempting to send mail
   07:34:04.198 [3864.4052] <2> bpcd main: BPCD_DISCONNECT_RQST

If you don’t see this in the log, then nbmail is not being called, and you have a configuration problem within NetBackup itself. If you see the entries in the log, but receive no email, then verify whether the email address is correct and valid. If the email address is correct, then the problem lies either with the nbmail.cmd script itself, or with BLAT.

Troubleshooting BLAT:

The later versions of BLAT (from version 1.82 onwards) use profiles. The idea is that you configure your user or server and any other settings for the mail system in a profile and then just specify this when you use the command. The following technote describes this: http://support.veritas.com/docs/244258

So an appropriate change in nbmail.cmd would be to change the BLAT line as follows:

@blat %3 -s %2 -t %1 -p NetBackup -q

where NetBackup is a profile you created.

When testing BLAT, you need to remove the -q switch and pipe the output to a file; you could replace the above line with:

@echo:Testing %1 ,%2 ,%3 >>C:\Testing.txt
<blat> %3 -s %2 -t %1 -p NetBackup>>c:\Testing.txt

*** Note the emission of -q switch ***

When you test nbmail.cmd from the command line, it is helpful to use the same account that NetBackup client service is using, this will help highlight any account permission issues that may stop the process from working.

具体语法如下

Blat v2.5.0 w/GSS encryption (build : Sep 14 2005 22:46:29)

Win32 console utility to send mail via SMTP or post to usenet via NNTP
by P.Mendes,M.Neal,G.Vollant,T.Charron,T.Musson,H.Pesonen,A.Donchey,C.Hyde

http://www.blat.net

syntax:
  Blat <filename> -to <recipient> [optional switches (see below)]
  Blat -install <server addr> <sender's addr> [<try>[<port>[<profile>]]] [-q]
  Blat -profile [-delete | "<default>"] [profile1] [profileN] [-q]
  Blat -h

-------------------------------- Installation ---------------------------------
-install[SMTP|NNTP|POP3] <server addr> <sender's email addr> [<try n times>
                [<port> [<profile> [<username> [<password>]]]]]
                : set server, sender, number of tries and port for profile
                  (<try n times> and <port> may be replaced by '-')
                  port defaults are SMTP=25, NNTP=119, POP3=110
                  default profile can be specified with a '-'
                  username and/or password may be stored to the registry
                  order of options is specific
                  use -installNNTP for storing NNTP information
                  use -installPOP3 for storing POP3 information
                      (sender and try are ignored, use '-' in place of these)

--------------------------------- The Basics ----------------------------------
<filename>      : file with the message body to be sent
                  if your message body is on the command line, use a hyphen (-)
                  as your first argument, and -body followed by your message
                  if your message will come from the console/keyboard, use the
                  hyphen as your first argument, but do not use -body option.
-of <file>      : text file containing more options (also -optionfile)
-to <recipient> : recipient list (also -t) (comma separated)
-tf <file>      : recipient list filename
-cc <recipient> : carbon copy recipient list (also -c) (comma separated)
-cf <file>      : cc recipient list filename
-bcc <recipient>: blind carbon copy recipient list (also -b)
                  (comma separated)
-bf <file>      : bcc recipient list filename
-maxNames <x>   : send to groups of <x> number of recipients
-ur             : set To: header to Undisclosed Recipients if not using the
                  -to and -cc options
-subject <subj> : subject line, surround with quotes to include spaces(also -s)
-ss             : suppress subject line if not defined
-sf <file>      : file containing subject line
-body <text>    : message body, surround with quotes to include spaces
-sig <file>     : text file containing your email signature
-tag <file>     : text file containing taglines, to be randomly chosen
-ps <file>      : final message text, possibly for unsubscribe instructions

----------------------------- Registry overrides ------------------------------
-p <profile>    : send with server, user, and port defined in <profile>
                : use username and password if defined in <profile>
-profile        : list all profiles in the Registry
-server <addr>  : specify SMTP server to be used (optionally, addr:port)
-serverSMTP <addr>
                : same as -server
-serverNNTP <addr>
                : specify NNTP server to be used (optionally, addr:port)
-serverPOP3 <addr>
                : specify POP3 server to be used (optionally, addr:port)
                  when POP3 access is required before sending email
-f <sender>     : override the default sender address (must be known to server)
-i <addr>       : a 'From:' address, not necessarily known to the server
-port <port>    : port to be used on the SMTP server, defaults to SMTP (25)
-portSMTP <port>: same as -port
-portNNTP <port>: port to be used on the NNTP server, defaults to NNTP (119)
-portPOP3 <port>: port to be used on the POP3 server, defaults to POP3 (110)
-u <username>   : username for AUTH LOGIN (use with -pw)
-pw <password>  : password for AUTH LOGIN (use with -u)
-pu <username>  : username for POP3 LOGIN (use with -ppw)
-ppw <password> : password for POP3 LOGIN (use with -pu)

---------------------- Miscellaneous RFC header switches ----------------------
-organization <organization>
                : Organization field (also -o and -org)
-ua             : include User-Agent header line instead of X-Mailer
-x <X-Header: detail>
                : custom 'X-' header.  eg: -x "X-INFO: Blat is Great!"
-noh            : prevent X-Mailer/User-Agent header from showing Blat homepage
-noh2           : prevent X-Mailer header entirely
-d              : request disposition notification
-r              : request return receipt
-charset <cs>   : user defined charset.  The default is ISO-8859-1
-a1 <header>    : add custom header line at the end of the regular headers
-a2 <header>    : same as -a1, for a second custom header line
-dsn <nsfd>     : use Delivery Status Notifications (RFC 3461)
                  n = never, s = successful, f = failure, d = delayed
                  can be used together, however N takes precedence
-hdrencb        : use base64 for encoding headers, if necessary
-hdrencq        : use quoted-printable for encoding headers, if necessary
-priority <pr>  : set message priority 0 for low, 1 for high

----------------------- Attachment and encoding options -----------------------
-attach <file>  : attach binary file(s) to message (filenames comma separated)
-attacht <file> : attach text file(s) to message (filenames comma separated)
-attachi <file> : attach text file(s) as INLINE (filenames comma separated)
-embed <file>   : embed file(s) in HTML.  Object tag in HTML must specify
                  content-id using cid: tag.  eg: <img src="cid:image.jpg">
-af <file>      : file containing list of binary file(s) to attach (comma
                  separated)
-atf <file>     : file containing list of text file(s) to attach (comma
                  separated)
-aef <file>     : file containing list of embed file(s) to attach (comma
                  separated)
-base64         : send binary files using base64 (binary MIME)
-uuencode       : send binary files UUEncoded
-enriched       : send an enriched text message (Content-Type=text/enriched)
-unicode        : message body is in 16- or 32-bit Unicode format
-html           : send an HTML message (Content-Type=text/html)
-alttext <text> : plain text for use as alternate text
-alttextf <file>: plain text file for use as alternate text
-mime           : MIME Quoted-Printable Content-Transfer-Encoding
-8bitmime       : ask for 8bit data support when sending MIME
-multipart <size>
                : send multipart messages, breaking attachments on <size>
                  KB boundaries, where <size> is per 1000 bytes
-nomps                : do not allow multipart messages

---------------------------- NNTP specific options ----------------------------
-groups <usenet groups>
                : list of newsgroups (comma separated)

-------------------------------- Other options --------------------------------
-h              : displays this help (also -?, /?, -help or /help)
-q              : suppresses all output to the screen
-debug          : echoes server communications to a log file or screen
                  (overrides -q if echoes to the screen)
-log <file>     : log everything but usage to <file>
-timestamp      : when -log is used, a timestamp is added to each log line
-ti <n>         : set timeout to 'n' seconds.  Blat will wait 'n' seconds for
                  server responses
-try <n times>  : how many times blat should try to send (1 to 'INFINITE')
-binary         : do not convert ASCII | (pipe, 0x7c) to CrLf in the message
                  body
-hostname <hst> : select the hostname used to send the message via SMTP
                  this is typically your local machine name
-raw            : do not add CR/LF after headers
-delay <x>      : wait x seconds between messages being sent when used with
                  -maxnames or -multipart
-comment <char> : use this character to mark the start of commments in
                  options files and recipient list files.  The default is ;
-superdebug     : hex/ascii dump the data between Blat and the server
-superdebugT    : ascii dump the data between Blat and the server
-------------------------------------------------------------------------------

Note that if the '-i' option is used, <sender> is included in 'Reply-to:'
and 'Sender:' fields in the header of the message.

Optionally, the following options can be used instead of the -f and -i
options:

-mailfrom <addr>   The RFC 821 MAIL From: statement
-from <addr>       The RFC 822 From: statement
-replyto <addr>    The RFC 822 Reply-To: statement
-returnpath <addr> The RFC 822 Return-Path: statement
-sender <addr>     The RFC 822 Sender: statement

For backward consistency, the -f and -i options have precedence over these
RFC 822 defined options.  If both -f and -i options are omitted then the
RFC 821 MAIL FROM statement will be defaulted to use the installation-defined
default sender address.

BLAT is a open source utility and the most recent version of BLAT can be downloaded from this site: http://sourceforge.net/projects/blat/

I. Installing and Configuring the BLAT executable

1. Download the .ZIP file from the download page specified above
2. Extract the files to their own folder.
   Note: Most of the files in this .ZIP file are informational and is source code for developmental purposes.
3. Copy the blat.exe file to the \WINNT\System32 directory in Windows
4. From a command prompt, run the following command (Note: This will be the primary account that will send the emails from the specified server):

   % blat -install <server addr> <sender's addr>
   	

   Note: “<server addr>” is the hostname or IP address of the email server that will send the email notifications.
   “<sender’s addr>” is the account that will be the primary sender of the email notifications.
   Example:

   % blat -install emailserver.company.com useraccount@company.com
   	

5. Test the installation of blat by creating a text file C:\testfile.txt with a message and emailing it to the NetBackup administrator.

   % blat C:\testfile.txt -s test_subject -to useraccount@company.com
   	

   If blat is working correctly, the NetBackup administrator should receive the contents of the C:\testfile.txt file.

II. Configuring the nbmail.cmd script

1. Open nbmail.cmd using notepad.exe or some other text editor. The file can be found on a NetBackup Server/Client install for Windows at <install_path>\VERITAS\NetBackup\bin.
   Please make a backup copy of this script before modifying it.
   Note: When using Notepad to modify a script do not use the Word Wrap option. If this option is enabled, then it will need to be unchecked. Using this option can result in extra line feeds being added to the script which will render it non-functional.

2. Most of the lines in the nbmail.cmd file are informational. The following line(s) are what need to be adjusted:
   For NetBackup 4.5 and 5.x systems find the line:

   @rem @blat %3 -s %2 -t %1 -i NetBackup -server WARTHOG -q
   

   For NetBackup 6.0 systems find the section:

   @REM @IF "%~4"=="" (
   @REM blat %3 -s %2 -t %1 -i NetBackup -server WARTHOG -q
   @REM ) ELSE (
   @REM blat %3 -s %2 -t %1 -i NetBackup -server WARTHOG -q -attach %4
   @REM )
   

3. Remove “@rem” from the beginning of each line. This will activate the sections needed for blat to run.
4. Replace “WARTHOG” with the name of the email server. An example of how this line should now appear is:
   Example on NetBackup 4.5 and 5.x systems:

   @blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q
   

   Example on NetBackup 6.0 systems:

   @IF "%~4"=="" (
   blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q
   ) ELSE (
   blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -attach %4
   )
   

5. Save the nbmail.cmd file
6. Example of an email sent by NetBackup using blat:

   Backup on client  by root was partially successful.
   File list
   ---------
   C:\Documents and Settings
   

   Options explained:

   • %3 is the file that BLAT will send in the body of the email. This is generated by one of the other scripts, backup_notification.cmd for example.
   • -s is the subject line of the email
   • %2 is the contents of the subject line. This is generated by another script that calls on blat, backup_notification.cmd, for example.
   • -t is who will receive the email.
   • %1 – is the email address. This is by default the contents of the Email Address for the administrator of this NetBackup Client field.
   • -i is the “From” portion of the email. This is not necessarily known to the email server. In this case it will be “From NetBackup.”
   • -server is the name of the SMTP server to use.
   • -q will suppress all output to the screen.

III. Configure NetBackup to use email notification

To allow a master server to send emails for all failed client backups that end with a non-zero status, do the following:

1. Open the NetBackup Administration Console
2. Open the Host Properties for the master server and go to the Global Attributes tab
3. At the bottom of this page, enter the email address for the NetBackup administrator in the field called Administrator e-mail address: (separate multiple entries with commas)

To allow a specific client to send emails for all successful and failed jobs, do the following:

1. Open the NetBackup Administration Console
2. Open the Host Properties for the Client and go to the Universal Settings tab
3. Under the Administrator section of this page, enter the email address for the NetBackup administrator in the field called Client Administrator’s e-mail (separate multiple entries with commas)

NetBackup should send email notifications at this point. To get more information sent to the administrator configure some of the <install_path>\VERITAS\NetBackup\bin\*.cmd files. This would result in additional information for the administrator.

IV. Additional ways to use BLAT and nbmail.cmd

Sending to multiple users can be done in two ways: by creating an administrative group SMTP account on an email server and configuring NetBackup and nbmail.cmd to use that SMTP address, or by configuring the nbmail.cmd file to send to multiple users.

Providing more email address for BLAT can be done by adding additional email addresses after the %1 in the nbmail.cmd file. Here is an example of the syntax required:

Example on NetBackup 4.5 and 5.x systems:

@blat %3 -s %2 -t %1,name1@acme.com,name2@acme.com,name3@acme.com -i NetBackup -server emailserver.company.com -q

Example on NetBackup 6.0 systems:

@IF "%~4"=="" (
blat %3 -s %2 -t %1,name1@acme.com,name2@acme.com,name3@acme.com -i NetBackup -server emailserver.company.com -q
) ELSE (
blat %3 -s %2 -t %1,name1@acme.com,name2@acme.com,name3@acme.com -i NetBackup -server emailserver.company.com -q -attach %4
)

Configured this way, four emails will be sent out. It is important to separate the email addresses with commas (,) and no spaces in between.

V. Troubleshooting BLAT

1. It may be necessary to do some troubleshooting of BLAT. If BLAT is run from a straight command line, and it has an error, it will produce a message in the command line results. To make a “log” file for BLAT, make an entry at the end of the nbmail.cmd “@blat” line similar to this:
   Example on NetBackup 4.5 and 5.x systems:

   @blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q >>"C:\program files\veritas\netbackup\logs\blat.out.txt"
   	

   Example on NetBackup 6.0 systems:

   @IF "%~4"=="" (
   blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q >>"C:\program files\veritas\netbackup\logs\blat.out.txt"
   ) ELSE (
   blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -attach %4 >>"C:\program files\veritas\netbackup\logs\blat.out.txt"
   )
   	

   This will create a .txt file in the specified directory and will append to the bottom of that file. If there is an error message from BLAT it will show in the specified file.

2. There have been instances where email notification is working, but Vault will not send reports correctly. To correct this, a modification to the “blat” line in the nbmail.cmd file is necessary. If you are experiencing this, make the following modification to the nbmail.cmd file:
   Example on NetBackup 4.5 and 5.x systems:

   @blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -mime
   

   Example on NetBackup 6.0 systems:

   @IF "%~4"=="" (
   blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -mime
   ) ELSE (
   blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -attach %4 -mime
   )
   

3. There have been instances where email notification is configured correctly, BLAT is configured correctly, but emails are not received. Try making the following modification to the nbmail.cmd file:
   Example on NetBackup 4.5 and 5.x systems:

   @blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -enriched
   	

   Example on NetBackup 6.0 systems:

   @IF "%~4"=="" (
   blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -enriched
   ) ELSE (
   blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -attach %4 -enriched
   )
   	

Related Documents:

248387: Will VERITAS NetBackup ™ 4.5 work with command line Simple Mail Transfer Protocol tools other than BLAT?

256043: DOCUMENTATION: The nbmail.cmd mail notification — a mini workshop with troubleshooting tips and details of how to get it working

268192: VERITAS NetBackup ™ 5.1 System Administrator’s Guide, Volume I for Windows

268610: DOCUMENTATION: How to configure email notification and the different methods to email backup exit statuses from a UNIX master in NetBackup