Standing up new 60 TB Standby DB on different storage - 3 options - are there more?

From: Chris Taylor <christopherdtaylor1994_at_gmail.com>
Date: Wed, 21 Feb 2018 14:16:13 -0600
Message-ID: <CAP79kiROjr0ZOiKuq0FxHQb0sZWhJhONuf1s+v2nO28tSoakyw_at_mail.gmail.com>



Scenario:
60 TB database on 12.1 (no multi-tenant)

Requirement:
Create Standby DB on a new host with new storage

Here are the options I've identified. I'm looking for others - or concerns about any of these 3. Personally, I favor #1 but with this size database, I'm not sure how "smart" it is.

  1. Active Duplicate from Primary to Standby using RMAN duplicate - I like this one, but never done a database of this size before. Am concerned about it failing midstream but I "think" an RMAN duplicate will pick up where it left off if you have to restart it?
  2. RMAN backup to disk on primary , swing luns to new Standby server and restore backup? Concern here is the time element involved in the backup, recovery and maintaining archivelogs necessary for the recovery
  3. Standby Database Creation using incremental backups of datafiles like this: https://blog.rackspace.com/standby-database-creation-of-vldbs. Concern here is that I've never done this method and seems like it could be prone to errors

Any other options I'm not considering? Any comments on the above options?

Thanks,
Chris

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Feb 21 2018 - 21:16:13 CET

Original text of this message