jmsperu commented on PR #12900: URL: https://github.com/apache/cloudstack/pull/12900#issuecomment-4411314364
@weizhouapache fair point — the intent here was never to replace external/operational DB backup tooling, but to give small and edge deployments a one-knob "backup the management plane to the same NAS that already holds my VM backups" option for disaster recovery (rebuild from a fresh management server using only what's on the NAS). Concrete adjustments I can make: 1. Make the DB component opt-in via an explicit `infrastructure.backup.include.database` global setting, defaulting to **false** — so by default we only ship configs + certs (where there's no real ops alternative anyway). 2. Document explicitly that for production deployments with existing backup tooling, the DB component should stay disabled and be handled externally. 3. Keep the unified target (same NAS as VM backups) for the configs+certs path so recovery is in one place. Does that split land closer to where you'd want it? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
