We are currently running version 8.6 of Backup Exec on a Windows NT server, which we use to back up our Novell Server (running the latest version of the agent).
There are 5 volumes on the server, and 4 of them back up perfectly, with a throughput of around 270Mb per minute. However, when Backup Exec tries to back up the largest volume, it slows to a crawl, with the throughput falling to around 70Mb per minute.
I've tried everything. I don't think we have a network problem, as the number of ECBs in use is well below the minimum that we have defined. Similarly, the Directory Cache buffers are only slightly above the minimum (2,000), and well below the maximum (4,000).
Processor utilisation is generally quite high during backup, 70% - 90%, with the busiest thread being a thread called RB_LWMTD4239080.
While backup is running, I have noticed that the Dirty Cache Buffers and Current Disk Requests can get quite high, which would lead me to conclude that we have a possible bottleneck with the disks or RAID controller. However, I don't know if this occurs naturally during backup.
Has anybody experienced a problem like this before?
Cheers,
Tobinsk
There are 5 volumes on the server, and 4 of them back up perfectly, with a throughput of around 270Mb per minute. However, when Backup Exec tries to back up the largest volume, it slows to a crawl, with the throughput falling to around 70Mb per minute.
I've tried everything. I don't think we have a network problem, as the number of ECBs in use is well below the minimum that we have defined. Similarly, the Directory Cache buffers are only slightly above the minimum (2,000), and well below the maximum (4,000).
Processor utilisation is generally quite high during backup, 70% - 90%, with the busiest thread being a thread called RB_LWMTD4239080.
While backup is running, I have noticed that the Dirty Cache Buffers and Current Disk Requests can get quite high, which would lead me to conclude that we have a possible bottleneck with the disks or RAID controller. However, I don't know if this occurs naturally during backup.
Has anybody experienced a problem like this before?
Cheers,
Tobinsk