Forum Discussion

snawaz3's avatar
snawaz3
Level 6
13 years ago
Solved

Resume Backup

The backups running last night were interrupted due to the client file server being rebooted. In the activity monitor I clicked on resume job. The jobs show as running but kilobytes written is not changing. It has been 2 hrs since I resumed the backup. The jobs were about 70% to 80% complete. What is happening?. Will the job continue from where it was interrupted? Will it retart the job from the beginning and I will see the kiolbytes being written after the resumed backup job catches up to where it was interrupted?

  • If the job allows resume then you must be using checkpoint re-start and so the backup will resume from the last checkpoint If nothing has happened for 2 hours it may be caused by the server being busy in the day slowing the snapshot down. It is worth checking the client server to see what processes are running - if bpfis is running then it is still doing it snapshot, if bpbkar32 is running then it is running its backup - if neither are running then check the media server doing the backup for orphaned bpbrm or bptm processes that may have been left behind by the original job after the client reboot - these may need clearing down to be able to resume the job in hand. It may be worth suspending the job again and then doing a process cleanup, after which resume it again Also - if writing to disk - take a look at the disk to see if the backup image files are actually growing in size which indicates that data is being passed Hope this helps
  • If the job allows resume then you must be using checkpoint re-start and so the backup will resume from the last checkpoint If nothing has happened for 2 hours it may be caused by the server being busy in the day slowing the snapshot down. It is worth checking the client server to see what processes are running - if bpfis is running then it is still doing it snapshot, if bpbkar32 is running then it is running its backup - if neither are running then check the media server doing the backup for orphaned bpbrm or bptm processes that may have been left behind by the original job after the client reboot - these may need clearing down to be able to resume the job in hand. It may be worth suspending the job again and then doing a process cleanup, after which resume it again Also - if writing to disk - take a look at the disk to see if the backup image files are actually growing in size which indicates that data is being passed Hope this helps
  • besides, just make sure that you are seeing activity moniter with the Attempt 2

    make sure you are not looking at attempt 1, because its already failed.. 

    so look in attempt 2

  • thanks guys. the finally restarted. but are very slow. will open another incidence for your help.