This chapter concerns setting up Novell Storage Services, an improved version of the network file system. The objectives important to this chapter are found on page 11-1:
Concepts:
Set Up and Configure NSSNovell Storage Services is a more advanced file system than what the text refers to as the traditional file system. In previous versions of NetWare, the SYS volume was required to be a traditional volume, but it can now be an NSS volume instead. The text states that you can convert traditional volumes to NSS volumes with the VCU, Volume Conversion Utility. Note, however, that the process as described is similar to a server migration: you are actually copying the data from a traditional volume to a logical NSS volume. It is not actually a conversion. It is safer than a real conversion process might be, since you don't have to delete the original volume immediately. VCU is run from a server console. It has several command line parameters,
listed in the text. The simplest form of use is just to enter the command,
followed by the name of the existing volume, followed by the name of the
new NSS volume. The text warns us that this command is likely to produce an error message on its results screen. This is because the traditional volume contains a hidden file, not needed by the NS volume, that is not copied to the NSS volume. On that results screen, you are asked a question.
The recommended procedure is to check for errors, and delete the original volume when you are sure the NSS copy is usable. Configuring Space RestrictionsLike traditional volumes, NSS volumes can be configured to restrict the amount of space users are allowed on them. The interface for this is accessed by running ConsoleOne, then accessing the properties of the volume object. You can add users to the list of Users with Space Restrictions. Each user can have a different space limit, if needed. The limit is entered as a number of Kilobytes, and must be a multiple of 4 KB. It is also possible to restrict the space allotted to a volume itself. Like the limitation on a user, the limit for the volume is entered as a number of Kilobytes, and must be a multiple of 4 KB. Cache BuffersAs mentioned in a previous chapter, NSS takes 60% of available cache buffers by default. This is assumed to be sufficient in most cases. You can set a maximum of 1,048,576 cache buffers. That number is not as hard to remember as it looks. It is 2 to the 20th power, the number of bytes in a megabyte. If you remember that a cache buffer is 4 KB, and multiply that times a megabyte, you get 4 GB, which is the limit on how much RAM in a server is configurable as cache buffers. You can set the number of cache buffers two ways: from Monitor, or from a console command line. File SnapshotNovell's File Snapshot feature enables backup utilities to keep separate
copies of data files each time they are saved. This feature can be enabled
for all or selected NSS volumes. The command to enable it is TTSTransaction Tracking System (TTS) is the system that was used in NetWare 4.11 to track changes in the Directory, and to back out of changes that were unsuccessful. In NetWare 5, this system was not available for use with NSS volumes. NetWare 6 has made TTS available for NSS volumes, but you must make a choice. You can use TTS with traditional volumes or NSS volumes on a specific server, but not with both. By default, it is used with the traditional volumes on a server, so it must be turned off, then turned back on for the server's NSS volumes, if you want to change over. Monitor, Manage, and Rebuild NSS Storage SpaceThe state of a volume can be viewed from the properties of the volume object, and can also be viewed from the properties of the server object that stands for the server the volume is stored on. Both methods use ConsoleOne to view the object and properties. Volumes can be mounted or unmounted (made physically available or unavailable) through ConsoleOne. Oddly, you do not do so through the volume object, but through the server object for the server that holds the volume. Another action you can take in ConsoleOne is to activate or deactivate an NSS volume, or an NSS pool. This makes the volume (or pool) logically available or unavailable to users. It is recommended to deactivate a volume before performing maintenance. You can think of deactivation as more powerful: deactivating a volume will dismount it, deactivating a pool will deactivate and dismount all volumes in it. The activate command does not mount volumes or pools. NSS pools and volumes can be deleted in ConsoleOne. If you delete a pool, the volumes in it must be considered unrecoverable. If you delete a volume, you can salvage it if you do so within the Purge Delay time. After this amount of time, the system will automatically purge the deleted volume. The default value for this time is 4 days. It can be changed, but you should note that the syntax for changing it expresses the delay time in seconds. An NSS pool can be increased in size through ConsoleOne. The text warns that you should avoid adding space from multiple devices, since this extends the risk of losing data to a device failure. If there is a problem when you attempt to activate an NSS volume, you may need to repair it before it can be used. First, check the NSS pool the volume is in for errors with the VERIFY utility. Errors are stored in a file called PooName.VLF. If errors exist, correct them with the REBUILD utility. The text notes that these functions can be performed on a traditional volume, but the command used is VREPAIR. The commands that are actually used to run VERIFY and REBUILD are: Set Up User Access to the Server File SystemThe next section of the chapter describes features new to NetWare 6 that relate to accessing files. The first is iFolder, which is a service to synchronize remote copies of files with those on an iFolder server. It requires that client software be installed on workstations, and is then accessed through a browser. This service may be most useful to someone who uses mulitple workstations in their job, and needs to have access to the most recent copy of files at all times. Information about the iFolder service, and a link to download the client software, are provided by default through a web page on the iFolder server you install on your network. The web address to access this information page is simply the IP address of the server. Similarly, the Server Management Console of the iFolder server
is found at: Note that https is used, not http. The italic portion above, as always, indicates a variable to be supplied in your own network. The text warns us repeatedly that, unlike most URLs, this one is case sensitive for the characters after the IP address. An administrator can log in to this address and manage iFolder accounts, set file space restrictions, and configure policies. Naturally, you can create and delete (remove) user accounts. However, be aware that users who have the iFolder client can recreate an account for themselves just by logging in to the server again. If you are requested to restore files to an iFolder, Novell recommends that you restore the entire folder to a new folder, then let the user sort out what they need. Both folders will need to be made accessible to the same user account. Changing a user's iFolder password is different from what you might expect. First you must make sure the user's account is not in use, then you remove the account, which removes all files stored on the server for that user. Then the user logs in again, which recreates the account and the folder, and the user copies the desired files from their workstation to the server. This procedure relies on iFolder having recently synchronized the files on the server with the files on the workstation. If this has not happened lately, the user will probably lose data. NFAP is Native File Access Protocols, or Native File Access Pack,
depending on the reference you find. The idea is that it teaches the Novell
server to provide file service without a NetWare client on a workstation.
The NetWare server will mimic the file access protocols used by workstations
on common networks. A separate installation is required for each environment:
The chapter provides in depth information on installing and configuring NFAP for Windows. The other network environments are not described in detail, probably because of the large market share held by Microsoft. This information, and similar information about the other network operating systems named is available online at Novell's web site. The next topic is NetStorage. This takes a little explanation. NetStorage is what Novell calls a gadget, a link to specific content provided by NetWare Web Access. NetWare Web Access is a Java program that runs on a server. So this method of access uses a browser to access the files on the NetWare server. This is different from iFolder in that iFolder requires a client, and NetStorage does not. Also, iFolder will synchronize files, but NetStorage does not provide this service. NetStorage is installed on a server, and is configured when installed. It can be installed as an add on service after the server software is installed. Workstations must use Netscape Navigator 4.7 or later, or Internet Explorer 5.0 or later, or Microsoft Web Folders. When installing NetStorage, you must specify the IP address or DNS name of a server that holds a Master or Read/Write replica of the partition your NetStorage users will be in. That server is called the primary server for NetStorage, even though it may not be the server where you are installing NetStorage. To access NetStorage from a workstation, the URL is similar to those
we have seen already: After logging in to the network, a user will be given a web interface to the NetWare file resources normally obtained through script based drive mappings. You cannot map drive letters to them, nor can you change the login script that serves as the source of your access. NetDrive is another new and specialized service for web access to files and folders. In this case, NetDrive does give you a drive letter, mapped to a NetWare resource. It requires a special NetDrive client, but does not require the standard Novell client. NetDrive can use any of four access methods:
There are some operating system incompatibilties to be aware of:
Some program incompatibilities are noted in the text. F-Secure and KasperSky antivirus programs may lock the workstation when using NetDrive. If using ZoneAlarm, the Internet security setting should be set to medium, or NetStorage may not work. Use the NetDrive client to create drive mappings. Once made, the mapped drive will appear in Windows Explorer, where is can be disconnected if need be. |