Updates were made to the following sections. The changes are explained below.
Location |
Change |
---|---|
Section 15.0, Configuring DST Shadow Volume Pairs with Novell Cluster Services |
Sections and steps to manually set the EXCLUDE_VOLUME line in the /etc/opt/novell/ncp2nss.conf file were removed. |
This section was modified for clarity. |
|
Section 15.2, Planning for DST Shadow Volume Pairs and Policies in a Cluster |
This section was modified for clarity. |
When you bring the resource online on a node for the first time, an EXCLUDE_VOLUME line is automatically added to the /etc/opt/novell/ncp2nss.conf file as well as the temporary exclusion table in cache on that node. |
|
Section 15.8, Renaming a Shared Pool in a DST Cluster Resource |
This section is new. |
Section 15.9, Renaming a Shared Volume in a DST Cluster Resource |
This section is new. |
Section 15.10, Removing the Shadow Relationship for a Clustered DST Volume Pair |
This section was modified for clarity. |
Section 15.11, Upgrading a Cluster with DST Resources from OES 2 SP3 to OES 11x |
This section is new. |
Location |
Change |
---|---|
This section is new. |
|
Section 10.4, Replicating the Secondary File Tree Structure to the Primary Volume |
This section is new. |
Location |
Change |
---|---|
Section 3.0, Planning Your Dynamic Storage Technology Server Environment |
Planning the DST server environment was relocated to its own section. |
Configuration of global policies was relocated to its own section. |
Location |
Change |
---|---|
The introduction was modified for clarity. |
|
This section was modified for clarity. |
|
This section was modified to clarify how security is handled for different merged views. |
|
In general, you should not create a DST shadow relationship between two unrelated existing volumes. You can temporarily remove a shadow relationship between two volumes, and then re-define it, because their content is logically and structurally related. |
The Section 12.0, Managing Directory and User Space Quotas on DST Volumes section is new.
Location |
Change |
---|---|
This section is new. |
|
New folders are automatically created on the primary volume. An instance of the folder is created on the secondary volume immediately if the REPLICATE_PRIMARY_TREE_TO_SHADOW parameter is enabled, or when data in the new folder is moved by a policy to the secondary volume. The parameter is disabled by default. If you define a DST shadow volume pair with an existing volume as secondary and a new volume as primary, the directory structure is replicated gradually to the primary volume as files are used or moved there with a policy. Empty folders are not automatically replicated on the new primary volume. To ensure that the entire existing directory structure (including empty directories) is replicated on the primary volume, an administrator can enumerate the directory from an NCP client that is mapped to the merged view. |
|
This section was modified to clarify how NSS directory quotas are enforced for the primary volume and secondary volume. |
|
This section was modified to clarify how NSS user quotas are enforced for the primary volume and secondary volume. |
|
This section is new. |
|
Section 9.13, Using Backup Utilities with DST Shadow Volume Pairs |
If you back up the NSS volume by using the NSS Extended Attributes (XAttr) settings to preserve the NetWare metadata (netware.metadata) for file system rights and attributes, this information can be restored only directly to an NSS volume. For information about using the NSS /ListXattrNWmetadata option and the security considerations involved, see Backup utilities might also work against the ShadowFS merged view. However, because the ShadowFS merged view is a Linux mount point and is not seen by the backup software as an NSS volume, the file system rights and attributes are not preserved. It is not recommended or supported to back up NSS files from this Linux mount point. |
The information in this section was previously located in the installation section.
Location |
Change |
---|---|
Section 3.8, Supported Native Linux File Access Protocols with ShadowFS, FUSE, and LUM |
This section was added to clarify supported configurations. |
This section was added to clarify supported configurations. |
Location |
Change |
---|---|
This section is new. |