Re: VLDB RTO issue

We do incremental forever using incrementally updated image copies with additional help from backup storage. All scripts and method is described here:
https://ilmarkerm.eu/blog/oracle-imagecopy-backup/

Have not had any problems backing up and doing daily restore tests with busy 160+TB databases and smaller 20-50TB ones.

On Fri, Feb 21, 2020 at 9:42 PM Harinderpal Singh <harinderpsingh_at_gmail.com> 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
>
>
>
>
>

-- 
Ilmar Kerm

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