Hello, Thomas!

Saturday, October 12, 2013, 1:06:24 AM, you wrote:

TS> * Running th restore through the Services API/Manager

right, this is the fastest way.

TS> * Provide a larger page cache upon restore, because especially the index
TS> creation step loves RAM. Don't forget to set the page buffers value back
TS> again at database-level after the restore via e.g. gstat. I've seen
TS> restore improvements of > 300% for largish indexes this way.

This idea is useless. We have done complex restore
test, including specifying -bu nnn option, and found no difference
for cache size from 1024 to 16384 pages (classic and superserver),
for data only (-i) or full restore (data+indices).

--
Dmitry Kuzmenko, www.ib-aid.com