The problem is with a bug in the s/w. I'm guessing you probably made a change to one of the pools recently. We have had the same problem twice. The only fix is to delete the pools and recreate them from scratch. We have to do this each time we make a change. CA is yet to admit a problem.
In response to the initial problem which stated local backups are just as slow, this rules out any network problems. This may sound stupid, but try shutting down the services & renaming the log file. We had a similiar problem when the log file was about 16MB. We now do this on a regular basis...
I would try initializing the database. It appears there is some corruption dbcheck is not detecting, in which case keybuild or dbfix would not help. We have been running the same version for 1 year now and experience occasional db corruption. Most of the time it is fixed with the utilities...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.