starts at $4,000 per node per year all inclusive. With discount it can be halved but we are talking a node itself so if you have 5 nodes in primary and 5 nodes in DR we are talking about $40K already.
HTH Dr Mich Talebzadeh LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>* http://talebzadehmich.wordpress.com *Disclaimer:* Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction. On 11 November 2016 at 16:43, Mudit Kumar <mkumar...@sapient.com> wrote: > Is it feasible cost wise? > > > > Thanks, > > Mudit > > > > *From:* Mich Talebzadeh [mailto:mich.talebza...@gmail.com] > *Sent:* Friday, November 11, 2016 2:56 PM > *To:* user @spark > *Subject:* Possible DR solution > > > > Hi, > > > > Has anyone had experience of using WanDisco <https://www.wandisco.com/> > block replication to create a fault tolerant solution to DR in Hadoop? > > > > The product claims that it starts replicating as soon as the first data > block lands on HDFS and takes the block and sends it to DR/replicate site. > The idea is that is faster than doing it through traditional HDFS copy > tools which are normally batch oriented. > > > > It also claims to replicate Hive metadata as well. > > > > I wanted to gauge if anyone has used it or a competitor product. The claim > is that they do not have competitors! > > > > Thanks > > > > > Dr Mich Talebzadeh > > > > LinkedIn > *https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw > <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>* > > > > http://talebzadehmich.wordpress.com > > > > *Disclaimer:* Use it at your own risk. Any and all responsibility for any > loss, damage or destruction of data or any other property which may arise > from relying on this email's technical content is explicitly disclaimed. > The author will in no case be liable for any monetary damages arising from > such loss, damage or destruction. > > >
