1
Solution Sheet
Overcoming the WAN
Limitations of CIFS, NFS,
FTP, and Xcopy
Accelerating the Performance
of Centrally Managed File Services
It is a challenge to maintain synchronized
les across a distributed enterprise. In
addition, it can be costly to deploy and
manage le servers in remote and branch
ofces. As a result, most enterprises prefer
to centralize enterprise le servers.
However, inherent limitations exist in
existing protocols, le sharing applications,
and WAN technologies that make it difcult
to provide le services across a WAN.
This is true across most le sharing
technologies, which include:
• The Common Internet File System
(CIFS) protocol, which is used by
Microsoft
®
le systems. CIFS is a
particularly “chatty” protocol, which
limits its performance across networks
with high latency. Every time a le is
transferred using CIFS, for example, it
is methodically broken down into small
blocks (4 KB to 64 KB). Each block
is sent individually by the le server,
requiring an acknowledgement by the
client before the next set of information
can be transferred. This often results in
signicant latency across a WAN.
In addition, because CIFS uses TCP as a
transport protocol, it is subject to normal
TCP back-off procedures during periods
of congestion. This often adds even
more latency across the WAN, further
debilitating application performance in
many enterprise networks.
• Network File System (NFS), a
common le sharing application used
by UNIX le systems. Unlike Microsoft
CIFS, the underlying NFS protocol can
use either UDP or TCP as a transport
mechanism. Therefore, it does not suffer
from performance limitations that come
with TCP backoff. However, NFS is a
relatively chatty protocol, which makes it
difcult to deliver this application across a
Wide Area Network (WAN).
• File copy utilities, like FTP and Xcopy,
are used to batch copy or transfer les
between multiple locations, often as part
of regular backup or disaster recovery
programs. XCopy operates on top of the
Microsoft CIFS protocol, and therefore
suffers from the same limitations as
other CIFS applications. FTP, on the
other hand, does not rely on a chatty
protocol, like CIFS. However, because
it operates over TCP, it is still limited by
the bandwidth and latency constraints of
many enterprise WANs.
When limited bandwidth is coupled with
high latency (100ms or greater), packet
loss, and TCP delays, as is the case on many
enterprise WANs, it becomes difcult to
deliver le services effectively. Fortunately,
Silver Peak is able to overcome the
limitations present in most le applications
through protocol acceleration, compression,
and advanced data reduction techniques.
Data Reduction Using
Network Memory
Silver Peak appliances use Network
Memory
™
to reduce the amount of
repetitive information that is sent across
the WAN when performing le access and
storage. Depending upon the type of le
being transferred, this can lead to enormous
performance improvements — 60x in some
instances (see Figure 1).
Silver Peak’s Network Memory is
bidirectional. Once content traverses a
WAN in one direction, the patterns are
stored in each appliance. Future transfers
in the opposite direction are immediately
accelerated, enabling Silver Peak to offer
amazing performance with exceptional
scalability. As Figures 2 and 3 show, this
capability provides signicant benet
across different methods of le transfers.