Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Resume Backup

Created: 21 Mar 2013 • Updated: 21 Mar 2013 | 3 comments
This issue has been solved. See solution.

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?

Operating Systems:

Comments 3 CommentsJump to latest comment

Mark_Solutions's picture

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

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
RamNagalla's picture

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

snawaz3's picture

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