RE: [firebird-support] TMP space required during restore

2012-01-26 Thread Rick Debay
 Twice the size is an old and possibly still a good guess, I think. It
all depends on the number and size of the indices.

So to restore an 11GB database we should have 22GB available where
TempDirectories points? 


Disclaimer: This message (including attachments) is confidential and may be 
privileged. If you have received it by mistake please notify the sender by 
return e-mail and delete this message from your system. Any unauthorized use or 
dissemination of this message in whole or in part is strictly prohibited. 
Please note that e-mails are susceptible to change. RxStrategies, Inc. shall 
not be liable for the improper or incomplete transmission of the information 
contained in this communication or for any delay in its receipt or damage to 
your system. RxStrategies, Inc. does not guarantee that the integrity of this 
communication has been maintained nor that this communication is free from 
viruses, interceptions or interference. 




Re: [firebird-support] TMP space required during restore

2012-01-26 Thread Alexey Kovyazin
Rick,

 So to restore an 11GB database we should have 22GB available where 
TempDirectories points?

No.
Download our free tool DBInfo 
(http://ib-aid.com/products/firebird_interbase/monitoring/dbinfo) and 
open your database there.
Look at Index Pages size. If you have the single table with the single 
index in the database, it will be close to the size you need to have in 
Temp, otherwise it will be less (during restore indices are being built 
one by one).

Detailed breakdown for each index you can figure out by investigating 
gstat -r statistics (or look at IBAnalyst to have it visualized): 
http://www.ib-aid.com/images/ibanalyst_index_size.png

Regards,
Alexey Kovyazin
IBSurgeon (www.ib-aid.com)



 Disclaimer: This message (including attachments) is confidential and 
 may be privileged. If you have received it by mistake please notify 
 the sender by return e-mail and delete this message from your system. 
 Any unauthorized use or dissemination of this message in whole or in 
 part is strictly prohibited. Please note that e-mails are susceptible 
 to change. RxStrategies, Inc. shall not be liable for the improper or 
 incomplete transmission of the information contained in this 
 communication or for any delay in its receipt or damage to your 
 system. RxStrategies, Inc. does not guarantee that the integrity of 
 this communication has been maintained nor that this communication is 
 free from viruses, interceptions or interference.

 



[Non-text portions of this message have been removed]



Re: [firebird-support] TMP space required during restore

2012-01-24 Thread Thomas Steinmaurer
 gbak: ERROR: I/O error for file /tmp/fb_sort__M9plMy
 gbak: ERROR: Error while trying to write to file
 gbak: ERROR: No space left on device


 We've started getting this error when restoring an 11GB database.  How
 much space should we estimate for temp files?

Twice the size is an old and possibly still a good guess, I think. It 
all depends on the number and size of the indices.


-- 
With regards,
Thomas Steinmaurer (^TS^)
Firebird Technology Evangelist

http://www.upscene.com/
http://www.firebirdsql.org/en/firebird-foundation/


Re: [firebird-support] TMP space required during restore

2012-01-24 Thread Ann Harrison
Rick Debay wrote:

 gbak: ERROR: I/O error for file /tmp/fb_sort__M9plMy
 gbak: ERROR:     Error while trying to write to file
 gbak: ERROR:     No space left on device


 We've started getting this error when restoring an 11GB database.  How
 much space should we estimate for temp files?

More.

 Thomas Steinmaurer t...@iblogmanager.com wrote:

 Twice the size is an old and possibly still a good guess, I think. It
 all depends on the number and size of the indices.

Each table must be sorted for each index defined.  The sort doesn't
use the whole record, just the key, the record number, and a small
amount of overhead.  The sort is done for each index, and no sorts are
done in parallel.If you have lots of small tables, you'll need
less space than if you have a few very large tables.  The amount of
space used is determined by the index with the largest key in the
largest table and may require considerably more space than the index
it eventually creates if sub-sorts have to be merged to disk.

Good luck,

Ann