Trivial problems cause job to end with ERROR status - Veritas Backup Exec

This is a discussion on Trivial problems cause job to end with ERROR status - Veritas Backup Exec ; Backup jobs are constantly ending with a status of "error". This is becoming quite annoying. There really aren't any errors just some open files which were skipped during the backup. I understand the rationale that "you told us to backup ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Trivial problems cause job to end with ERROR status

  1. Trivial problems cause job to end with ERROR status


    Backup jobs are constantly ending with a status of "error". This is becoming
    quite annoying. There really aren't any errors just some open files which
    were skipped during the backup. I understand the rationale that "you told
    us to backup a file but we couldn't do it so it's an error." However, there
    should be a way to ignore trivial ones like this. The help file also says
    that an error will have the 5 carats (^^^^^) but the log file for this job
    does not have the carats anywhere yet it still ends in a status of error.


    Is there a setting to modify this behavior?

    Please CC my email address as I don't get to this newsgroup very often.

    Thanks in advance.

  2. Re: Trivial problems cause job to end with ERROR status


    Here's an update on the problem below. I've discovered that BE really doesn't
    end in error for skipped files. The problem is the message "Unable to initialize
    remote agent..." The target server is a win2k server. The agent is running.
    I put it in debug mode and here's what it says:

    6a8 5/18/2001 9:20:25: Running... 'Q' to stop
    a78 5/18/2001 9:22:48: Client thread starting
    a78 5/18/2001 9:22:48: FS_InitFileSys
    a78 5/18/2001 9:22:48: loaded bedsnt5.dll
    a78 5/18/2001 9:22:48: loaded bedsnote.dll
    a78 5/18/2001 9:22:48: Client thread terminating
    a78 5/18/2001 9:23:09: Client thread starting
    a78 5/18/2001 9:23:09: Client thread terminating
    a78 5/18/2001 9:27:55: Client thread starting
    a78 5/18/2001 9:27:55: Client thread terminating
    a78 5/18/2001 9:28:10: Client thread starting
    a78 5/18/2001 9:28:10: Client thread terminating
    a78 5/18/2001 9:36:16: Client thread starting
    a78 5/18/2001 9:36:16: Client thread terminating
    a78 5/18/2001 9:36:29: Client thread starting
    a78 5/18/2001 9:36:29: Client thread terminating
    a78 5/18/2001 9:41:15: Client thread starting
    a78 5/18/2001 9:41:15: Client thread terminating
    a78 5/18/2001 9:41:23: Client thread starting
    a78 5/18/2001 9:41:24: Client thread terminating

    As you can see, I tried several jobs. It looks like the BE server is connecting
    as the client starts a thread but it terminates right away.

    I looked in your KB and it mentions a name resolution problem. I added a
    LMHOSTS file to the BE server and made sure that "use lmhosts" is checked
    for the network interface - still same result.

    What else can I try?





    "Alex" wrote:
    >
    >Backup jobs are constantly ending with a status of "error". This is becoming
    >quite annoying. There really aren't any errors just some open files which
    >were skipped during the backup. I understand the rationale that "you told
    >us to backup a file but we couldn't do it so it's an error." However, there
    >should be a way to ignore trivial ones like this. The help file also says
    >that an error will have the 5 carats (^^^^^) but the log file for this job
    >does not have the carats anywhere yet it still ends in a status of error.
    >
    >
    >Is there a setting to modify this behavior?
    >
    >Please CC my email address as I don't get to this newsgroup very often.
    >
    >Thanks in advance.



+ Reply to Thread