D.5 Removing the Shadow Volume Relationship in a Cluster Resource with a Remote Secondary

  1. Log in to the master node of the cluster as the root user, then open a terminal console.

  2. If the cluster pool resource for the shadow volume is not running on the master node, cluster migrate it to the master node. At the console prompt, enter

    cluster migrate resource_name masternode_name
    
  3. Offline the cluster pool resource that is managing the shadow volume.

    cluster offline resource_name
    

    This unloads the cluster resource and deactivates the cluster pool and the shadow volume so that the cluster is not controlling them.

  4. Manually activate the shared pool and mount the primary volume.

    1. At the console prompt of the master node, enter

      nssmu
      
    2. In the NSSMU menu, select Pools, then press Enter.

    3. Select the primary pool, then press F7 to activate it.

    4. Press Esc to return to the NSSMU menu, select Volumes, then press Enter.

    5. Select the primary volume, then press F7 to mount it.

    6. Press Esc twice to exit NSSMU.

  5. Remove the shadow volume relationship between the two volumes:

    1. In Novell Remote Manager for Linux, log in as the root user. to the master node.

    2. Select Manage NCP Services > Manage Shares to go to the NCP Shares page.

    3. On the NCP Shares page, locate the primary NSS volume in the Active Shares list, then click the Unmount button next to the share name.

    4. On the Manage Shares page, click the Information (i) icon next to the volume name of the NSS volume to access the Remove Shadow Action Options.

    5. On the volume’s Share Information page under Volume Tasks > Remove Shadow Action Options, click Remove Shadow.

      After the shadow volume is removed, the page refreshes to report a successful removal.

    6. Select Share Management to go to the NCP Shares page, locate the volume that was the primary volume in the Active Shares list, then click the Mount button next to it.

    7. Verify that the shadow volume was removed by using one of the following methods:

      • Select View File System > Dynamic Storage Technology Options to go to the Dynamic Storage Options page. The former primary volume now has an Add Shadow link next to it instead of a Shadowed link.

      • Select Manage NCP Services > Manage Shares, then click the Information icon next to the former primary volume name.

        The File System Shadow Path field displays that it is not applicable (n/a).

  6. In NSSMU, manually deactivate the primary pool and its volume.

    This automatically dismounts the shared volume, which allows the cluster resource to be managed by the cluster resource again.

    1. At the console prompt of the master node, enter

      nssmu
      
    2. In the NSSMU menu, select Pools, then press Enter.

    3. Select the primary pool, then press F7 to deactivate it.

    4. Press Esc twice to exit NSSMU.

  7. Modify the load script of the cluster pool resource that was managing the clustered shadow volume pair:

    1. In iManager, select Clusters, then select Cluster Manager.

    2. Click the Object browser, then locate and select the cluster server node to view a list of cluster resources.

    3. On the Cluster Manager page, click the name link of the primary cluster resource to view its Cluster Pool Properties page, then click the Scripts tab.

    4. On the Scripts > Load Script page, comment out or remove the following commands:

      #Log in to the remote server
      exit_on_error /opt/novell/ncl/bin/nwlogin --server 10.10.10.41 --tree MYCOMPANY_TREE --user dstuser --context users.context --password novell 
      
      ncpcon mount volumename=volID,SHADOWPATH=shadowpath 
      
    5. On the Scripts > Load Script page, uncomment the mount command for the primary pool’s volume that you commented out when you set up the clustered shadow volume. For example:

      exit_on_error ncpcon mount VOL1=254
      
    6. Click Apply to save your changes.

      The changes do not take effect until the cluster resource is taken offline and brought online.

  8. Modify the unload script of the cluster pool resource that was managing the clustered shadow volume pair:

    1. On the Scripts > Load Script page, click the Unload Script link.

    2. On the Scripts > Unload Script page, comment out or remove the nwlogout command for the remote secondary server:

      #ignore error nwlogout --server remote_servername_or_IP_address
      
    3. Click Apply to save your changes.

      The changes do not take effect until the cluster resource is taken offline and brought online.

  9. Online the cluster pool resource for the primary pool:

    1. Select Clusters, then select Cluster Manager to view the list of cluster resources.

    2. Select the check box next to the primary cluster pool resource, then click Online.

    3. Select the cluster node where you want the resource to load (such as server38), then click OK.

  10. Verify that the cluster resource is running by going to the Clusters > Cluster Manager page.

  11. Use one of the following methods to remove file access to the secondary volume:

    • All NSS volumes on all of the remote servers: On the DST server, log out of the Novell Client sessions for all remote servers.

      1. Log in to the DST server as the root user, then open a terminal console.

      2. At the console prompt, enter

        nwlogout --tree <tree_name>
        
    • All NSS volumes on the remote server: On the DST server, log out of the Novell Client session for a specified remote server.

      1. Log in to the DST server as the root user, then open a terminal console.

      2. At the console prompt, enter

        nwlogout --server <remote_servername_or_ip_address>
        
    • Individual NSS volume on the remote server: Remove the file system access rights on the remote volume for the user name you used to log in to the remote server.

  12. For the remote NSS volume, remove any special file system access rights that you gave the user name that you used for the remote login.

  13. For the remote NSS volume, set up file access for users.