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 creates database file even though error [CORE1333] #1752

Closed
firebird-automations opened this issue Jun 30, 2007 · 4 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @cincuranet

When I start nbackup for example with wrong chain of backup files, the restored database file is created. I expect that if error occurs, no file is created so I'm able to fix input and start restore immediatelly again.

@firebird-automations
Copy link
Collaborator Author

Commented by: @romansimakov

It's not a bug. When you start nbackup with wrong chain of backup files, the restored database file will contains integrity part of database. So you will lost the data, but will have data of 0 or (0, 1) levels. If restored database file is deleted, you lost full database. In that time you can delete restored database file manually if you need. To detect an error you can check error output stream of nbackup utility.

@firebird-automations
Copy link
Collaborator Author

Commented by: @cincuranet

Oh, that's smart. :)

So the "bug" can be closed.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Open [ 1 ] => Closed [ 6 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 12460 ] => Firebird [ 15105 ]

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