WAFS Frequently Asked Questions

• What platforms does WAFS support?

  The WAFS Server can run on any 32-bit Windows 2003, NAS, 2000 and XP.  We recommend Windows 2000 and above.  The WAFS Agent can run on any Windows 2003, NAS, 2000, and XP.

  Neither the Agent nor Server use significant resources, however, if you have more that 250,000 files to mirror, we recommend a 1GB main memory system (for running the WAFS Agent), unless you are already memory constrained prior to installing WAFS.  WAFS runs on 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 software needed on any machine - no restrictions or limits are imposed.

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

• How can I use WAFS?

  Deploying WAFS takes only a few minutes.  The most common way to mirror existing data is simply to select existing folders (on any NTFS drive such as SAN, RAID, or local disk such as C drive). WAFS will keep it in complete sync 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 systems, all other systems have the identical files.  Files always open, and users are always guaranteed the latest version.

  WAFS projects 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, these tools are scheduled or timed transfers.  There is no concept of real time version coherence.  Second, these tools do not project native lock coherence, so multiple users conflict on the same file.  In addition, 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, then upload the data after it is modified, and to simply have users access the files during the day.  This process is error-prone, because it is impossible to keep users in sync. WAFS is just a series of normal folders on your existing file servers at each office.  Also, upload/download tools are terribly inefficient in time and bandwidth utilization, and are usually unsecured.

• 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.