Open andbos opened 11 months ago
Would also love to see RMAN support, like an RMAN CRD with backup schedule und targets inside ... So I can get rid of those upcoming error messages about too little free space in my SIDB container for Archive Logs ... This would also help with customer Bosch testing SIDB internally . Best regards, Marcel
Hi,
It's been three months since I created this issue. Could you please elaborate a bit on what will come in the next release and when that will come in time? Also, what have you got planned for future releases?
Best regards, Andreas
Hi,
Is support for RMAN backups and Automatic failover & Observer in the road map?
Best regards, Andreas
Hello Andreas,
Failover&Observer are already there - use the Data Guard feature if You want zero downtime patching and minimum downtime failover, or use pre-started containers for quicker cold failover, also a feature of OraOperator.
About RMAN support - I am also waiting for this and I am keen on the developer's response to Your inquiry :-)
Best regards, Marcel
Gesendet: Freitag, 14. Juni 2024 um 10:32 Uhr Von: "andbos" @.> An: "oracle/oracle-database-operator" @.> Cc: "ilfur" @.>, "Comment" @.> Betreff: Re: [oracle/oracle-database-operator] Roadmap features (Issue #76)
Hi,
Is support for RMAN backups and Automatic failover & Observer in the road map?
Best regards, Andreas
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
Hi,
Yes, support for manual failover is there but not for automatic failover. The automatic failover feature I'm referring to is Data Guard Fast-Start Failover. It requires having an Oracle Observer process running on another node than primary & standby which then will monitor the primary & standby and if the primary goes down it will trigger failover (after FastStartFailoverThreshold has been reached).
Best regards, Andreas
Hi,
Is there a plan to support the following features (for SIDB):
Also, is expansion of storage already supported? Assuming the storageClass has allowVolumeExpansion set to true, would it work to adjust spec.persistence.size and run kubectl apply (or patch the PVC manually). When I tried this on a physical database instance the PVC size was increased but the pod (after restart) got stuck in Init.
Best regards, Andreas