Using P2P as backup internet and SAN Design

[ankitohc]

Team,

I have two questions-

1. Question (Centralized SAN Design):
We have multiple sites, and each site currently has its own SAN (e.g., Virginia to Pocatello, or Mexico). Now we're considering eliminating the local SANs and creating a centralized hub — for example, making Virginia the data center for all sites. We already have SD-WAN (Meraki) in place.
Is it really worth going with MPLS (Layer 3) or Metro Ethernet (Layer 2) to reduce latency, so users won’t face performance issues?

2. Question (P2P as Internet Backup):
Can we utilize a point-to-point (P2P) link as an internet backup? For example, if we have only one ISP at a site and that ISP goes down, can we use the P2P link to route internet traffic through another site that still has internet access — so we don’t need to maintain a second internet connection?

Ankit

[Joseph W. Doherty]

#2 Generally, yes.

NB:  I know none of the specific capabilities of Meraki's SD-WAN.

#1 MPLS or MetroE vs. what?  The SD-WAN?

If the latter, as the goal of SD-WAN is to obtain the best WAN performance over whatever WAN is being used, all being equal, SD-WAN is likely the better choice, but much will depend on what's actually under the covers.

For example, one immediate issue will likely be additional distance based latency.  The two technologies that often mitigate that are in-line compression and/or local data caching.  Neither is "standard" with MPLS or MetroE, but may be with SD-WAN, or easier to optionally incorporate.