WAFS Frequently Asked Questions

Which platforms does WAFS support?

The WAFS Server supports 32-bit and 64-bit Windows operating systems, including Windows 2000 through Windows Server 2008. Local and network storage is fully supported in order to grow with your data needs. Full details of supported and recommended system configurations are available here.

Neither the Agent nor the Server uses significant resources, however, if you have more that 250,000 files to mirror, we recommend a 3GB main memory system (for running the WAFS Agent), unless you are already memory constrained prior to installing WAFS. WAFS runs on an existing server, no matter what is already installed. Any PCs or other platforms (including Macintosh, Unix, Linux etc.) running on a LAN can access the data via network share. No extra software is needed on any computer—no restrictions or limits are imposed.

WAFS also provides automatic and secure browser access to files (and all past files and deleted files), from any location.

How can I use WAFS?

Deploying WAFS is simple. The most common way to mirror existing data is to select existing folders (on any local disk or an NTFS drive, such as a SAN or RAID). WAFS will keep it completely synchronized with a folder on any number of remote file servers at any distance.

WAFS ensures that all files are identical on all systems. No matter how rapid files change on any system, all other systems have the identical files. Files always open and users are always guaranteed the latest version.

WAFS supports native file locking in real time. No possibility of file conflicts.

What type of sharing does WAFS support?

Many users, on the same LAN and in remote geographical locations, can use the same files concurrently. The data is always fully synchronized; any change to a file at one server is immediately reflected at all other servers. WAFS extends the LAN concept over the Internet and provides real-time disaster recovery.

What is the difference between WAFS and upload/download tools like FTP?

First, those tools are for scheduled or timed transfers. There is no real-time version coherence. Second, those tools do not support native lock coherence, so multiple users risk modifying the same file creating versioning issues. Finally, upload/download tools are not integrated with the Windows file system, so a lot of manual work is needed to get the data from the server, upload the data after it is modified, and to have users access the files during the day. The process is error-prone, because it is impossible to keep users in sync. Upload/download tools are inefficient in time and bandwidth utilization, and are usually not secure. Conversely, WAFS is just a series of normal folders on your existing file servers at each office.

My organization is using VPN to connect remote sites and to enable people to connect from home. Do I need still need WAFS?

Absolutely. Combining WAFS with VPN has many benefits, including dramatically increased speed (e.g., a large file will open at hard-drive speeds), reduced bandwidth needs, and off-line access. However, since WAFS uses HTTP for all communications, you do not need a VPN.