This guide describes how to install, configure, and manage the Novell® Dynamic Storage Technology for Novell Open Enterprise Server 2 (OES 2) Linux.
Section 2.0, Installing and Configuring Dynamic Storage Technology
Section 4.0, Using Dynamic Storage Technology in a Virtual Environment
Section 5.0, Using DST to Migrate Data on Demand from NetWare to OES 2 Linux
Section 6.0, Management Tools for Dynamic Storage Technology
Section 7.0, Planning Your Dynamic Storage Technology Solution
Section 3.0, Installing and Configuring Shadow File System (ShadowFS) for CIFS/Samba Users
Section 12.0, Troubleshooting for Dynamic Storage Technology
Section A.0, Commands and Utilities for Dynamic Storage Technology
This guide is intended for storage services administrators.
We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.
For the most recent version of the Novell Dynamic Storage Technology Administration Guide, see the Novell Open Enterprise Server 2 documentation Web site .
For documentation on NCP™ (NetWare® Core Protocol™) Server and NCP volumes for traditional Linux* file systems, see the OES 2: NCP Server for Linux Administration Guide.
For documentation on Novell Storage Services™ (NSS) volumes, see the OES 2: NSS File System Administration Guide.
The OES 2: Novell Linux User Management Technology Guide describes how to Linux-enable users for an OES 2 Linux server. CIFS/Samba users of shadow volumes must be Linux-enabled.
For documentation on other OES 2 products, see the Novell Open Enterprise Server 2 documentation Web site .
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux or UNIX*, should use forward slashes as required by your software.