Make sure your system satisfies the required software and configuration settings that are specified in this section.
Dynamic Storage Technology runs on OES 2 Linux (or later) servers. DST supports 32-bit and 64-bit processors. For information about installing and configuring OES 2 Linux, see the OES 2 SP3: Installation Guide.
Dynamic Storage Technology is a component of the NetWare Core Protocol (NCP) Server. NCP Server for Linux provides the NCP services for the shadow volume. NCP Server must be installed and running in order for DST to work. NCP Server also provides a merged view of the data for NCP users and applications.
DST is automatically enabled when NCP Server is running and enabled, even if there are no shadow volume pairs currently defined. There is no way to separately turn DST on or off in Novell Remote Manager for Linux or in the YaST Runlevel Editor.
For information about managing NCP Server for Linux, see the OES 2 SP3: NCP Server for Linux Administration Guide.
Dynamic Storage Technology supports only Novell Storage Services (NSS) volumes in shadow volumes. You must install Novell Storage Services and any other OES 2 services that it requires. For information, see Installing and Configuring Novell Storage Services
in the OES 2 SP3: NSS File System Administration Guide for Linux.
IMPORTANT:Some restrictions apply when using NSS volumes in a DST shadow volume. For information, see Section 5.4, Using NSS Volumes in DST Shadow Volumes.
Dynamic Storage Technology requires that access to data be restricted to users with User objects defined in Novell eDirectory 8.8.2 or later. For information about configuring eDirectory and users, see the Novell eDirectory 8.8 SP7 Administration Guide.
IMPORTANT:All users of data on the shadow volume pair must be eDirectory users. In OES 2 Linux, the server’s root user is the only local user who can access data without authenticating in eDirectory.
In OES 2 SP3 Linux (or later), Novell CIFS is supported to give CIFS users access to the data on DST volumes that are built with NSS volumes. CIFS users see a merged view of the data by accessing a CIFS share on the primary volume. For information about configuring and managing Novell CIFS, see the OES 2 SP3: Novell CIFS for Linux Administration Guide. For planning information, see Novell CIFS.
Novell CIFS is supported as an alternative to the Novell Samba solution. Novell CIFS does not require ShadowFS, FUSE, or LUM.
Novell Samba is supported as an alternative to Novell CIFS to give SMB/CIFS users access to the data on DST volumes.
The SMB/CIFS users and the Linux Samba service must be enabled with Linux User Management (LUM).
The merged view for SMB/CIFS is provided by the Shadow File System (ShadowFS) and FUSE (File System in Userspace). These components are installed automatically when you install NCP Server and Dynamic Storage Technology. For information, see Section 12.0, Using ShadowFS to Provide a Merged View for Novell Samba Users.
Linux User Management is selected and installed automatically when you install NCP Server and Dynamic Storage Technology. LUM is required if you use Novell Samba with DST volumes. For information about how to configure users and services for LUM, see the OES 2 SP3: Novell Linux User Management Administration Guide.
NCP Server and Dynamic Storage Technology support the sharing of shadow volumes in clusters with Novell Cluster Services for OES 2 Linux or later.
NCP Server and DST are not cluster-aware. They must be installed and configured on each OES 2 Linux node in the cluster where you plan to fail over DST shadow volumes.
For information about installing Novell Cluster Services, see Planning for Novell Cluster Services
in the OES 2 SP3: Novell Cluster Services 1.8.8 Administration Guide for Linux.
For information about managing cluster resources, see Configuring and Managing Cluster Resources
the OES 2 SP3: Novell Cluster Services 1.8.8 Administration Guide for Linux.
For information about configuring shadow volumes in cluster resources, see Section 13.0, Configuring DST Shadow Volume Pairs with Novell Cluster Services.
Novell Remote Manager for Linux is required for managing NCP Server services and Dynamic Storage Technology. It is selected and installed by default when you install NCP Server and Dynamic Storage Technology.
For information about managing Novell Remote Manager and using its other features, see the OES 2 SP3: Novell Remote Manager for Linux Administration Guide. For information about management options for DST, see Section 6.1, Dynamic Storage Technology Plug-In for Novell Remote Manager for Linux.
Novell iManager 2.7.4 for Linux is required for managing eDirectory users, Samba services, Novell CIFS services, Linux User Management, Novell Storage Services, and Novell Cluster Services for Linux. It is not necessary to install iManager on every server, but it must be installed somewhere in the same eDirectory tree. For information about installing and using Novell iManager, see the Novell iManager 2.7.6 Administration Guide.
You use the Storage plug-in to share devices and to create and manage NSS pools and volumes. For information, see Storage Plug-In Quick Reference
in the OES 2 SP3: NSS File System Administration Guide for Linux.
You use the Clusters plug-in for Novell iManager to manage the DST shadow volume cluster resource, load script, and unload script. For information, see Configuring and Managing Cluster Resources
in the OES 2 SP3: Novell Cluster Services 1.8.8 Administration Guide for Linux.
OpenWBEM is a PAM-enabled Linux utility that must be enabled and running on the OES 2 Linux server when you are managing services with Novell Remote Manager for Linux and Novell iManager. During the install, ensure that you enable OpenWBEM (the default) when you configure Linux services. For information, see Services in OES 2 That Require LUM-Enabled Access
in the OES 2 SP3: Planning and Implementation Guide.
Port 5989 is the default setting for secure HTTP (HTTPS) communications. If you are using a firewall, the port must be opened for CIMOM communications.
IMPORTANT:If you receive file protocol errors, it might be because WBEM is not running.
The following table contains some useful commands for resolving CIMOM issues:
|
To perform this task |
At a terminal console prompt, enter as the root user |
|---|---|
|
To check openWBEM status |
rcowcimomd status |
|
To restart openWBEM |
rcowcimomd restart |
Ensure that you install and configure additional OES 2 Linux services that might be required by each of the other services mentioned in this section. Refer to the individual guides for those services for information about how to install and manage them.