Netware 6.Doc

Tamara Washington

Netware 6

December 2, 2002

Because volumes are the basic components of the Net Ware file system one should intend to make them satisfy the needs of his/her current or future organization. Chapter 17 discusses volumes and the effects they have on net ware. If you are interested in learning more about volumes, continue reading. When planning Net Ware volumes simply follow these guidelines:

Volume Sys. Make Volume Sys the Net Ware system file and also make two or more volumes for ones' application and data files.

Name Space Capability. All naming space capabilities are enabled by default to help one combine file management.

Fault tolerance and volumes Only one volume per disk may be created if fault tolerance is more important than performance. The most basic fault tolerance is being able to operate in the event of a power failure. One would have to have two or more of the same system to ensure fault tolerance.

* Mirroring safeguards data by duplicating it on another disk. The disk's work simultaneously so if one disk fails the other can continue its task. Data assurance is not met by mirroring alone, because if both disk fail at the same time your data is still lost.

* Duplexing hard disks The volume may span m ultiple hard disk if you feel fault tolerance and performance are significant, although you should duplicate each hard copy to ensure data safety.

* Descriptive volume names Descriptive names would be sufficient when naming volumes (ie; if a volume will hold executives info, the volume may be named EXECS.)

Going a little further in the book I looked at identifying the contents of Net Ware SYS Directories. I found that Net Ware creates numerous directories on its SYS volume that contain NLM'S. These directories are used to run typical server and network operations. Should these directories become deleted, moved, or renamed, one would have serious problems running Net Ware.

As a network admin, one would need to understand the types of directories operated for planning a file system. There are several types of directories to be used. Here are a few directories to organize one's individual's files:

* Home directories which should be named after the user's login name and supply users with a home directory to hold user-made files

* Configuration files which makes a user-specified directory to store user-configuration files.

* Application directories which contain application program files and make security recognized. Access must be granted to a user if he/she wants to access the application file.

* Shared data directories Groups of users can share data information if a shared data directory is created. This directory may also be used to ensure data security; granting or restricting a user's rights to this directory is your choice.

Another Admin need to know is how to evaluate a directory structure. There are a small number of directory structures that are positively right or wrong. They are either changed very well or very poorly. They resemble ease of use, ease of keeping file system security, and ease of administration. Having a one- volume directory structure is possible but not recommended. Having multiple volume directories gives you the lead way of securing individual volumes and designating administration volumes to their assigned administrator.

As part of an overall strategy to make files available from anywhere to employee's iFolder is introduced. iFolder provides important benefits to your network users for locating and synchronizing the same directories and files at home, on the road, or at work. With iFolder you can access your work files from your laptop in your bedroom.

There are three parts that work together for a successful use of iFolder to manage and access your files. They are as follow: iFolder client software which can be installed on any windows workstation that you access iFolder files from. If this is installed correctly an iFolder icon will appear in the system's tray. iFolder Server Software which lets you perform administrative tasks on all your iFolder accounts. This also lets you customize your company's appearance, business needs, and emotions.

To install and configure iFolder you must understand the server and workstation requirements, how to install iFolder, and How to perform iFolder Post-Installation Tasks.

I have took the liberty of making a copy of each and every one of these instructions to perform these procedures as told in the book. If you follow these instructions installing and configuring iFolder should be a breeze considering you meet all of the requirements listed below:

To install iFolder

1. Mount the Netware 6 CD on the server

2. From the graphical console, select Novell>start

3. Select add

4. Browse to the Netware 6 volume and highlight PRODUCT.NI; then select ok.

5. Select ok again to run the product installation program.

6. From the components screen, select clear all.

7. Select iFolder storage services; then select next

8. From the Server Options Window, enter the following information:

* Secondary IP Address This configures iFolder to use a unique IP address to avoid port conflicts with other services, such as Enterprise Web Server.

* User Data. Enter the path to the directory where you want the iFolder user data to be stored on the iFolder server.

* Admin Names. Enter the names of all administrators who need rights to modify iFolder user account information from the SMC

If you are entering more than one name, separate the user names with a semicolon.

* Network Domain Enter the IP address or DNS name of your server.

* Admin's