Forum Discussion

Ken_Chan1's avatar
Ken_Chan1
Level 3
5 years ago

Backup failed: (28) failed trying to fork a process

Hi,

I have backup problem recently and shown (28) failed trying to fork a process.

The backup size is around 13TB, backup type NDMP, storage DD4200.

It's not failed every backup, can anyone advise what is the problem?

Many thanks.

Regards,

Ken

  • Ken_Chan1 

    I cannot find any 'known issues' with status 28 for NDMP backups.

    This means that something in this environment is causing it.

    Please give us all relevant details, such as NDMP filer and OS version, backup policy details,
    all text in Job Details of failed job, ndmpagent log on the ndmpagent log on the ndmp media server. 
    These logs on the media server may also be helpful: bpbrm and bptm. 
    These log folders do not exist by default - please create them if they do not exist. 

    Please copy logs to process name, e.g. ndmpagent.txt before uploading here. 

    • Ken_Chan1's avatar
      Ken_Chan1
      Level 3

      Hi Marianne,

      Which logging level need to set for those logs ? (ndmpagent, BMTM and BPBRM)

      • Marianne's avatar
        Marianne
        Level 6

        ndmpagent is a unified log and exist by default. 
        This log should be the most useful one. I cannot remember what the default logging level is for unified logs, but for initial troubleshooting, the default should be fine. I believe to only ever increase unified logging level when requested by Veritas Support. 

        For bptm and bpbrm, level 3 usually gives sufficient info.