Unsolved
This post is more than 5 years old
27 Posts
0
1095
Windows jobs appears to be hung - waiting for bootstrap?
Hi -
I have a full backup that appears to be hung - it looks like everything has been backed up and completed but is looking for the "bootstrap" to run?
I am a newbie - is this the index tape?
Do we need to make sure there is one in the library?
Do I just assign a tape as an index tape?
Is there a way to kill this job and restart it?
I keep getting "job aborted" because another job is currently running.
Need help.
Thanks,
-John
ble1
14.3K Posts
0
July 10th, 2012 07:00
Check pending messages... what is typical early mistake in configuration is to have backups going to media server A and restrict pool oo devices assigned to media server A... but bootstrap by default will go on same pool, but from backup server and not media server. In such case you get an issue like this. Check if that is your situation. If yes, I would suggest to have separate pool for index and bootstrap backups only.
John Leonard
27 Posts
0
July 11th, 2012 10:00
I was able to stop and then start the jobs.......
It appears that the jobs appear to be hanging even after a restart of the jobs.
I there a way to find logs that can assist in troubleshooting this?
Where do I want to start?
The jobs look be suck at 50% and have been running for 18hrs.
It looks like a level 1 backup - could it be taking longer because the full did not complete?
Please advise.
Thanks.
-John
ble1
14.3K Posts
0
July 12th, 2012 02:00
Check logs (daemon.raw). If you have access to same UNIX/Linux box or running newer Windows NW version, you can run nsrwatch to check if you have any critical waiting event.