It's supposed to be slow, it is basically doing the "first" backup again. That means, there is no acceleration, it's doing everything from scratch.
First of all I had to cancel the Accelerator Forced Rescan (AFR) full backup since it's running in 2 MB/sec and it's been running for 6 days which is ridiculous. I was thinking may be it's taking time to do some calculation at the back end and anytime the backup speed would gear up. No it didn't happen.
Now I am running an incremental to backup the changed data in last 6 days.
Even if AFR backup is supposed to behave like 1st backup, it should be fast.
I have observed an interesting matter:
1. After AFR backup kicked in, I found the progerss to be little. So I started monitoring in the Resource Monitor. Multiple threads are running in the system.But one thread at a time is reading the filesystem and updating 500 files. Then no bpbkar32 process is reading filesystem for 20-40 seconds and then another thread start reading filesystem. I know it's ridiculous. But that's the count I saw in the Netbackup console and the bpbkar32 behaviour in resource monitor window. The speed of reading filesystem was below 1 MB/sec mostly.
2. When I am running incremental backup, same multiple threads are running. But the overall filesysteam reading speed is 50-70 MB/sec as I am observing in resource monitor.
Why does Netbackup behave in this manner?
Can you please confirm how many files are you backing up?? Do you see millions of very small files being backed up and do they change (small files) every day or frequently??
Share the job details showing the number of files you are backing up. I have seen Accelerator backup taking more time compared to incremental or differential backup when there are millions or multiple thousands for very small size files to backup.
