Re: DG for nologging

> On 8/03/2018, at 8:02 AM, Andrew Kerber <andrew.kerber_at_gmail.com> wrote:
> 
> The problem I have always had with SAN replication (as a dba) is that we end up relying on people outside of our control, sys admin, network, storage personnel, to keep the data up to date, and we really lack the ability to validate the status on a daily basis.  I like dataguard because I have full access to logs and status, can see what is going on, know when there are problems, and typically have the ability to fix the problems.  With SAN replication you are relying on someone else to take care of everything.
> 
>> On Wed, Mar 7, 2018 at 12:32 PM, Arjen Visser <arjen.visser_at_gmail.com> wrote:
>> Some disadvantages of SAN:
>> 1)With database SAN replication you are replicating database data 3 times so quite inefficient and requiring more bandwidth. Once for all the changes in the data files, once for replicating redo, and once for replicating archive logs. With a standby database you are only replicating the changes once.
>> 2)You do not know if your SAN replicated database will start if you really need it. With a standby database it is always running and ready to take over.
>> 3) The replicated SAN database cannot be used for anything. The standby database can be used for offload reporting, offloading backups, feeding ETL etc.
>> 
>> Regards, Arjen
>>