#3560 Issue closed: bprestore can return a value higher than 1 and be successful

Labels: bug, waiting for info, fixed / solved / done, ready-to-close?

bwelterl opened issue at 2026-02-03 10:51:

ReaR version

2.9

Describe the ReaR bug in detail

Hello,

The return code of bprestore in restore/NBU/default/400_restore_with_nbu.sh can higher than 1 and restore is successful.

LogPrint "RUN: /usr/openv/netbackup/bin/bprestore $bprestore_args"
LogPrint "Restore progress: see $backup_restore_log_file"
LANG=C /usr/openv/netbackup/bin/bprestore $bprestore_args
rc=$?
if (( $rc > 1 )) ; then
    Error "bprestore failed (return code = $rc)"
fi

The return code up to 5 means a successful restoration.

If this should be confirmed by Veritas.

Thanks

Benoit

Platform

Linux x64

OS version

RHEL 10

Backup

NBU

Storage layout

No response

What steps will reproduce the bug?

No response

Workaround, if any

No response

Additional information

Each return code should be interpreted.

gdha commented at 2026-02-04 07:58:

@bwelterl Thanks for the feedback - I will check this out.

gdha commented at 2026-02-09 08:45:

Common bprestore return codes and their meanings include:
0: The restore was successful.
1: The restore was partially successful.
5: The restore failed to recover the requested files; this is a general error code often used for failed VM instant recoveries or general file-level failures.
25: Cannot connect on socket; indicates a connection failure, often resolved by checking PBX (vxpbx_exchanged) service.
8: Unable to determine the status of rbak (used to perform the restore), meaning NetBackup cannot confirm if the restore worked.
13: General failure to restore.

gdha commented at 2026-02-27 15:06:

@bwelterl PR has been merged. Please verify and let us know if this issue can be closed. Thanks.

gdha commented at 2026-03-16 15:28:

No news is good news, therefore, we are closing this issue.

bwelterl commented at 2026-03-17 08:23:

Hi @gdha

Thanks for the PR. To be honest, I'm not 100% sure we have a correct backup with a different return code than 0.
We might write a warning to let the user check the logs in this case.

Thanks a lot.

Benoit

[Export of Github issue for rear/rear.]