Long distance application failover between data centers.

Hello:
I am working a project where there is a requirement to have a primary server and a secondary for application failover. The requirements dictate that the servers must be geographically separate at separate data centers but yet on the same IP subnet so that heartbeat messages are not natively routed. What protocol can I use to bridge the subnet over an IP routed network? GRE? L2TP?

GRE will not work as according to the last information I have you cannot bridge over a GRE tunnel. We had one such application with similar requirements and we ended up using L2TPv3 that allows transparent LAN extension. We have not had any issues with it and if you are only going to use it for heartbeats you should not run into any performance issues. L2TPv3 does tend to drive the CPU utilization high in case you have a lot of data traversing the tunnel.

Similar Messages

Coherence - grid-data replication between data centers

Hi All ,
We have two data centers , each having a coherence data-grid. How can we replicate cached data in grid between these two data centers ? I looked at the , http://coherence.oracle.com/display/INCUBATOR/Push+Replication+Pattern
but , ? I need more information on this ? Can someone direct me to some useful links and documentation ?

Unfortunately, what you've seen is about as far as it goes, I'm afraid.
I've just got it working, but it was a pain to have to dig through so much API docs and source code in order to get it working. It really should have a much better set of documentation, including a tutorial, IMHO. The crazy thing is, once you have got it working, it turns out it's not actually that difficult!
I've also posted some questions on the Incubator forums, but they've mainly fallen on deaf ears (except for one guy, Neville, who I don't think works for Oracle.) I've been trying to get PublishingTransfomers to work, but the documentation for them is very, very poor. Also, none of the "examples" have any Transformers.
It's a shame that something so heavily "pushed" at the Coherence SIGs, PR, is so poorly documented/supported... (Take a look at the low post counts of those supporting it from Oracle, and the number of unanswered messages.)
Anyway, give it a shot and let me know if you have any specific questions. I guess they should really be posted on the Incubator forum rather than here, but as it's such a "ghost town" over there I wouldn't be too hopeful of a reply! :)
NB. Make sure you download and look at the Examples: http://coherence.oracle.com/display/INCUBATOR/Coherence+Incubator+Examples

Long Distance Storage Replication

Looking for some data on storage replication between data centers connected via VPN. VPN is based on 7206VXR/IOS w/ DS-3 access. DS3 endpoints are the same Tier1 provider. Distance is Miami to/from Chicago.
Replication fo 20Gb SQL Database (initially) in a 12 hour window. Current SQL copy takes roughly 16 hours.
EMC Clarion array replication is next on the plate.

There are many options available to you and would depend on the budget and the infrastructure you already have in place. All of the storage products could provide you with FCIP links. The FCIP link/tunnel would flow inside and as data in the VPN tunnel
There are modules for the 7200's that act as B-port and would encapsulate the data across a FCIP link and so the the endpoints would be the 7200's. Then the SN5428 can provide the same FCIP connectivity and then the FC ports from the storage could plug directly into the 5428.
What may be the best option is the MDS with compression and write acceleration. Depending on the encapsulation of the DS3, the MTU can run from 1500 to 4400. So, the MDS could sit off of a gigabit link from the 7200's and make that MTU on the MDS's gigabit interface the MTU of the (MTU of the DS3-the overhead encapsulation of the VPN). Then you could apply compression and/or write acceleration to give you the FCIP link from MDS to MDS and provide the speed that you desire.

Adding 2 New SItes between 2 Data Centers

I have a current Site installed with default settings (no additional sites/subnets/site links), and we are plannig on creating 3 new DCs in our remote Data Center, which will be the second site. I want to seperate desktop traffic between the 2
Data Centers. My question is, what is the best way to do this? I want to keep the Deafult First Name Site as a catch -all for all subnets that may be missed.

1. Why do you wish to keep clients from accessing DCs in the datacenter? What harm do you think may occur?
2. Assuming a two-site topology with a site link associating each of them won't accomplish what you want, but can *reduce* the amount of authentication traffic from one site to another.
3. Keeping the Default First Site Name is fine - it won't hurt anything, but using it as a 'catch-all' for IP subnets not registered in AD indicates poor IP address management. You should address that issue first.
4. It might be possible to completely eliminate client auth traffic in one site from reaching another site by creating three sites in series (Site A <-> Site B <-> Site C) and disabling "Bridge all site links". With Site Link Bridging
disabled, the connection from Site A to Site C will no longer be transitive and clients that are members of that site will not send authentication requests to DCs in Site C. However, that's a lot of 'hoops' to jump through just to address a problem I'm
not sure is all that important.
-ds
David Shaw [MSFT]

