Bug 971939
Summary: | RHEV-M Assisted/Automatic DB Recovery | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Luca Villa <luvilla> |
Component: | RFEs | Assignee: | Andrew Cathrow <acathrow> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | acathrow, iheim, lpeer, pablo.iranzo, pzhukov, rbalakri |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | integration | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-03 11:22:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Luca Villa
2013-06-07 15:53:11 UTC
(In reply to Luca Villa from comment #0) > The desiderata is to have > a) RHEV-M to be able to manage inconsistencies between DB data (e.g., > restored data) and the infrastructure status, and to propose a way to > discard or include differences. Is it possible to use DB replication for this? Config files are not being changed often > b) RHEV-M always up and running > c) Supported mechanism to achieve the goal > (In reply to Pavel Zhukov from comment #4) > (In reply to Luca Villa from comment #0) > > The desiderata is to have > > a) RHEV-M to be able to manage inconsistencies between DB data (e.g., > > restored data) and the infrastructure status, and to propose a way to > > discard or include differences. > Is it possible to use DB replication for this? Config files are not being > changed often We were actually considering to replicate data to a hot stand-by DB or to transaction logs stored elsewhere. Config files are not changed often true, but it could happen and we need to ensure we are able to restore the system up-to-date and in a fully consistent way. > > b) RHEV-M always up and running > > c) Supported mechanism to achieve the goal > > (In reply to Luca Villa from comment #5) > Config files are not changed often true, but it could happen and we need to > ensure we are able to restore the system up-to-date and in a fully > consistent way. IMHO it's the job for backup solutions (application, script, system administrator etc) not for RHEV. The next step will be something like "backup /etc/sysconfig".... It should be "standard" task like "trigger backup after changing of the important config files" for system administrator. we added a simple backup/restore script. we will add support for importing an existing data domain and reconciling differences (note in 3.2 you can already get a list of disks in the storage and register them to the engine, but that will be extended more when we cover importing data domains). *** This bug has been marked as a duplicate of bug 1015321 *** |