Novell Storage Services

Previous NSS Volumes Not Automatically Upgraded

Previous NSS volumes are not automatically upgraded during the NetWare 6 installation process. After you install NetWare and reboot the server, you can upgrade previous NSS volumes to the current NSS volume layout.

Before you upgrade previous NSS volumes, you must ensure that NDS^® is up and running and that the Backlink process is complete.

To upgrade previous NSS volumes, do the following at the server console:

• To upgrade a single NSS volume, enter

  nss /zlssvolumeupgrade=volume

• To upgrade all NSS volumes, enter

  nss /zlssvolumeupgrade=all

After you upgrade all the volumes, you can use the MOUNT ALL command or mount the volumes individually.

Must Add Trustee Rights to SYS:LOGIN When Upgrading Volume SYS:

You can use the Volume Conversion Utility (VCU) to upgrade a traditional volume SYS: to the NSS volume SYS:. However, the implied trustee rights do not transfer with this method. After you upgrade volume SYS:, you must manually add a public trustee with read and file scan rights to the LOGIN directory.

Modifying a Volume's NDS Object When Converting Volumes

You can convert traditional volumes to NSS volumes after you upgrade to NetWare 6. The following is an example of using the volume conversion utility (VCU) when you want to modify the volume's NDS object:

vcu TRAD NSSPOOL provo_tree\novell\provo ds_poolname ds_volName

DS tree: provo_tree
DS context:provo.novell
DS NSSPOOL name: ds_poolName
DS TRAD name: ds_volName

Do Not Create Traditional Volumes Still in Clusters

After you upgrade the first server in a cluster, the shared NSS volumes might appear as free space in a traditional partition on the remaining NetWare 5 servers. Creating a volume in this space will corrupt the NSS volumes. For more information, see Novell Cluster Services.