cancel
Showing results for 
Search instead for 
Did you mean: 

Hung Backup jobs

chandrasekarmp
Level 4

I have a Master server with 6.5.3 and All my backup ploicies are working fine.

But C Drive backups are running for long time and after writing some amount of data the backup job is getting hung. 

This happens only for few client servers. We are not able to figure out the issue. 

can anyone please help me out?

6 REPLIES 6

scorpy_582
Level 6
bpbkar is the process that runs on the client wwhen a backup is run.. 

To enable the log for bpbkar, create a directory <install path>\Veritas\Netbackup\logs\bpbkar
Increase the verbosity from the admin console
Run a backup and you will see where exactly its hung..

What is your backup selection? If its ALL_LOCAL_DRIVES, try to take backup of just C:\ in one policy.
Check the system event log.

rookie11
Moderator
Moderator
   VIP   

check whether anti virus may be scanning files in C:\ 

Stumpr2
Level 6
The C:\ drive is usually smaller than the other drives. You could be experiencing low disk space. Read the article titled "Low Disk Space" in the articles section of the forum.
https://www-secure.symantec.com/connect/articles/low-disk-space

predrag
Not applicable
Partner Accredited
There are several reasons why C drive is failing:
- Disk space issue (as Stumpr mentioned)
- Check the Volume Shadow Copy Services...
- Disk performance issues (RAID5 or RAID6 issues)

Predrag

rlj
Level 3
I'm having the same hang/queued problem when running a backup on the media server it's self.  Remote backups using the media server work.  It first started hanging on the backup scan, so I disabled that and it now hangs with a queued message.  I've unloaded the magazines and loaded 8 new LTO3's.  I'll try another test.. Ron

PS;  I'm just running a simple directory backup for testing..  BE 12.5

Shashank
Level 4
Hi,
   Disk space issue in c drive
  Check the Volume Shadow Copy Services is manual
  Disk performance issues (RAID5 or RAID6 issues) & I/O read\write operation.
    Check memory utilisation

  Eventough this will not work just delete the policy & recreate policy.