Core switches between 2 data centers

Existing data center has 2 X Cisco 6500 series core switches, new data center has 2 X Cisco nexus core switches. For the connection between 2 data center, it will be using leased line. To establish the network connection for both side, should it use trunk port with layer 2 connection directly or layer 3 ip routing (configure the ip on switchport interface) ? What is the better approach for its design? Please share your idea.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Normally, when dealing with off-site traffic, L3 is better as it limits traffic to only what needs to go off-site.
However, as you're dealing with data centers, it's no longer uncommon that there's need to share L2 between them. So, much depends on what your needs are.

After replacing the hard drive on my G4 Powerbook and reinstalling Tiger I am no longer able to synch between itunes and itunes, it seems that the software on the ipod is of later date than itunes and I am unable to update itunes to the state prior..

After replacing the hard drive on my G4 Powerbook and reinstalling Tiger I am no longer able to synch between itunes and my ipod (Classic 160gb) it would seem that the software on the ipod is of later date than itunes and I am unable to update itunes to the state prior to the original harddrive's failure for Tiger OSX 10.4.11
Any ideas on the subject would be most helpful
Thanks in advance
Dingoh

The last security update released for Tiger users was the 2009-005 update. The latest version of QuickTime is 7.6.4. The last version of iTunes that can run on Tiger is 9.2.1, because 10.0 only supports Mac OS X Leopard and later.
So, are you on version 9.2.1?
Was it Tiger or Leopard you had on the drive before?
iTunes 9.2.1 download...
http://support.apple.com/kb/DL1056

Customizing distance between data Points on x-Axis

Hi,
I want to draw a LineChart.
I have these Timestamps [84, 1000, 34000, 34699, 439999] who
are represanting the x-Value of DataPoints along the X-Axis.
Unfortunately the distance between 2 datapoints along the
x-Axis is always the same, that means that between the points with
x-values 84 and 1000 is the same distance along the axis as between
the points with x-values 34699 and 439999.
But the distance between points with x-values of 34699 and
439999 should be much greater than between 84 and 1000.
How can I customize the distance between data Points on a
LineChart to solve my Problem?
I really dont know right now!
Greeting,
Z.

"zidaninho" <[email protected]> wrote in
message
news:gls479$nkt$[email protected]..
> Hi,
>
> I want to draw a LineChart.
> I have these Timestamps [84, 1000, 34000, 34699, 439999]
who are
> represanting
> the x-Value of DataPoints along the X-Axis.
>
> Unfortunately the distance between 2 datapoints along
the x-Axis is always
> the
> same, that means that between the points with x-values
84 and 1000 is the
> same
> distance along the axis as between the points with
x-values 34699 and
> 439999.
> But the distance between points with x-values of 34699
and 439999 should
> be
> much greater than between 84 and 1000.
>
> How can I customize the distance between data Points on
a LineChart to
> solve
> my Problem?
>
> I really dont know right now!
What happens if you convert the time stamps to Dates and use
a DateAxis?

Rogers - Long Distance Data?

Hi all,
I just got my first Data Plan and Blackberry (8900 Curve) from Rogers yesterday. I was wondering if using data outside of my local calling region (i.e. Toronto) will cause "Long Distance Data" charges? Or is there no such thing?
Cheers,
Ben

With the Canadian providers (including Rogers) Data roaming in Canada is free. So from Victoria to St Johns, there is no "long distance" as you put it for using data, regardless of the fact that you have a Toronto phone #.
When you travel outside of Canada, that's when you start paying Data roaming charges.

Data Guard Application Failover

Hi,
We've setup a physical standby database on 11.2.0.1.
I'd request for opinions on how well to manage application fail-over when we switchover/fail over the database. The application connects to the database through TNS name resolution.
Some people have suggested we edit the tns entry for the application server and point it to a virtual hostname, which will resolve to one IP address, then change this IP address only on the DNS to point to the new primary during switchover. But this looks to have challenges since the service names for the primary and standy instances are different, so the tns entry has to be modified.
Any suggestions on best application failover?
dula

