Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NBackup Delta file still 'active' after nbackup-0 end [CORE3292] #3660

Open
firebird-automations opened this issue Dec 27, 2010 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: ABC Mail (abcmail)

the DELTA file is still activily used for updates on db, the original FDB file isn't updates.
I would like to merge the DELTA file into the FDB, so there's again one file for the database

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

NBackup is known to have various issues, especially in the older Firebird versions, see CORE2539, CORE1139, CORE2749, CORE2266 for examples. Some of those issues are resolved in the recent v2.1 post-releases, but generally it's recommended to migrate to Firebird 2.5 if you heavily rely on that feature.

@firebird-automations
Copy link
Collaborator Author

Commented by: ABC Mail (abcmail)

Thanks Dimitry, but do you also know how to correct the problem caused by nbackup, leaving the Delta file after backup?

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

The issue has been fixed in case CORE2539/Firebird v2.1.4 as Dmitry noted. There is no workaround to the issue.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Problem with the active delta could be (supposedly) resolved with backup/restore via GBAK.

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

It should be merged automatically after shutdown of all server processes (suppose you used CS)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant