2.4.1 Problems Configuring Replica Sites on Virtualized NetWare

Problems occur when configuring two DFS replica sites on virtualized NetWare guest servers, whether they are on the same host or on different hosts.

If you specify two virtual NetWare servers as replica sites when you define the DFS management context, an error occurs that prevents the second replica site from being set up. To avoid or resolve this problem, set up one replica site when you define the DFS management context, then use the Distributed File Services > Manage Replica Sites page in iManager to set up a second replica site on the second virtual NetWare server.

If an existing replica site is configured on a virtual NetWare server, and you set up a second replica site on another virtual NetWare server, an error occurs when you start the VLDB services on the second site. The process is successful despite the message.

2.4.2 Specifying Non-Default VLDB Database Paths on Replica Sites

If you specify two replica sites when you create a DFS management context, it is not possible to specify non-default VLDB paths that are different for each of the replica sites. By default, each replica site uses the default VLDB path appropriate for its platform. If you specify a non-default VLDB path when two sites are selected, that path applies to both selected replica sites.

For example, you typically specify a non-default VLDB path when you cluster the VLDB service for a replica site so that the VLDB is located on a clustered resource. If you cluster each replica site, the sites might need different non-default paths on their respective servers.

To specify different non-default paths for two replica sites, create the DFS management context with a single replica site, and specify its non-default VLDB path. After the management context is successfully created, use the Distributed File Services > Manage Replica Sites page in iManager to add the second replica and specify the non-default VLDB path to use for its VLDB.

2.4.3 VLDB Service Start in iManager Is Not Working

It is not possible to use iManager to start the VLDB service if the VLDB database is not stored in the default location.

However, you can start the VLDB service from the server console by using the following command:

vldb /dir=vldbpath

where vldbpath is the path to the VLDB database file that you specified on the VLDB replica server.

2.4.4 Splitting Volumes Doesn’t Work if Folders Contain Non-English Characters

Split operations are not possible on volumes that include folders with non-English characters in the folder names.