Please dont laugh when you read this. i was told by the CA techs that in order to derive the actual throughput rate for my backup jobs, I was to add 200 to the throughput rate reported in the log file.
That is hard to believe- Since it's their software, you'ld think if there was a bug that under reported throughput they'ld immediately issue a patch (I would!) - This is probably more akin to a car dealer telling you that you needed to "add 20 mpg to what that gov'ment sticker says, to get the 'true' reading..."
Mind you if the throughout time includes the pre-backup calculations and the database update at the end then the throughput figures would be a fair bit under the true rate.
We have one server that does about 25 sessions on it's backup (multiple servers and multiple logical drives) - it takes it about 1.5 hours to update the ARCserve database and about 8 hours for the actual job to run.
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.