Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 914
  • Last Modified:

Network link for data replication between Primary and Disaster Recovery Datacenters

We have a requirement of 20 Mbps bandwidth pipe between PDC and DR sites.
Highlevel design on my mind:>
PDC and DR shall be provided with two links of 10 Mbps each between them which shall be configured in load sharing mode to cater a 20 Mbps requirement.
>A pair of Juniper 4350 series routers@ PDC and a pair of Juniper 2350 routers @DR are setup in a load balanced mode to provide a dedicated  20 Mbps bandwidth between primary and Disaster Recovery sites. This link shall be used only for the data replication purposes
>All the routers shall be active. routers have only ethernet interfaces and no WAN cards.
My questions:>
What is the simple way i can connect these 2 sites? I am looking for a leased line...Can i use the Ethernet ports and connect using Metro ethernet wire services? What is the simplest protocol i can use here? pls suggest any other technolgy which is simple and provide point to point communication.
0
daya83753
Asked:
daya83753
  • 6
  • 4
  • 2
  • +3
1 Solution
 
mateojaime07Commented:
does your juniper routers have the ability to BGP?
0
 
daya83753Author Commented:
Yes.  j4350 and j2350's support BGP. Can support upto 32 BGP instances.
0
 
mateojaime07Commented:
we have been looking at a similar situation for our VMWare DR solution. We have been considering 2 60 MB sonet ring connections with a metro E connection through TW Telecom. We would use BGP to route to the DR site and/ or use point to point VPN tunneling. not sure if this helps any. Are you using VMWare?
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
itubafCommented:
Dear you have many options, like

A)if your DR site located near (less than 40-100KM) your Primary site you can use wrireless WAN (Motrolla. Redline...)
this will be cost effective and high perfiormance solution, one time cost and you get upto 300MBPS speed on air (Motrolla PTP600)

B) if yous sites are in a same country request your ISP to provide you PTP connnection
this can benfit you that no need for any firewall configration, ISP will provide you modems/routers connected to each other

c) if your DR not located in country and you want to use VPN,
-->you can order Leasline and connect with WAN1 of each juniper
-->Take one more line if you require internet for office users.
--> create routes for internet Source (ANY), Destination (ANY), Service (ANY or HTTP, HTTPS, as per your desire), Gateway (Internet-Line-Router), Interface (your router interface connected to Internet router), Metric 20, Priority (as per Config).
-->try to use DH Group 5.

 
0
 
daya83753Author Commented:
i like option B. but we have already procured te J2350 and j4350 routers. We did not purchase any WAN interface cards. I am looking for options to use the existing ethernet ports on the routers for a point to point connection. What underlying routing technology we should opt for?
0
 
itubafCommented:
it depend what data you want to send, i have one primary and two DR and my data contains, office application, office files/emails and Veritas Storage foundation i created simple VPN and no specific routing protocol configured. its work fine.
0
 
itubafCommented:
for OPTION B, ISP will take care of everything you just need to provide them 2 spare IP addess on each site, what i wrote above is for VPN or option C.
0
 
daya83753Author Commented:
It is storage replication and database logshipping i have to take care of using this link. i am more worried on the WAN interfaces i have to procure for a PPTP connection. My question is the ethernet interface fine in this case?
0
 
itubafCommented:
if your ISP is ready to provide you PTP connection (Point to Point) than ISP normaly will provisde you router and handle routing protocols as well, you dont need to do anything except providing them two IP for router LAN, WAN side they will take care.

if your ISP is providing only PTP lease line with out router you can check with ISP what Modem ISP will provide to you (PTP can be provide only is two options 1) with router, 2) with Modam), some ISP request V.35 connection with their modams so please before you order any WAN card for your juniper/ or any device make sure ISP  Modam support your WAN card.

one thing is common in both senarios you dont have to go for a specific routing protocol in PTP line or VPN connection.
0
 
itubafCommented:
as i said above, ISP can only tell you what interface you may require.

if ISP provide you modam than
1)you may require V.35 cable and serial card for juniper, .
2) you can use router Cisco Router ehthernet port if ISP modem has Ethernet connection.

If ISP Provides you Routher then,
1) you will provide tham 2 spare IP on both sides and two patch cords and connectivity to core switch
 
0
 
djcaponeCommented:
Hi,

Option B is probably your best, most cost effective solution, especially if both datacenter sites are on-net.

Often times (and in your situation, I would recommend), Point to Point links are setup with layer 2 connectivity.  As such, there would be no need for routing of any kind, as the connections can go directly into your switches.  This may not be the case if you are on-net and the connectivity is a SONET/TDM solution, as opposed to on site, where you would most likely get a Fast/Gig Ethernet handoff.

Additionally, I would question your need for multiple Point to Point links between sites.  Bandwidth pricing scales dramatically as your bandwidth increases.  You could end up paying $1500+ for a 10 Mbps solution per carrier, if a carrier would even offer a solution at that low of a commit for point to point Ethernet connectivity.  Depending, on what 2 locations your connecting, you could get a 100 Mbps connection for under $2000 a month.  You would save money and ensure high speed connectivity between your Primary and DR site.  Furthermore, if your primary site experiences a failure where you need to turn up services at your DR, whether you have one or 2 links would not matter.  The only thing a second Point to Point link would be protecting you from is a failure of the Point to Point circuit followed almost immediately by a Primary site failure where you would experience running on "old" (maybe 30 minutes tops, as most circuit outages would not last longer than that, so the failure followed by the failure would need to happen in a short window) data.  the chances of an event like this are extremely rare.

Also, you do determine that multiple Point to Point links are required, I would obtain route maps from the carriers to ensure that the 2 links you are purchasing take diverse routes.  The benefit of having redundant links is greatly diminished when the fiber your data travels over is buried in the same conduit.

My 2 cents....
0
 
djcaponeCommented:
Correction to my previous post....

Layer 2 Point to Point connectivity is often available On-Net....It is OFF-Net where you may be forced into some type of Layer 3 situation, but even then most carriers can configure a layer 2 solution for you.
0
 
eeRootCommented:
There are a few ways of doing this, 2 common methods would be to use metro-ethernet or MPLS.  The config isn't that complicated, and you can get service providers that setup and manage/monitor the connections for you.
0
 
Craig BeckCommented:
I've just done this kind of setup with LAN extensions (Layer 2).  You could connect the sites using a L3 switch at each end and configure an EtherChannel between the two.
The best way would be to ask your ISP to do this as a managed service.  That way you only have to worry about configuring your own firewall at each end, for example.
Unless you run a fully redundant switched network at each site there's little argument for using a dedicated router/L3 switch per link either as you would have a single point of failure at the switch where the routers connect at each site.
0
 
itubafCommented:
Dear, as i you mention above your requirment is SAN replication, better you go with Option B. Option B will little expensive but you will have better performance and less hastle.

ordering 2 PTP lines will not benefit you, as if you want SAN replication i am sure you will be using a replicator, this would be very difficulty to transfer DATA using "synchronous or asynchronous" to one host using different gateways. and if you use Active/Passive than why you will bear cost of 2nd line

i suggest you order PTP line with ISP, ISP will connect your SITE A and SITE B , and these lines will work like Bridge or routed bridge. you may no need to worry for security as these lines will be connected with directly. you can slect your local country largest ISP for this purpose, but for redundancy purpose you can order one 4-6MB lease line (internet line) on both sites  through diffent ISP and configure VPN and enable STP on any site switch. enabling STP will help you if PTP line down the data will transfer using VPN on temporary base till ISP resolve line issue.

Cheers

0
 
daya83753Author Commented:
thanks.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 6
  • 4
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now