HP Storageworks HSG80 Manuale Utente

Pagina di 18
Platform-Specific Issues
16
Association Sets
In a Windows NT- X86 cluster configuration, all remote copy sets within an association set 
must be placed in one cluster resource group.
Novell NetWare
NetWare Cluster Services (NWCS)
NWCS v1.01 SP1 for NetWare 5.1 and NWCS v1.6 for NetWare 6 are supported at the 
initiator and target sites. Stretch clusters are not supported at this time. A stretch cluster is 
defined as having a NetWare Cluster using NWCS with cluster members located at both the 
DRM initiator and target sites. NWCS supports both remote copy set and nonremote copy set 
LUNs.
Planned Failover/Failback with NWCS
When preparing the initiator and target sites for a planned failover/failback, use caution when 
removing access to the LUNs at the initiator site. Removing access to the split brain detector 
(SBD) partition, as well as the cluster volumes, without first bringing down the cluster will 
result in server abends. To avoid cluster members abending, issue the following command at 
the system console:
CLUSTER DOWN
You can also run 
ULDNCS.NCF
 at the system console for each cluster member to unload 
cluster services completely.
NetWare 6 Storage Planning Considerations
If you plan on using Novell Storage Services (NSS) logical volumes in a DRM configuration, 
you should be aware that the nature of Novell's Distributed File Services (DFS) allows you to 
span an NSS volume across multiple hard disk partitions. This is not desirable in a DRM 
configuration. Instead, you should maintain a one-to-one relationship among LUNs, remote 
copy sets, NSS partitions, NSS pools, and NSS logical volumes.
Additional Instructions for Failover/Failback
When NetWare volumes are created at the initiator site, they are inserted into the Novell 
Directory Services (NDS) tree as servername_volumename (for example, SERVER1_VOL1). 
After a site failover, the replicated NetWare volumes are still available and can be mounted by 
any NetWare server at the target site, but the volumes will now take on the new server name 
(for example, SERVER2_VOL1). In addition, they will not be automatically inserted into 
NDS, and for traditional NetWare volumes only, they will not maintain the file system 
permissions established at the initiator site. You MUST perform the following steps the first 
time failed-over volumes are mounted at the target site:
Traditional NetWare Volumes
After failing over to the target site and mounting the NetWare volumes:
1. Type 
nwconfig
 from the file server console.
2. Select Directory Options.
3. Select Upgrade Mounted Volumes into the Directory, and supply an 
administrator-equivalent userid and password.