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

Physical (page-level) standby replication / page shipping [CORE2990] #3372

Open
firebird-automations opened this issue May 6, 2010 · 16 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Saulius Vabalas (svabalas)

Is related to CORE2216

Votes: 11

Data replication/mirroring Option natively built into FB Engine allowing shipping and applying deltas on target DB's at page level for predefined tables and/or rule configurable record ranges. Critical for High Availability Databases

====== Test Details ======

See test for CORE2216

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

I'd suggest to split this request into two separate ones: built-in page-level replication (new feature) and its table/record level customization (improvement).

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Version: 3.0.0 [ 10048 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @aafemt

I'd suggest to discover nbackup instead of...

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

NBackup doesn't allow you to have a warm standby, for example. IMO, this is a completely different tool, although with some technological similarities.

@firebird-automations
Copy link
Collaborator Author

Commented by: Saulius Vabalas (svabalas)

Have no problems splitting it into 2 items. Dmitry is right on the target. The goal is to have Hot Stand-By DB where Engine is performing replication real-time

@firebird-automations
Copy link
Collaborator Author

Modified by: Saulius Vabalas (svabalas)

description: Data replication/mirroring Option natively built into FB Engine allowing shipping and applying deltas on target DB's at page level for predefined tables and/or record ranges. Critical for High Availability Databases

=>

Data replication/mirroring Option natively built into FB Engine allowing shipping and applying deltas on target DB's at page level for predefined tables and/or rule configurated record ranges. Critical for High Availability Databases

@firebird-automations
Copy link
Collaborator Author

Modified by: Saulius Vabalas (svabalas)

description: Data replication/mirroring Option natively built into FB Engine allowing shipping and applying deltas on target DB's at page level for predefined tables and/or rule configurated record ranges. Critical for High Availability Databases

=>

Data replication/mirroring Option natively built into FB Engine allowing shipping and applying deltas on target DB's at page level for predefined tables and/or rule configurable record ranges. Critical for High Availability Databases

@firebird-automations
Copy link
Collaborator Author

Commented by: Jitka Dařbujanová (jitka)

What is maximum average number of active DB connections to Firebird server (for example on Linux system)? I know that it highly depends on machine, configuration and architecture of database... But do you have some statistics, more specific case studies etc anywhere?

I have been told that 1000 active users on Linux and less on Windows server on some training, can you confirm that? What to do when more is needed and mirroring isn't there at this moment? Thanks for your advice.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

summary: Built-in data replication/mirroring => Physical (page-level) standby replication / page shipping

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Fix Version: 4.0 Alpha 1 [ 10731 ]

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Siva Ramanathan (s2ramana)

This is critical for mass enterprise adoption.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is related to CORE2216 [ CORE2216 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Saulius Vabalas, please decide what to do with this ticket. We have CORE2216 implemented for v4 Alpha 1, see its usage pattern inside the last comment. It's kinda asynchronous physical replication (standby). Built-in logical (record level) replication (both synchronous and asynchronous) will be added at the Beta stage. If you're satisfied with any of these solutions, this ticket should be closed. If you still see value in built-in page shipping (as synchronous physical replication), then let's leave it open and waiting for some other day.

@firebird-automations
Copy link
Collaborator Author

Commented by: Saulius Vabalas (svabalas)

nbackup improvement is a good addition, but I would like to keep this ticket open till the rest of this request is fulfilled.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Fix Version: 4.0 Alpha 1 [ 10731 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Covered by another test(s)

Test Details: See test for CORE2216

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