Re: VLDB RTO issue

Harinderpal,

The simplest and least-expensive approach would be to incorporate Flashback Database into your existing DR standby, as documented HERE <https://docs.oracle.com/database/121/SBYDB/log_apply.htm#GUID-B891A164-1FDC-4AB3-838F-E6A91E7DA0B7>, in section 8.2.2.1 immediately following the discussion about delayed log apply in section 8.2.2.  Considering delayed log apply, either on your existing DR standby, or (more appropriately) on a second local or DR standby is also worth considering.

Hope this helps...

-Tim

On 2/21/2020 11:40 AM, Harinderpal Singh wrote:
> Hi there,
>
> The database for our critical Banking application is 13 TB, and our
> RTO (Recovery Time objective) is 2 hours. We are running on 12C  and
> have 3 nodes RAC clusters in both Prod & DR and have Active Data Guard
> set up too.
>
> But our company's Audit & Risk compliance team has flagged us with
> VLDB break asking us how would you restore your large DB from the
> backup in 2 hours if there will be any Cyber Attack and corruption
> gets propagated to DR. I know this kind of restore/recovery may not be
> required ever, but we still have to prove that we have a strategy in
> place to meet our RTO of 2 hours in case we have to restore from
> backup. I would like to mention that we have to keep at least 8-10
> years of data in our DB for compliance purposes.
>
> I know there might be lots of DBAs on this forum who could be
> supporting VLDBs, can you please share how have you implemented VLDB
> recovery solutions for your DBs?
>
> Thanks,
> Harinder Singh
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l