Installation and User's Guide

Scenario 3b: Back up a node which manages the clustered drives within a clusterresource group and bypass enumeration of cluster resourcesThis is a scenario similar to scenario 3 which can be deployed if the TivoliStorage Manager Backup-Archive client takes an inappropriate amount oftime during startup processing. During initialization of the Backup-Archiveclient, all of the cluster resources are enumerated to determine whichresources represent cluster disk devices. This processing can be skipped bycoding the clusterdisksonly parameter to no.Options file:CLUSTERNODE YESCLUSTERDISKSONLY NODOMAIN f: g:EXCLUDE f:\...\file.txtScenario 4: Back up a node which manages the clustered drives within a clusterresource group, using volume mount points as cluster resourcesIn this scenario, it is assumed that the node is responsible for backing up acluster resource group that has two drives, f: and f:\mnt. There areclustered drives which appear as volume mount points (IBM TivoliSANergy, Windows 2003 server). Ensure that you define the incrementalprocessing domain as only the volumes within a cluster resource group. Ifyou have multiple cluster resource groups, assign a unique Tivoli StorageManager node to manage each cluster resource group.Options file:CLUSTERNODE YESCLUSTERDISKSONLY NODOMAIN f: f:\mntEXCLUDE f:\mnt\...\file.txtTable 55 shows the list of clusternode and clusterdisksonly combinations.Table 55. Clusternode and clusterdisksonly combinationsClusternode Clusterdisksonly When to useno yes This is the default behavior ifnothing is specified; sinceclusterdisksonly is set to yes,the cluster disk map is built.yes yes This is the basic way to runin a cluster node to back upcluster disks; the cluster diskmap is built.320 IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide