Replication

Hi,

I have clients in central who are using Vertica replication and are happy with it for the most part. One major issue with replication is that if an object does not exist on the target system, it will be owned by the dbadmin user when created, not the originating owner. That's the only complaint I've heard about replication.

The issue with copy cluster is that the DR site will lag way behind the PROD site as it'll take a while to do a complete copy.

I do not have any clients currently using ant 3rd party replication tools. Although I did let WWT in St. Louis know about Attunity, but they did not want to pay for it

Hi Jim ,
if I understand correctly , copycluster is doing an incremental copy , so the first one should take a while, but the following "refresh" should be quicker ?
thanks for the feedback
Regards
Bernard

Yes, it is incremental. It's good if you need the entire cluster copied at the DR site, but, my clients identified a sub-set of the DB they want to replicate, so I guess that's why they chose replication. Also, a major complaint I hear for copy cluster is that the target cluster has to be down.

However, with the recent changes in licensing, maybe the copy cluster option is best?

Recent changes to licensing:

• Premium is allowed 2 duplicate data copies. Express isn’t. No change to non-production guide.
• Non production – 1 active DR cluster w/ duplicate data can be used for read/write purposes

The point there is "duplicate data". I believe the DR site has to be an EXACT copy of the primary. So if not using copy cluster, any other method to maintain the DR will require the client to make sure the primary site = the DR site (i.e. via ETL into both sites, updating both sites, full replication, etc.)

ok thanks for that clarification