You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by DEEPTHI KOLLIPARA <de...@tcs.com> on 2020/06/03 08:17:30 UTC
Configuring DR site for Ignite Application
Hi Team,
We have implemented Apache Ignite 2.7 version with Ignite native persistence enabled in partition mode. We are planning to create a DR(Disaster Recovery) site for the production environment using RP4VM.
RP4VM will technically keep the cloned VM at DR Site in sync with the Production Site OR vice-a-versa. RP4VM will help in case if DR Shifting is done than VMs are other location can be readily available for Business Continuity.
Will there be any issues with the ignite nodes when nodes are started in DR site. Kindly suggest on this.
Thanks
Deepthi K
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
Re: Configuring DR site for Ignite Application
Posted by Denis Magda <dm...@apache.org>.
Hi Deepthi,
Will that be a full image of a VM with a current execution state (memory,
OS, disk, Ignite node process) or just a snapshot of Ignite persistence
files?
In short, if you do the full image but don't clone the network settings
then the cluster will fall to pieces once VMs and their execution state are
recovered on another DR. The thing is that the nodes used one set of IP
addresses in on DR and expect to have the same IPs after the recovery.
-
Denis
On Tue, Jun 9, 2020 at 9:23 PM DEEPTHI KOLLIPARA <de...@tcs.com>
wrote:
> Hi Denis,
>
>
>
> Thank you for your reply. Its mentioned as there should not be any
> change in IP address, port number. But for DR site IP’s and ports will be
> change, but data will be sync with original nodes.
>
> How cluster will behave if the IP address got change?
>
> Cluster Nodes Migration With vMotion
>
> · Memory state on the new host is identical.
>
> · Disk state is identical (or the new host uses the same disk).
>
> · *IP addresses, available ports, and other networking parameters
> are not changed.*
>
> · All network resources are available, TCP connections are not
> interrupted.
>
> Thanks
>
> Deepthi K
>
>
>
> *From: *Denis Magda <dm...@apache.org>
> *Sent: *Wednesday, June 3, 2020 8:52 PM
> *To: *user <us...@ignite.apache.org>
> *Subject: *Re: Configuring DR site for Ignite Application
>
>
> "External email. Open with Caution"
>
> Hi Deepthi,
>
>
>
> If RP4VM is comparable to VMWare VMotion then the following page should be
> exactly what you are looking for:
> https://apacheignite.readme.io/docs/vmware-deployment#cluster-nodes-migration-with-vmotion
>
>
> -
>
> Denis
>
>
>
>
>
> On Wed, Jun 3, 2020 at 1:17 AM DEEPTHI KOLLIPARA <
> deepthi.kollipara@tcs.com> wrote:
>
> Hi Team,
>
>
>
> We have implemented Apache Ignite 2.7 version with Ignite native
> persistence enabled in partition mode. We are planning to create a
> DR(Disaster Recovery) site for the production environment using RP4VM.
>
>
>
> RP4VM will technically keep the cloned VM at DR Site in sync with the
> Production Site OR vice-a-versa. RP4VM will help in case if DR Shifting is
> done than VMs are other location can be readily available for Business
> Continuity.
>
>
>
> Will there be any issues with the ignite nodes when nodes are started in
> DR site. Kindly suggest on this.
>
>
>
> Thanks
>
> Deepthi K
>
>
>
>
>
>
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
RE: Configuring DR site for Ignite Application
Posted by DEEPTHI KOLLIPARA <de...@tcs.com>.
Hi Denis,
Thank you for your reply. Its mentioned as there should not be any change in IP address, port number. But for DR site IP’s and ports will be change, but data will be sync with original nodes.
How cluster will behave if the IP address got change?
Cluster Nodes Migration With vMotion
· Memory state on the new host is identical.
· Disk state is identical (or the new host uses the same disk).
· IP addresses, available ports, and other networking parameters are not changed.
· All network resources are available, TCP connections are not interrupted.
Thanks
Deepthi K
From: Denis Magda<ma...@apache.org>
Sent: Wednesday, June 3, 2020 8:52 PM
To: user<ma...@ignite.apache.org>
Subject: Re: Configuring DR site for Ignite Application
"External email. Open with Caution"
Hi Deepthi,
If RP4VM is comparable to VMWare VMotion then the following page should be exactly what you are looking for: https://apacheignite.readme.io/docs/vmware-deployment#cluster-nodes-migration-with-vmotion
-
Denis
On Wed, Jun 3, 2020 at 1:17 AM DEEPTHI KOLLIPARA <de...@tcs.com>> wrote:
Hi Team,
We have implemented Apache Ignite 2.7 version with Ignite native persistence enabled in partition mode. We are planning to create a DR(Disaster Recovery) site for the production environment using RP4VM.
RP4VM will technically keep the cloned VM at DR Site in sync with the Production Site OR vice-a-versa. RP4VM will help in case if DR Shifting is done than VMs are other location can be readily available for Business Continuity.
Will there be any issues with the ignite nodes when nodes are started in DR site. Kindly suggest on this.
Thanks
Deepthi K
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
Re: Configuring DR site for Ignite Application
Posted by Denis Magda <dm...@apache.org>.
Hi Deepthi,
If RP4VM is comparable to VMWare VMotion then the following page should be
exactly what you are looking for:
https://apacheignite.readme.io/docs/vmware-deployment#cluster-nodes-migration-with-vmotion
-
Denis
On Wed, Jun 3, 2020 at 1:17 AM DEEPTHI KOLLIPARA <de...@tcs.com>
wrote:
> Hi Team,
>
>
>
> We have implemented Apache Ignite 2.7 version with Ignite native
> persistence enabled in partition mode. We are planning to create a
> DR(Disaster Recovery) site for the production environment using RP4VM.
>
>
>
> RP4VM will technically keep the cloned VM at DR Site in sync with the
> Production Site OR vice-a-versa. RP4VM will help in case if DR Shifting is
> done than VMs are other location can be readily available for Business
> Continuity.
>
>
>
> Will there be any issues with the ignite nodes when nodes are started in
> DR site. Kindly suggest on this.
>
>
>
> Thanks
>
> Deepthi K
>
>
>
>
>
>
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>