Forum Discussion

sheriff_e47's avatar
sheriff_e47
Level 5
10 years ago

Restore must be resumed prior to first image expiration

Hi,

I have this messages:

2/22/2014 10:25:21 - begin Restore
12/22/2014 10:25:21 - number of images required: 1
12/22/2014 10:25:21 - media needed: HQ0595
12/22/2014 10:42:25 - Warning bprd (pid=391) Restore must be resumed prior to first image expiration on Sun Jan 11 09:24:07 2015
12/22/2014 10:42:25 - end Restore; elapsed time 0:17:04
the restore failed to recover the requested files (5)

I have checked the same case articles about this, but I still dont get the solution.

Please help anybody, what seems to be the problem here?

 

Thanks & Regards,

7.1.x and Earlier
Backup and Recovery
NetBackup
Restore
Solaris
Troubleshooting
  • sheriff_e47's avatar
    sheriff_e47
    10 years ago

    Hi All,

    I have found the solution here

    http://www.symantec.com/business/support/index?page=content&id=TECH32332

    It happened that the /usr/openv/netbackup/bin/tar binary if this client was missing, so I copied the tar file from another working client. Now it can restore again. Thank you very much

     

     

     

16 Replies

Sort By
  • sheriff_e47's avatar
    sheriff_e47
    Level 5
    10 years ago

    FYI,

    - This NBU running on Solaris 10 OS and this is the very first time I perform restore on this media server.

    - Media server is client server as well

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    It seems restore got stuck at 'media needed ... ' and then timed out. Actual restore process and media mount was never attempted. I have seen this when bprd process got hung on master server. Please try to stop NBU. Use bpps to ensure all processes/daemons are stopped. Before starting NBU again, create log folders under netbackup/logs: On master: bprd On media server: bpbrm and bptm Try the restore again after starting NBU. If stuck at 'media needed' for more than 2 minutes, please run bpps on the master and post output.
  • sheriff_e47's avatar
    sheriff_e47
    Level 5
    10 years ago

    Hi Marianne,

    Ok thanks for your suggestion. But, since there's 2 important backup policies are still running, I will try to stop the NBU and create those folders after they are completed.

    Thanks

  • Nicolai's avatar
    Nicolai
    Moderator
    10 years ago

    The "Restore must be resumed prior to first image expiration on Sun Jan 11 09:24:07 2015" simply mean that the restore did not go well, and that the restore must be performed before "Jan 11 2015" because that is the day the backup expire. You can't restore a backup that is expired.

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    In the meantime, run bpps | grep bprd This will show us current and hung bprd processes. If no restores or user backups are running, there should only be one bprd with PPID of 0.
  • sheriff_e47's avatar
    sheriff_e47
    Level 5
    10 years ago

    Here the output

    root@backupprd # ./bpps | grep bprd
        root   854     1   0   Mar 27 ?          72:15 /usr/openv/netbackup/bin/bprd
    root@backupprd #

  • sheriff_e47's avatar
    sheriff_e47
    Level 5
    10 years ago

    Hi Marianne,

    I have stop/start NBU, create the log folders, and start restore again. But, it still the same. Here I attach the bpps output. Please share your analysis. Thanks

  • sheriff_e47's avatar
    sheriff_e47
    Level 5
    10 years ago

    Hi Nicolai,

    Thanks for the explanation. Btw, is there a way to extend the expiration date of the image? Please your advice. Thanks

     

     

     

  • Nicolai's avatar
    Nicolai
    Moderator
    10 years ago

    Yes - you can use the bpexpdate command to extend (or delete) the backup. So be carefull with that command

    /usr/openv/netbackup/bin/admincmd/bpexpdate -recalculate -backupid acme_0988403420 -d 10/31/2016

    The command above will extend the backup lifetime to 31/10/2016. However if specify a time in the past you expire the backup.

    Hope this clarify

     

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    root 8688 1 0 16:40:01 ? 0:00 bprd -dontfork -mpxmain This one is the culprit. The process goes into a hang state. I have only seen this where FORCE_RESTORE.... entry is in place. Normally killing this process and retry of the restore gets the restore going.