Emailing logs - Veritas Net Backup

This is a discussion on Emailing logs - Veritas Net Backup ; Can anyone help me get Netbackup to email me to logs (both failure and success) each night after backup. My environment is 3 Win2k servers one with Exchange 2K on it (which isn't working either). I followed the manual and ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Emailing logs

  1. Emailing logs

    Can anyone help me get Netbackup to email me to logs (both failure and
    success) each night after backup. My environment is 3 Win2k servers one
    with Exchange 2K on it (which isn't working either). I followed the manual
    and downloaded BLAT, I can send messages from the command line using BLAT
    but Netbackup won't.

    Thanks in advance



  2. Re: Emailing logs

    Make sure you've tweaked your nbmail.cmd file appropriately and that
    blat.exe is located somewhere in your path (all on your client). You might
    even dink with a batch file similar to nbmail.cmd and run it manually to
    make sure blat is being called properly. Oh, yeah, also make sure your
    client has a goodies folder with listpaths.exe in it, since that's what
    nbmail.cmd uses. As I recall, this isn't installed by default.

    Post again if you continue to have problems.

    Kathy

    "Kevin Campbell" wrote in message
    news:3b86701c@hronntp01....
    > Can anyone help me get Netbackup to email me to logs (both failure and
    > success) each night after backup. My environment is 3 Win2k servers one
    > with Exchange 2K on it (which isn't working either). I followed the

    manual
    > and downloaded BLAT, I can send messages from the command line using BLAT
    > but Netbackup won't.
    >
    > Thanks in advance
    >
    >




  3. Re: Emailing logs

    BLAT was already in the working path, and there was already a goodies
    folder. What do you mean when you say "dink with a batch file similar to
    nbmail.cmd"? From a command prompt I can use BLAT and email myself an
    document.


    "KLeeman" wrote in message
    news:3b8676bc$1@hronntp01....
    > Make sure you've tweaked your nbmail.cmd file appropriately and that
    > blat.exe is located somewhere in your path (all on your client). You

    might
    > even dink with a batch file similar to nbmail.cmd and run it manually to
    > make sure blat is being called properly. Oh, yeah, also make sure your
    > client has a goodies folder with listpaths.exe in it, since that's what
    > nbmail.cmd uses. As I recall, this isn't installed by default.
    >
    > Post again if you continue to have problems.
    >
    > Kathy
    >
    > "Kevin Campbell" wrote in message
    > news:3b86701c@hronntp01....
    > > Can anyone help me get Netbackup to email me to logs (both failure and
    > > success) each night after backup. My environment is 3 Win2k servers

    one
    > > with Exchange 2K on it (which isn't working either). I followed the

    > manual
    > > and downloaded BLAT, I can send messages from the command line using

    BLAT
    > > but Netbackup won't.
    > >
    > > Thanks in advance
    > >
    > >

    >
    >




  4. Re: Emailing logs

    Try running nbmail.cmd manually and pass the proper number of paramaters to
    it. So, in my case "nbmail.cmd test1 test2 test3". If that doesn't work,
    take the -q off the end of the blat line (if you have one so you can see
    where it's dying). As long as blat works through that script, move on to
    your bpend_notify script.

    This is probably the one where more "dinking" comes into play. You can try
    running that manually by passing the proper number of paramaters to it also
    (six altogether). If it doesn't work, make a copy of it and edit things
    until you see what's breaking it (e.g., take the "@"s off the beginning of
    the run lines so you can see what it's doing, don't let listpaths figure out
    your locations...fill them in yourself, etc.).

    Also, another obvious thing I should have said was to make sure your
    bpend_notify script name contains the proper class name. A class named
    "test" would need a script name of bpend_notify.test.bat, and this must
    reside in the "bin" directory on the client.

    Let me know what you find out!

    "Kevin Campbell" wrote in message
    news:3b868f9c$1@hronntp01....
    > BLAT was already in the working path, and there was already a goodies
    > folder. What do you mean when you say "dink with a batch file similar to
    > nbmail.cmd"? From a command prompt I can use BLAT and email myself an
    > document.
    >
    >
    > "KLeeman" wrote in message
    > news:3b8676bc$1@hronntp01....
    > > Make sure you've tweaked your nbmail.cmd file appropriately and that
    > > blat.exe is located somewhere in your path (all on your client). You

    > might
    > > even dink with a batch file similar to nbmail.cmd and run it manually to
    > > make sure blat is being called properly. Oh, yeah, also make sure your
    > > client has a goodies folder with listpaths.exe in it, since that's what
    > > nbmail.cmd uses. As I recall, this isn't installed by default.
    > >
    > > Post again if you continue to have problems.
    > >
    > > Kathy
    > >
    > > "Kevin Campbell" wrote in message
    > > news:3b86701c@hronntp01....
    > > > Can anyone help me get Netbackup to email me to logs (both failure and
    > > > success) each night after backup. My environment is 3 Win2k servers

    > one
    > > > with Exchange 2K on it (which isn't working either). I followed the

    > > manual
    > > > and downloaded BLAT, I can send messages from the command line using

    > BLAT
    > > > but Netbackup won't.
    > > >
    > > > Thanks in advance
    > > >
    > > >

    > >
    > >

    >
    >




  5. Re: Emailing logs

    Well the NBmail.cmd was not the problem. It looks like a bpend_notify
    script problem, or let me say a lack of one. I made a copy of it and
    renamed the copy bpend_notify.bat and placed on the master server. I assume
    that is how you create one. From what I read in the manual if I don't
    specify a class and put a .bat extenstion on it it will work for all
    classes.

    Kevin

    "KLeeman" wrote in message news:3b86ae88@hronntp01....
    > Try running nbmail.cmd manually and pass the proper number of paramaters

    to
    > it. So, in my case "nbmail.cmd test1 test2 test3". If that doesn't work,
    > take the -q off the end of the blat line (if you have one so you can see
    > where it's dying). As long as blat works through that script, move on to
    > your bpend_notify script.
    >
    > This is probably the one where more "dinking" comes into play. You can

    try
    > running that manually by passing the proper number of paramaters to it

    also
    > (six altogether). If it doesn't work, make a copy of it and edit things
    > until you see what's breaking it (e.g., take the "@"s off the beginning of
    > the run lines so you can see what it's doing, don't let listpaths figure

    out
    > your locations...fill them in yourself, etc.).
    >
    > Also, another obvious thing I should have said was to make sure your
    > bpend_notify script name contains the proper class name. A class named
    > "test" would need a script name of bpend_notify.test.bat, and this must
    > reside in the "bin" directory on the client.
    >
    > Let me know what you find out!
    >





+ Reply to Thread