Hi Normally our restored DB will be 40GB. Is there any reason we would need significantly more space than this when restoring?
Secondly are there specific bugs in 2.5.4 which could result in this behaviour? If not I would guess the 2.5.5 would not fix this problem? Best regards Jardar On Wed, Jun 22, 2016 at 6:23 AM, liviuslivius [email protected] [firebird-support] <[email protected]> wrote: > > > hi, > > two things > 1. try latest FB version in part, you have 2.5.4 but there is 2.5.6 or > newer > 2. 20 GB is small try to restore this db on normal PC if server have only > 20GB free. > > ps. in FB3 transaction id is int64 - no more problems :) > > regards, > Karol Bieniaszewski > > > -------- Oryginalna wiadomość -------- > Od: "Rune Bjønness [email protected] [firebird-support]" < > [email protected]> > Data: 22.06.2016 02:03 (GMT+01:00) > Do: [email protected] > Temat: [firebird-support] Gbak restore hangs on "activating and creating > deferred indexes" > > > > Hi, > > > > We're trying to do a restore of a 40 GB database (FB 2.5.4 / Win 2008 > Server) because it has reached its transaction limit. > > During our first restore attempt it seemed to freeze after having restored > all records and started activating and creating deferred indexes. > > That is, the size of the restored file was not changing for several hours > and the last entry in the log file from gbak ended in the middle of a > sentence. > > > > We lost hope and cancelled the process, which resulted in several more log > entries of "activating and creating deferred indexes" being written, but we > got no error messages. > > The server had 20 GB of available disk space left when the restore was > hanging. > > > > Do you have any suggestions to what the cause of this could be, or how we > can identify the cause? > > > > > > --Rune Bjønness > > > -- Jardar Maatje Nortek Data Services AS Brugata 1 0168 Oslo tlf: +47 95184034