Dan,
You are most welcome to OTN
I have a question regarding Active Data Guard and any potential outage that might be encounted in a failover or switchover.Switchover/Failover wont happen without your interaction.
If you configure FSFO with protection mode(Ex: Max Availability)
Read-Only application is accessing Active Data Guard database on standby. Would there be any outage if the standby were made the primary ?What outage? If standby made to primary(failover) then you may less very minor data based on how redo transport you are configuring. if you are using ARCH then the lost would only data+changes what ever in Archive log file, If you using LGWR then its very very less. So recommended to use redo transport as LGWR
I have assumed no, but there is a debate in my office that there would be a small outage due to change in roles. We are using broker also.If you change role, then there would be no outage.
For more details refer this oracle documentation http://www.oracle.com/technetwork/articles/smiley-fsfo-084973.html
Edited by: CKPT on Jan 12, 2012 4:50 PM

Requirements about delay and bandwith for using OTV in Nexus 7000 between two data centers separated 25 miles?

We have two Nexus 7000, and I need use them with OTV between two data Centers separated 25 miles, but I don´t know what are the optimal values about bandwidth and delay (ms) for extended VLANs IDs (production and DAG replication) for Microsoft Exchange environment. Can somebody tell me please which are the values required for operate OTV in optimal conditions in this case? We have about 35 000 users that will use that platform of email. Thanks a lot for your comments. Regards.

We have two Nexus 7000, and I need use them with OTV between two data Centers separated 25 miles, but I don´t know what are the optimal values about bandwidth and delay (ms) for extended VLANs IDs (production and DAG replication) for Microsoft Exchange environment. Can somebody tell me please which are the values required for operate OTV in optimal conditions in this case? We have about 35 000 users that will use that platform of email. Thanks a lot for your comments. Regards.

WAN Vlan optimization between 2 Data Centers - 4451 Router

Hello Group gurus,
I have little odd question
We have 2 Data Centers, we have dedicated 1Gig link across them. we want to optimize certain Vlan traffic across them.
we have 4451 routers installed at each location and OSPF running for end subnets to know each other. but that is routing part completed.
however how can we utilize UCSE chassis of 4451 to optimize vlan traffic across data center is still a query.
I tried to find out document on google but specific to my requirement has not seen on.
if someone already set up this type of scenario, please help.
Thanks in advance

Hi John, I think it's best to use the right equipment for the job. If you've already got a router in place and you're not in a campus/metro/ISP environment, it's not really prudent to use another router. A simple layer 2 or layer 3 switch can accomplish this and give you plenty of ports at a much better price per port.
You may want to look in to the SG300 series switch if you want something that can handle route load and give ample amount of ports.

Can you cluster Coherence over data centers?

We're currently running two separate Coherence clusters in different data centers. One is prod, the other DR.
Would it be possible to cluster the nodes from each of these to create one cluster spanning both data centers? Then in a failover scenario the data would already be available.
I know Coherence nodes heartbeat to one another to retain cluster membership and that there is a TTL setting to determine packet life. Would have nodes in different data centers result in heartbeats being missed or TTLs killing packets?
Has anyone had any success with this?

