This section describes steps to move data transparently between OES NetWare and OES Linux:
The following section assumes that on OES Linux TSAFS is running in the default mode of operation and is not using NetWare emulation.
If NetWare emulation mode (see NetWare Emulation Mode on OES Linux)is being used, then TSAFS on OES Linux can be treated like a NetWare backup or restore.
OES Linux TSAFS supports only the NFS name space. This is to ensure consistency of pathnames for both NSS and non-NSS file systems on the same server.
All trustees and owners of files and folders on the OES Linux NSS file system should be LUM-enabled. This enables setting trustees and owners for files and folders by NSS.
For more information on LUM-enabling users, refer to the Linux User Management Guide
For more information regarding trustee and access rights for LUM-enabled users on NSS for OES Linux, refer to the File System Management Guide
When restoring data that was backed up from a NetWare source, use the following guidelines
The NFS name space should be enabled on the source from which the backup was taken.
The backup should be restored in the NFS name space on the OES Linux server.
If trustees and owners for files and folders need to be preserved, these users should be LUM-enabled.
On restoring data to NSS volumes on OES Linux, there is no data loss. All attributes and streams that are supported on NetWare are supported on OES Linux NSS volume.
When restoring to NCP volumes under non-NSS file systems, the trustee assignments and inherited rights filters are preserved.
Both backup and restore operations use the Novell client libraries and hence require that the Novell client be installed on the server. For more information on how to install and configure the Novell client refer, Novell Client for Linux Installation and Administration Guide