How to replicate, for DR purposes, a Greenplum DB to another data centre? -


we planning large greenplum db (growing 10 100tb on first 18 months). traditional backup , restore tools aren't going have 24hr rpo/rtos deal with. there way replicate db across our dr site without resorting block replication (i.e. place segment on san , mirror)?

you've got number of options choose:

  1. dual etl. replicate input data , run same etl on 2 sites. synchronize them backup-restore every week or so
  2. backup-restore. simple backup-restore can not efficient. if use datadomain can perform deduplication on block level , store changed blocks. can offload deduplication task run on greenplum cluster (ddboost). in case of replication remote site replicate changed blocks, reduce replication time. in experience, if clean backup on dd takes 12 hours, subsequent ddboost backup take 4 hours + 4 hours replicate data
  3. custom solution. know case when data replicatioin remote site made part of etl process. etl job know tables changed, added replication queue , moved remote site using external tables. analysts working in special sandbox , sandbox replicated backup-restore daily

at moment greenplum not have built-in wan replication solution options choose from.


Comments

Popular posts from this blog

php - Submit Form Data without Reloading page -

linux - Rails running on virtual machine in Windows -

php - $params->set Array between square bracket -