Coherence performance is related to the latency between nodes. Having one cluster spread over 2 data centers could harm performance (some timeouts could have to be changed to prevent nodes from data center A to claim another node in datacenter B is out of reach/possibly dead).
When you lose network connectivity between the 2 data centers (note i'm not saying "if you lose connectivity". It WILL happen), you're welcome into the "split brain world", each half of the grid believing the other is dead and claiming to be the "master". And thus, if you have data replicated on N nodes, the master/backups are redispatched all over each datacenter, harming performance for a few minutes (the timing depending of course on many parameters...). And of course the data will no longer be synchronized between the 2 data centers. The quorum has to be thought of, and stuff like that...
I might be wrong, but AFAIK I'd rather have 2 separate clusters. I believe 12.1 has new features to replicate data the the master grid to the DR one, I have not been through all the new documentation.

Monitor vibration over long distance ( 300m)

Hi everyone,
Currently, I have a project to monitor vibration (16 IEPE channels) from a station that is more than 300m away from monitoring station. Looking at NI's products, I have a few options:
1. Using ENET-9234:
- Only 4 channel/module. I need to use 4 modules in total, and need to connect to a router.
- Ethernet distance is limited at 100m. To reach 300m, I need to use at least 2 repeaters, which are not suitable for my project (off-shore environment)
2. Using MXI-4 with Fiber Optic: PXI-8336
- Maximum allowed distance is 200m.NI recommend to add another segment (i.e. add another PXI chassis in between) to extend range to 400m. Or use optical converter to convert between multi-mode fiber to single-mode fiber to extend range
http://digital.ni.com/public.nsf/allkb/C86BF63CC73C6721862575F2005A246D
These recommendations are not suitable either due to harsh contion in the sea and difficult maintenance.
3. Last option is acquire and process data at the site. Then transfer only processed data back to monitoring station over GPIB or RS-485.
I would like to seek your advices on these options. Is there any way to avoid the repeaters in between?
If you have any other ideas, please kindly let me know.
Thank you very much!
Have a great week ahead!
PQH

I also like the cRIO approach. There are copper to fiber media converters on the market that offer single mode fiber which is what you would need for the longer distance.
Check out the following tools to help you get up and running quickly with cRIO:
This listing is an attempt to list and briefly describe core tools that speed the development of waveform acquisition and analysis applications on the CompactRIO and RT platforms.
NI CompactRIO Developers Guide: This is a core developer's guide for a wide range of waveform acquisition and analysis applications. It provides useful background on CompactRIO and control applications in particular. It has chapters on waveform acquisition as well as deployment and management of applications on CompactRIO.
http://www.ni.com/compactriodevguide/
Reference Applications for cRIO Waveform Acquisition: This is the core template for acquiring waveforms for analysis, including vibration, electrical power, and structural monitoring. It makes a great starting point for waveform applications on cRIO.
http://zone.ni.com/devzone/cda/epd/p/id/6206
cRIO Reference Designs for Structural Health Monitoring: This reference builds on the waveform acquisition reference and adds scan engine for slowly changing signals as well as TDMS data logging on event.
http://zone.ni.com/devzone/cda/tut/p/id/9851
Simple Messaging Reference Library (STM): This tool provides a TCP/IP communications protocol which is used in the benchmarks shown on the waveform acquisition reference page. It is an excellent tool for efficient communications between cRIO and a host, easily supporting time waveform live streaming.
http://zone.ni.com/devzone/cda/epd/p/id/2739
Reference Library for Converting Between LabVIEW and XML Data (GXML): This reference provides a remote XML configuration tool, to be used for remote configuration of the cRIO LabVIEW application.
http://zone.ni.com/devzone/cda/epd/p/id/6330
LabVIEW Syslog Protocol Reference Library: This reference offers a UDP cRIO status monitor to indicate to the host the operational status of the remote cRIO
http://forums.ni.com/ni/board/message?board.id=Components&thread.id=51
Reference Applications for cRIO Order Analysis Using a High Speed Tach: This reference offers tachometer or encoder interpretation in FPGA when the I/O device is in a separate and higher speed loop.
http://zone.ni.com/devzone/cda/epd/p/id/6301
DSA Module Synchronization Reference Design for Multiple cRIO Chassis: This reference is useful when the timing of I/O needs to be tightly synchronized between two cRIO chassis. It works with a signal line, as well as with GPS.
http://zone.ni.com/devzone/cda/epd/p/id/6146
Additional NI Systems Engineering Components are listed here: Additional tools can be found on the Systems Engineering Components discussion forum.
http://forums.ni.com/ni/board?board.id=Components
Hope this helps you get started with cRIO, which is a great choice for industrial oil platform applications for temperature, and Class 1 Div 2 certifications.
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

ORACLE8 OPS 환경에서 FAILOVER SETUP 방법(TRANSPARENT APPLICATION FAILOVER)

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
ORACLE8 OPS 환경에서 FAILOVER SETUP 방법
========================================
SCOPE
Standard Edition 에서는 Real Application Clusters 기능이 10g(10.1.0) 이상 부터 지원이 됩니다.
Explanation
oracle 7 ops (sqlnet v2.3.x 이상)에서는 fail로 인한 failover 지원이 manual
하게 reconnect를 하도록 하여 지원이 되었다. <bulletin 11033 참고>
이는 sql*net기능을 사용하여 connection time failover 기능을 사용하는 경우이다.
하지만, oracle 8 이상 에서는 automatic reconnection이 가능하게 되었다.
즉, run-time failover가 가능하다.
이는 일단 connection이 이루어진 후에 발생하는 모든 failover는
Transparent Application Failover 코드에 의해 처리된다.
다음은 Oracle 8 TAF(Transparent Application Failover) setup 방법이다.
tnsnames.ora file에 다음의 parameter를 지정하여 가능하다.
1. failover_mode : run time 시에 failover가 가능하게 한다.
2. TYPE (Required) : failover 후의 operation을 지정한다.
SESSION - failover 발생 시 새로운 session이 다른 instance에
reconnection되며 이전 session에서의 모든 uncommit된
작업은 rollback 된다.
select도 이어서 진행되지 못한다.
SELECT - failover 발생 시 새로운 session이 다른 instance에
reconnection되며 이 때 long query나 복잡한 query 등의
작업 수행 시 작업이 이어서 진행된다.
단, dml 작업은 rollback된다.
NONE - This is the default. No automatic failover
3. METHOD : 어떻게 failover할지를 지정한다.
BASIC - failover 발생 시에 backup instance(server)로 다시 접속한다.
PRECONNECT - primary instance와 backup instance 두 개에 모두
connection 맺어 놓은 후 failover 시에 backup
instance를 통해 service한다.
***< 중요 > 현재 PRECONNECT는 최소한 8.0.5는 되어야 하며
BASIC은 8.0.6이나 8.1.5에서만 가능하다.
4. BACKUP : failover 시 접속할 instance의 정보를 기술한다.
tnsnames.ora의 alias name을 기술한다.
Example
다음은 tnsnames.ora file의 example이다.
< example 1 >
=========================================================================
node1.WORLD =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(Host = node1)(Port = 1521))
(CONNECT_DATA = (SID = SID1)
(FAILOVER_MODE = (BACKUP = node2)
(TYPE = SELECT )
(METHOD = PRECONNECT))
node2.WORLD =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(Host = node2)(Port = 1521))
(CONNECT_DATA = (SID = SID2)
(FAILOVER_MODE = (BACKUP = node1)
(TYPE = SELECT )
(METHOD = PRECONNECT))
========================================================================
< test 1 >
1) 각 node의 instance를 start한다.
2) 각 node의 listener를 구동한다.
node1% lsnrctl start lsnr_node1
node2% lsnrctl start lsnr_node2
3) node1에서 다음의 작업을 한다.
sqlplus scott/tiger@node1
SQL> select count(*) from emp;
COUNT(*)
14
4) Node1에서 instance를 shutdown abort한다.
5) 3번의 session에서 select를 다시 한다.
SQL> select count(*) from emp;
ERROR at line 1:
ORA-25404: lost instance
다시 select한다.
SQL> select count(*) from emp;
COUNT(*)
14
Data가 node2 instance를 통해 제대로 select되며 이는 failover가 정상적으로
작동됨을 알 수 있다.
< example 2 >
다음은 TAF(Transparent Application Failover) 기능에 SQL*NET의
connection time failover 기능을 추가한 경우이다.
========================================================================
node1.WORLD =
(DESCRIPTION_LIST =
(DESCRIPTION = (ADDRESS = (PROTOCOL= TCP)(Host= node1)(Port= 1521))
(CONNECT_DATA =(SID = SID1)(SERVER=SHARED)
(FAILOVER_MODE = (BACKUP = node2)(TYPE=SESSION)(METHOD=PRECONNECT))))
(DESCRIPTION =(ADDRESS = (PROTOCOL= TCP)(Host= node2)(Port= 1521))
(CONNECT_DATA =(SID = SID2)(SERVER=SHARED)
(FAILOVER_MODE = (BACKUP = node1)(TYPE=SELECT)(METHOD=PRECONNECT))))
node2.WORLD =
(DESCRIPTION_LIST =
(DESCRIPTION =(ADDRESS = (PROTOCOL= TCP)(Host= node2)(Port= 1521))
(CONNECT_DATA =(SID = SID2)(SERVER=SHARED)
(FAILOVER_MODE = (BACKUP = node1)(TYPE=SESSION)(METHOD=PRECONNECT))))
(DESCRIPTION = (ADDRESS = (PROTOCOL= TCP)(Host= node1)(Port= 1521))
(CONNECT_DATA = (SID = SID1)(SERVER=SHARED)
(FAILOVER_MODE = (BACKUP = node2)(TYPE=SELECT)(METHOD=PRECONNECT))))
=======================================================================
< test 2 >
1) 각 node의 instance를 start한다.
2) 각 node의 listener를 구동한다.
node1% lsnrctl start lsnr_node1
node2% lsnrctl start lsnr_node2
3) node1에서 다음의 작업을 한다.
sqlplus scott/tiger@node1
SQL> select count(*) from emp;
COUNT(*)
14
4) Node1에서 instance를 shutdown abort한다.
5) 3번의 session에서 select를 다시 한다.
ORA-25404 error조차 없이 select된다.
SQL> select count(*) from emp;
COUNT(*)
14
Data가 node2 instance를 통해 제대로 select되며 이는 failover가 정상적
으로 작동됨을 알 수 있다.
(참고 1) dedicated 방식의 경우는 shared 대신에 dedicated를 기술한다.
물론 initSID.ora의 mts를 기술하지 않고 tnsnames.ora의 server option을 쓰지
않으면 default로 dedicated 방식을 쓴다.
(참고 2) example 1을 사용할 경우 session 종료 후 재접속 시 자동 failover가
되지는 않는다.
Reference Documents
oracle8 parallel server concepts & administration manual

