#108 Creation of temp tables is far so slow to perform a restore

[William Arlofski]

First I want to say I still appreciate the progress that you have made with Webacula. It is getting better with each update and I enjoy following its progress.

Webacula is a really nice and easy to follow interface for our non-tech clients who need some type of access to information about their backups but where bconsole (command line) is too complex for them.

Our problem is that even on small bacula deployments we are unable to utilize Webacula to allow our clients to do their own simple restores because the temp table creation is far too slow.

I would love to see this addressed and will help in any way i can to make this fast enough to give our clients the ability to do their own restores with webacula.

Thank you so much!

--
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/

[Nobody/Anonymous]

I already commented on this in http://sourceforge.net/tracker/?func=detail&aid=3198232&group_id=201199&atid=976600.

Problem is that every single file in the restore set is inserted into a database table AND for each file the Lstat decoding is done. Usually you do a selective restore to retrieve single files or some folders recursivley. So all this inserting and Lstat decoding is unnecessary for usually >90% of the files in the restore set.

An on-demand Lstat decoding and not putting the whole restore set in a database table would speed up things siginificantly, I am sure.

At the time being, selective restore in webacula is near to unusable, imho.

Of course I follow in line, offering any help on thinking out concepts and testing, etc. If needed.
Jan

OCSCAR
open source consulting administration realisation
http://www.oscar-consult.de/