Novell Home

My Favorites

Close

Please to see your favorites.

Does Novell BorderManager support the use of NSS cache volumes?

(Last modified: 16Dec2003)

This document (10082486) is provided subject to the disclaimer at the end of this document.

goal

Does Novell BorderManager support the use of NSS cache volumes?

fact

Novell BorderManager 3.8

Novell BorderManager 3.7

Novell BorderManager 3.6

Novell BorderManager 3.5

Novell BorderManager 3.0

NSS cache volumes are not supported with Novell BorderManager

symptom

The use of NSS volumes with BorderManager FastCache can cause symptoms from cache corruption, not displaying all objects properly on web browsers, to random abends or server hangs in some cases.

fact

BorderManager FastCache was designed for optimal performance with the traditional NetWare File System (NWFS).  FastCache makes low-level calls to NWFS that allow maximum performance and scalability of BorderManager¬ís proxy-cache services.  Comparable support for additional file systems would require an all-new proxy engine.  Future releases of Novell BorderManager may make use of a cache-optimized file system such as Cache Object Store (COS).
 
Cache volumes must use NWFS for optimal performance and reliability, especially in medium to high traffic environments.
This should not pose an issue with clusters, since shared media (which requires NSS) is unnecessary for cache volumes.  Cache data is expendable and need not be redundant.

fix

Several methods of changing from NSS cache volumes to the traditional NFWS cache volumes are as follows:

Method A:
1. Backup the NSS volume in question to tape or other media.
2. Delete the NSS volume and pool.
3. Recreate the NSS pool and volume as a smaller size.
4. Create an NWFS volume for FastCache in the remaining free space
5. Restore the data to the NSS volume.
Note: If the disk is really full, use Method D instead.

Method B:
1. Use iSCSI to attach additional storage via the LAN to your server.
2. Use Novell's VCU utility (ships in NW6, also in SP4 and beyond of NW5.1) to move your NSS data to the iSCSI attached NSS volume
3. Delete the local NSS volume and pool.
4. Recreate the NSS pool and volume as a smaller size.
5. Create an NWFS volume for FastCache in the remaining free space
6. Use VCU utility to restore the data to the NSS volume from your iSCSI attached storage.
7. <Optional> remove the iSCSI volume connection.
Note: If you already have a Fiber Channel SAN, this can easily be done on the SAN instead of iSCSI. iSCSI is just a low cost, no special hardware needed, SAN built out of LAN solution.
Note: If the disk is really full, use Method D instead.

Method C:
1. To shrink a volume, you don't have to decompress it first. Portlock Storage Manager will move the blocks to a new location.  Portlock Storage Manager cannot shrink an NSS pool at this time. This feature is under development.
2. Portlock Scorpion can move data from an NSS volume to an NWFS volume. The user can create the new volume and Scorpion will copy the data over.
Note: No other vendors currently have the ability to work with NSS volumes but Portlock ( www.portlocksoftware.com )
Note: Portlock can convert NSS data into NWFS data, and also convert NWFS data into NSS data. However, for adding BorderManager FastCache, this is not what is needed (since the cache data is not persistent and can be deleted since the cache will simply re-populate it from the Internet and Web servers).

Method D:
1. Add another disk to your server for FastCache.
2. Create an NWFS partition for FastCache on this new disk.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10082486
  • Solution ID: NOVL88933
  • Creation Date: 25Apr2003
  • Modified Date: 16Dec2003
    • NovellNetWare

      BorderManager Services

Did this document solve your problem? Provide Feedback