Mirrors/Global FTP Servers (Smart FTP Net)

Summary: Mirror (globally distributed) server functionality can be extended to build multi-user private virtual WAN. Smart Database Management software combined with the under $5K low end NT servers delivers appropriate solution to the small business and the emerging global markets.

Environment:

Mirrors - Internet Server replication.

Main purpose of the mirrors is to provide fast local access and content delivery customized to the region market. The series of servers involved in the direct access is reduced to one or two - reducing potential server to server traffic congestion. If one mirror fails, the next down the road is substituted.

Mirrors should be in countries with the low cost and modern telecommunication infrastructure, and easily accessible to the adjacent markets.

Most of the business information (databases, faxes, voice mail, graphics, multimedia etc.) when transported globally throughout the different times zones are using simplex protocol (one way upload or download). The desired time delivery scale is in hours, once the data are loaded to the local server then the forwarding could be orchestrated by the network.

E-mail attachments can be used, but the data volume is limited, and the data transfer is not very efficient (data replication, compression, encryption is NOT often used).

Problem:

FTP (File Transfer) - upload/download of mega bytes size files between the continents could be a frustrating task because:

1. Up to half of dozen of servers need to be on line and running
2. The speed is at the "slowest" link
3. If any segment fails, the transfer must be repeated
4. Voice mail and fax delivery using the telephone network are very expensive
5. Express mail is economical but slow (2 - 5 days) - customs and bureaucracy is involved
   

Solution:

• Build the virtual net (mirror servers) on the top of the existing global and "free" Internet infrastructure
• Develop FTP agent software
• Automate/convert the transfer from synchronous to asynchronous - only local server is involved in the first leg of the FTP transfer.
• Set series of host servers (switches - virtual net) to optimize the path and delivery time
• Increase the network robustness/fail-tolerance via the redundant servers/routes. If one server fails, the alternate route to bypass this node is available if needed.
• Clients download/upload data to their "local" server via FTP, Internet Phone, e-mail attachments (each server has large data storage).
• Technology (AI rules, replication DB, scheduling servers) and engineers building the infrastructure are available.
• Each transfer is validated via the independent feedback path to the sender aka e-mail, etc. when the transfer is completed (UPS like information tracking utility).

Prague to Seattle Case Study/Cost estimate:

The virtual net runs on the top of the Internet

The servers are strategically co-hosted at the ISP closest to the client - the cost and bandwidth differs

($????/month in Prague, $????/month in Amsterdam (or any direct Europe to USA link)

($300/month T3 access in New York, $500/month T3 access in Seattle)

System cost (HW/SW) starts at $8000 per server (Dual Pro 200MHz, 64Meg RAM, 4 GIG RAID, IIS/NT, Backoffice (SQL6.5, Exchange Server)

Each document transfer/virtual link has associated attributes - business rules -urgency, time window, where and how to deliver, security, authentication, delivery confirmation, etc..

Future extensions

This trans-time zone trip starts with the local Internet access - Internet terminal could be extended to phone (fax) - TAPI integrated into Internet Server. The new JAVA based devices could also replace the traditional PC based Internet access.

Simplex communication assumes that the delivery time delay is acceptable - the objective is to transfer large stream of data in secured and guaranteed mode at the fraction of the traditional telecommunication cost.

E-mail, phone, teleconferencing, chat, news is used in parallel to work with the distributed data on the local disk.

Groupware integration - open the chat mode and local document - using cut and paste to edit on-line.

Limitations

This model is limited to asynchronous delayed transfer only

The legal/intellectual/custom issues are not considered

The client/server link is only partially solved

What happens if European Community or others start to charge ?? cents per megabyte transfer

Conclusion:

Distributed computing server architecture is used on the Internet to facilitate large global data transfer. This time consuming and costly process is optimized to enable even small business in regions with substandard communication structure to be a part of the global economy. Servers can support all other Internet functions at the same time. The data forwarding is a background process. We can initiate the process with our server in Seattle. We need additional servers to cooperate.