Subject | RE: [firebird-support] restore single .gbk to multipe .fdb |
---|---|
Author | RB Smissaert |
Post date | 2007-10-07T07:45:31Z |
Thanks, I will make a new backup and do a fresh restore.
Didn't know I needed to use dialect 1.
RBS
_____
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Helen Borrie
Sent: 07 October 2007 01:00
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] restore single .gbk to multipe .fdb
At 08:09 AM 7/10/2007, you wrote:
isn't a cause of lost data. However, a backup taken from the
original database whilst a large insert operation was in process
would be. The backup process can only see data that was already
committed when the backup started.
Start afresh with a new backup taken from your v.5.6 server when
there's nobody online and gbak can get exclusive access.
And don't forget to use dialect 1 for client attachments with the restored
db.
./heLen
[Non-text portions of this message have been removed]
Didn't know I needed to use dialect 1.
RBS
_____
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Helen Borrie
Sent: 07 October 2007 01:00
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] restore single .gbk to multipe .fdb
At 08:09 AM 7/10/2007, you wrote:
>Figured out the syntax now to restore the IB .gbk file to multiple .fdbC:\test\s6.fdb
>files, and it seems to look good
>
>with one large primary file of about 2 Gb and a smaller file of about 0.5
>Gb. However when I test with
>
>a query like this:
>
>select max(entry_id) from entry on the largest table in the database it
>shows there are a lot of rows missing.
>
>This is what I ran with gbak:
>
> gbak -c -p 4096 -v -user sysdba -password xxx C:\test\s6.gbk
>500000 C:\test\s6A.fdbBacking up and restoring from single to multiple files and vice versa
>
>Any ideas what I might be doing wrong here?
isn't a cause of lost data. However, a backup taken from the
original database whilst a large insert operation was in process
would be. The backup process can only see data that was already
committed when the backup started.
Start afresh with a new backup taken from your v.5.6 server when
there's nobody online and gbak can get exclusive access.
And don't forget to use dialect 1 for client attachments with the restored
db.
./heLen
[Non-text portions of this message have been removed]