Issue Details (XML | Word | Printable)

Key: CORE-5486
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Chau Chee Yang
Votes: 0
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Using GBAK to restore a 3GB+ database infinite "restoring privilege for user SYSDBA gbak"

Created: 17/Feb/17 09:54 AM   Updated: 25/Feb/17 02:11 AM
Component/s: GBAK
Affects Version/s: 3.0.1
Fix Version/s: None

File Attachments: 1. Zip Archive CORE-5486.zip (878 kB)

Environment: Windows 10 x64

QA Status: No test


 Description  « Hide
I am trying to restore a firebird 3 backup file of size 3GB++, the restore goes smooth by restoring table, create index. When i reach "restoring privilege" stage, it keep showing unstop

gbak: restoring privilege for user SYSDBA
gbak: restoring privilege for user SYSDBA
gbak: restoring privilege for user SYSDBA
gbak: restoring privilege for user SYSDBA
gbak: restoring privilege for user SYSDBA
....

I don't know when it will end. It have run for more than 1 hour.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Sean Leyne added a comment - 17/Feb/17 11:31 PM
Was the backup file created by Firebird v3.x or previous version?

How many metadata objects are in the database?

Is the SYSDBA the database "owner"?

Chau Chee Yang added a comment - 18/Feb/17 01:42 AM
The backup is created by Firebird WI-V3.0.1.32609 Firebird 3.0 x64 running on Windows in service mode.
Here are rough statistics of the tables:

Tables: 179
Generators: 88
Indices: 439
Triggers: 0
Procedures: 0

All objects owner are SYSDBA.

Sean Leyne added a comment - 19/Feb/17 02:57 AM
Please try to reproduce by restoring a "metadata only" backup.

If successful, please consider posting a copy of the "metadata only" backup for the developers to review/test with.

Chau Chee Yang added a comment - 20/Feb/17 01:30 AM - edited
I have attached a zip file as requested:

database.fdb - database with meta data only after restore
restore.log - the abnormal lengthy restore log file

Sean Leyne added a comment - 21/Feb/17 03:49 PM
Since the restore completed, though with an extremely long section of "restoring privileges".

How long did the restore take?

Are you waiting a similar length of time for the "restoring privileges" in your normal restore?

Chau Chee Yang added a comment - 22/Feb/17 01:07 AM
The restore took about 5 minutes to finish without -v (verbose output).

It took more than 1 hour If using -v switch.

Vlad Khorsun added a comment - 22/Feb/17 09:25 AM
Could you show us gbak command line ?

Chau Chee Yang added a comment - 25/Feb/17 02:11 AM
GBAK with -v take very long time to restore (1 hour ++):

    gbak -c -v backup.fbk new.fdb

GBAK without -v take restore time is normal (less than 5 minutes):

   gbak -c backup.fbk new.fdb