Hi,
Many Thanks for your inputs. I created 2 non default listeners LISTENER_ORCL1 and LISTENER_ORCL2 on each node respectively.
I was able to set LISTENER_ORCL as remote listener. But for some reason, the local_listener does not get set. The statement is executed successfully but no changes in the parameters and TAF setup does not work. I initially had the default port number of 1521 for the listener but then changed it to 1522 (to test if it had something to do with default port no) but still no success.
SQL> show parameters listener
NAME TYPE VALUE
local_listener string
mts_listener_address string
mts_multiple_listeners boolean FALSE
remote_listener string LISTENER_ORCL
SQL> alter system set local_listener='LISTENER_ORCL1' SCOPE=BOTH SID='ORCL1';
System altered.
SQL> alter system set local_listener='LISTENER_ORCL2' SCOPE=BOTH SID='ORCL2';
System altered.
SQL> show parameters listener
NAME TYPE VALUE
local_listener string
mts_listener_address string
mts_multiple_listeners boolean FALSE
remote_listener string LISTENER_ORCL
Help Plssssssssssss!!!!!!!!

IP mobility solution for a Data Centers

Hello guys
Please give me an advice.
Now I try to work out a networking solution for a two geo separated data centers (DCs).
Both the data centers will contain a virtualised server infrastructure (VMware).
Now the main design problem is to choose good solution for IP mobility and for the DCs interconnect. We need to have an ability of moving a VM machines both for maintanance and for disaster recovery between the DCs. And users must seamlessly without any advanced knowledge about routing be connected to the VM machines that were moved. For now the users work in 1100 different offices around the Ukraine country.
Yes I know a little about Cisco OTV, RHI and LISP solutions. But all this solutions require the top level switches and routers like Nexus 7000 and Cat 6500. And they are very costly.
Is there cheaper solution for the IP Mobility?
Maybe the NHRP protocol that is a part of the DMVPN could be a good solution?
Are there any features in NHRP or in other protocol for monitoring the health of a VM machine, customising and propagation the routing info in case of VM machine motion?
Thank you for help.

Hi Lavanya,
Required data from a legacy system(generate data only in the form of flat files)to SAP R3 as FB01 journals - use BDC for this thing because it will be better for large source files.
the output file should be generated periodically(daily,weekly,fortnightly etc) - if this output file contains acknowledgment for the data uploaded by the above process, create a ABAP report for it and schedule it..........but if this output contains some other IDOC data which you need to send as a file to a third-party system, then go for SAP XI provided the IDOC data is not too large... but if the IDOC size is huge, then just create a ABAP report for outputting data to a file on application server and FTP the file to third-party system.
Regards,
Rajeev Gupta

Long distance application failover between data centers.

Similar Messages

Maybe you are looking for