Just curious to understand here, regarding having a second data
guard setup with delayed log apply:- We have the primary and physical
standby(with real time log apply) set up on premise. And to minimize the
storage/maintenance cost and modernization perspective, In this situation,
Is it advisable to have this additional physical standby(with delayed log
apply) hosted on a cloud( say e.g. AWS) environment, or will it have any
downside?
On Thu, Apr 28, 2022 at 9:35 AM Lok P <loknath.73@xxxxxxxxx> wrote:
Thank You So much for the guidance.
So it looks like having another data guard setup with a good enough apply
lag is the easiest way with minimal overhead as compared to other
strategies like compression etc.
Also as Mladen pointed out we do have exadata as data guard setup only. So
perhaps we currently have a single 10GB ethernet adapter which is why the
backup team has put the figure of ~2TB/hr of RTO. And having multiple 10GB
adapters we would be able to minimize the RTO even with current DB size.
Will check on this with the team.
Regarding if we really need Exadata for this application, actually we got
~50% performance improvement across the application jobs post movement
Exadata. But yes wil see if just having a large SGA is enough to get the
similar performance.
Regards
Lok
On Thu, Apr 28, 2022 at 5:39 AM Mladen Gogala <gogala.mladen@xxxxxxxxx>
wrote:
On 4/27/22 19:55, Clay Jackson (Clay.Jackson) wrote:
It would appear that DataGuard has you pretty well covered for “normal”
sorts of disasters and outages, and that your (or your management’s)
concern now is “What happens if my entire system gets corrupted and/or
hijacked, including my DataGuard “backups”?”
You can also take a backup off the standby database. It will be
recognized as the backup of the primary, provided you're using RMAN catalog.
Regards
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217https://dbwhisperer.wordpress.com
-- //www.freelists.org/webpage/oracle-l
