[Contents] [Back] [<< Prev] [Next >>]

File Transfer

Without a network, the options for transferring data between computers are limited. You can, of course, exchange files on floppy disks. This process came to be called “sneaker-net” because it consisted of networking by physically running around and hand-delivering floppy disks from desk to desk. Otherwise, you can use communication software to dial another computer and transfer files via a modem or a direct serial connection. With a network, users have constant access to high-speed data transfer without leaving their desks or dialing anywhere. Moving a file is as easy as depositing it in a shared directory.

When users transfer confidential files, the need for network security rises. You might need to limit file transfers to authorized users who are using password-controlled security systems, to assign file attributes that restrict the operations that may be performed with a file, or to encrypt files so they may be read only by authorized users. Each of these options is possible with networking.

Another important file-management task of the NOS is to provide and regulate access to programs and data stored on the file server’s hard drive, which is known as file sharing. File sharing is another main reason companies invest in a network. Companies save money by purchasing a single network version of an application rather than many single-user versions. Placing data files created by employees on a file server also serves several other purposes, such as security, document control, and backup.


[note.gif]

One of the most difficult facts to convince your network users of is that their data is actually far more secure on the network file server than on their own workstation. The reasons for this are numerous, but they center on the fact that network servers are backed up more regularly and have more sophisticated authentication and permission structures than most workstations. Perhaps most important, servers generally are locked away and are not as vulnerable to physical damage or theft.

Centralized document control can be critical in a company where a document might need to be revised several times. In an architectural firm, for example, the design of a building might be created by using a drafting program, such as AutoCAD. The architects might produce several versions of the building plan as the client comes to a decision. If the plan is stored on the individual computers of each architect, the firm might not know which is the most recent version of the plan. The wrong version might have a more recent date (because of a backup, for example). If the plan is saved on a file server, however, each architect can work on the same file. The file sharing is regulated by the operating system.

A tape backup should always be installed on the network, forming the heart of a centralized backup strategy. All files located on the network can be backed up regularly. This strategy is much safer than relying on individual users to back up their workstations and can be more easily managed and controlled by the administrator.