In addition to the requirements in Section 5.0, Planning for DST Shadow Volumes and Policies, your setup must meet the requirements in this section.
Dynamic Storage Technology must be installed and running on the primary OES 2 SP3 Linux server. For simplicity, this section refers to this server as the DST server.
Remote NSS volumes must reside in the same Novell eDirectory partition and tree as the DST server. It does not matter if DST is also running on a remote OES 2 Linux server. The following remote server platforms are supported:
NetWare 6.5
OES 1 Linux
OES 2 Linux
Each remote server should have a globally unique hostname because the Novell Client uses the hostname when it mounts the remote volumes on the DST server.
In a remote-volume scenario, the DST shadow volume uses the following:
Primary Volume: An NSS volume that resides on devices that are seen as local drives on the DST server. This includes Fibre Channel, iSCSI, and direct-attached-storage devices.
Remote Secondary Volume: An NSS volume that resides on devices that are seen as local drives on a remote server. The remote volume is mounted on the DST server by using the Novell Client for Linux.
You need an eDirectory user name and password to use for mapping remote NSS volumes to a DST server. The user name must be assigned as a trustee with the file system Supervisor right on the remote volume. The User object must reside in the same eDirectory partition and tree as the DST server. You can create a special-purpose user identity to be used only for mapping NSS volumes, such as dstuser.
IMPORTANT:The Novell Client allows only one user login to a given remote server. If you log in to multiple remote servers in the tree, you can use the same user identity or a different one for each server.
The Novell Client 2.0 SP3 for Linux (NCL) must be installed and running on the DST server. This is done by default on OES 2 Linux. For information about using NCL, see the Novell Client for Linux Documentation Web site.
The nwlogin command is used by the root user of the DST server to log in to the remote server. You need to supply the following information:
|
nwlogin Parameter |
Description |
Sample Value |
|---|---|---|
|
Tree |
eDirectory tree name that contains the two servers. |
MYCOMPANY_TREE |
|
Server |
Hostname or IP address of the remote server. If the remote NSS volume is in a pool cluster resource, use the IP address of the cluster resource. If you supply an IP address, DST discovers the hostname of the server and uses it in the mount path on the DST server. Make sure your hostnames are globally unique so that the paths are unique on the DST server. |
server41 10.10.10.41 |
|
User Name |
User name of a user that is a file system trustee for the remote NSS volume with the Supervisor right. You can use any user name that has been configured with sufficient rights on the remote volume, or you can set up a special user for this login purpose, such as dstuser. |
dstuser antonio |
|
Context |
eDirectory context for the specified user name. |
users.context.mycomany |
|
Password |
Password for the specified user name. |
password |
The Novell Client automatically mounts the remote NSS volume as a native Linux POSIX file system. The default mount location is
/var/opt/novell/nclmnt/.Servers/remote_servername/remote_volumename
You must enable the Hidden Files view to see the .Servers folder in a file browser.
The remote_servername is the hostname of the remote server. The Novell Client creates the folder name for the remote server with uppercase characters. For example, if the server’s hostname is server41, the folder name is SERVER41. The server folder contains the NSS volumes on the remote server and any system folders for the NSS file system. However, data access is restricted to the file system rights assigned for the user name you use to log in to the remote server.
The remote_volumename is the name of the NSS volume that you want to use as the secondary volume in a DST shadow volume pair. Supply the full Linux path for the volume when you specify it as the secondary path.
If the remote NSS volume is in a cluster, use the cluster IP address of the remote pool cluster resource when you map the NSS volume to the DST server. Because NCL uses the hostname of the remote server in the Linux path for the mount point, the mount point will change if the remote pool cluster resource fails over to another node in the remote cluster.
The Novell Client for Linux mounts the remote NSS volume as a Linux POSIX file system. All access to data on the remote secondary volume is controlled by DST based on the NSS file system trustees and rights that are known to the primary NSS volume. After you create a DST shadow volume relationship, you must manage the file system trustees and file access rights only from the merged view.
In the technology preview, trustee and file system rights metadata remains with the primary volume. Only the primary volume has a copy of the trustee database file. The metadata is not pushed through the Novell Client to the remote NSS volume.
If the primary volume contains data at create time, DST applies the existing NSS file system trustee and rights settings to both the primary and secondary volumes. This is the same behavior as for local secondary volumes.
If the remote secondary volume contain data at create time, the file system trustees and rights for the secondary volume are not synchronized with the primary volume. You must set the file access rights for the data on the secondary volume from the merged view. Changes and settings on the primary volume are not pushed to the remote volume.
If the remote secondary NSS volume contains data and resides on an OES 1 Linux or OES 2 Linux server, its trustee and file system rights metadata is stored in the ../._NETWARE/.trustee_database.xml file at the root of the volume. If the primary NSS volume is empty, you can copy this file to a newly created primary volume to use as the initial settings for the DST shadow volume. For information, see Section C.4, Copying a Remote Linux NSS Volume’s Trustee Database to the Primary NSS Volume.