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

Support for nbackup via service manager [DNET224] #233

Closed
firebird-automations opened this issue Apr 18, 2009 · 2 comments
Closed

Support for nbackup via service manager [DNET224] #233

firebird-automations opened this issue Apr 18, 2009 · 2 comments

Comments

@firebird-automations
Copy link

Submitted by: @cincuranet

Votes: 2

nBackup Support

Tracker reference: CORE1758.

The nBackup utility performs two logical groups of operations: locking or unlocking a database and backing it up or restoring it. While there is no rationale for providing a service action for the lock/unlock operations—they can be requested remotely by way of an SQL language request for ALTER DATABASE—a Services API interface to the backup/restore operations is easily justified.

Backup and restore must be run on the host station and the only way to access them was by running nBackup.

The two new service actions now enabling nBackup backup and restore to be requested through the Services API are:

isc_action_svc_nbak - incremental nbackup

isc_action_svc_nrest - incremental database restore

The parameter items are:

isc_spb_nbk_level - backup level (integer)

isc_spb_nbk_file - backup file name (string)

isc_spb_nbk_no_triggers - option to suppress database triggers

Commits: bae0837 8a443d7

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: In Progress [ 3 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: vNext [ 10571 ]

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

2 participants