Novell Storage Manager 2.0-SR3 README.txt
This maintenance release of NSM 2.0 is a complete install package which includes
the original NSM 2.0 plus the following updates:
FSFENGIN.NLM version 2.00.35
FSFEVENT.NLM version 2.00.15
NSMAdmin.exe version 2.0.2733.23360
This install package can be used for:
-New installations of NSM 2.0 eDirectory Platform
-Upgrades from File System Factory 1.x
-Upgrades from Novell Storage Manager 2.0
If you are upgrading from File System Factory 1.x, please see
http://www.storagemgr.com/nsm20/docs/upgrade
If you would like to use this package to upgrade an existing NSM 2.0
installation, PLEASE READ THE UPGRADE PROCEDURES LISTED BELOW.
--------------------------------------------------------------------------------
Novell Storage Manager 2.0 SR3 eDirectory Platform README.TXT
April 11, 2008
*****************************************************
* IMPORTANT !!! *
*****************************************************
This version of Novell Storage Manager now includes initial support for Unicode
characters in file and directory names underneath managed storage locations.
For details on what this means, please visit:
http://www.storagemgr.com/nsm20/support/faqs/unicode
Because of the increasing need to manage files and directories with Unicode
naming, please be advised of the following requirements for installing or
upgrading to this version of Novell Storage Manager:
1. This version of the NSM Engine only runs on NetWare 6.5 sp2 or later.
This provides basic management of file and directories with Unicode
naming.
2. For enhanced management of Unicode-named files and directories under
managed storage paths, the NSM Engine must run on NetWare 6.5 sp6 or
later. For information on the difference between basic and enhanced
Unicode support, please visit
http://www.storagemgr.com/nsm20/support/faqs/unicode.
3. Servers running FSFEVENT.NLM with Sentinel enabled should be running
NetWare 6.5 sp2 or later for basic Unicode support, or NetWare 6.5 sp6
or later for enhanced Unicode support. Although Sentinels may run
on previous versions of NetWare, it is not recommended as issues with
Unicode naming may arise.
4. Servers running FSFEVENT.NLM with only Event enabled may still run
on any of the supported NetWare Event Monitoring platforms listed at
http://www.novell.com/products/storagemanager/sysreqs.html.
New Install:
If this is a new installation, simply run the NSM2.0-eDir-SR3.exe install
package and follow the steps presented to you.
Upgrade Procedure:
This version of NSM only ships as a complete install, and does not ship as
separate upgradable NLMs. Due to the need for both the Engine and the
Sentinel NLMs to be upgraded at the same time on the Engine server, it is
important that you follow the steps listed here, and not try to simply
copy the NLMs onto target servers.
1. Backup the existing NSM installation directory (typically SYS:\FACTORY)
on the Novell Storage Manager (NSM) Engine server. Do not remove or
rename the existing installation directory, as the existing DBASE and
configuration files are needed for continued operation after the upgrade.
2. Run NSM2.0-eDir-SR3.exe. This will run through the entire install process
and will copy the newer versions of all the installation files including
FSFENGIN.NLM and FSFEVENT.NLM to the installation directory. Please be
sure to point to the same directory where NSM was originally installed.
The installer does not overwrite or remove any of the configured policies,
NSM database information, or configuration files. Some changes to non-
critical files, such as files in PROXYHOM, will need to be copied back
once the upgrade is complete.
*** IMPORTANT***
Please note that this upgrade will not copy any files or upgrade the
FSFENGIN and FSFEVENT NLMs if the existing Engine server is not running
NetWare 6.5 sp2 or later.
3. After the initial file copy is complete, you do not need to continue with
the configuration utility which sets up the license file, the schema
extensions, and the proxy accounts. Please note that these instructions
are for this particular upgrade only, as schema extensions or other changes
may be required in future upgrades.
Also, please note that if you do continue with the configuration utility,
the previously configured proxy accounts should show up as grayed out--
this is to prevent changes from the original configuration.
4. Unload / reload FSFENGIN.NLM on the NSM Engine server, or restart the
NSM Engine server. If using the configuration utility, this step will be
done for you in the last stage of the utility.
5. Upgrade FSFEVENT.NLM on all distributed Event monitors and Sentinel
servers:
a. Event Servers
1) Start the NSMAdmin.exe management utility and login to the NSM
Engine
2) Navigate to "Manage Engine" -> "Event Servers"
3) For each server in the "Event Server List," right-click on the
entry and select "Upgrade NLM"
b. Sentinel Servers
1) Start the NSMAdmin.exe management utility and login to the NSM
Engine
2) Navigate to "Manage Engine" -> "Sentinel Servers"
3) For each server in the "Sentinel Server List," right-click on the
entry and select "Upgrade NLM".
*** Note *** The option to "Upgrade NLM" for Sentinels is only
available with NSMAdmin 2.0.2489 (included in this package) or
later. If using an older version of NSMAdmin, please upgrade
to the current version of NSMAdmin to complete this step.
6. Copy back any modified files in your backupfrom the following directories:
- FACTORY\PROXYHOM
For a complete list of upgrades and fixes for the files included this release,
please read ReleaseNotes.txt included with this archive, or visit
http://www.storagemgr.com/NSM20/update/nsm-edir-update-history
