Installation and User's Guide

VM backups can only be performed by a backup-archive client installed on thecluster node that is the current owner of the VM. To see which VMs are owned bythe node, navigate the Windows menu items: ServerManager->Roles->Hyper-VManager.A VM should be restored only by a backup-archive client installed on the clusternode that is the current owner of the VM. To determine the VM configurations ofthe cluster, navigate the Windows menu items: ServerManager->Features->Failover Cluster Manager->cluster name->Services and Applications. Use theServices and Applications window to change which node is the owner of the VMbefore you restore the VM.VMs currently owned by different nodes which have files on a common ClusterShared Volume cannot be backed up simultaneously. The second backup will failas the shared volume will be owned by the first node. To determine which nodeowns the volume, navigate the Windows menu items: ServerManager->Features->Failover Cluster Manager->cluster name->Cluster Shared Volumes. The ClusterShared Volume windows displays the status of the volume, including ownership,and if a backup is in progress (with redirected I/O enabled).If your cluster environment typically has all VMs owned by a single node, andother nodes only provide failover support, the following applies:vvConsider using CLUSTERNODE YES for backup from the active node andrestore to failover nodes (if needed).Consider running the Tivoli Storage Manager scheduler as a failover service toperiodically backup all VMs. For example: dsmc backup vm *-vmbackuptype=hypervfull. A failover will start the scheduler on the failovernode.If your cluster environment typically has some VMs owned by one node, and otherVMS owned by other nodes, the following applies:vvConsider using ASNODE to allow for backup from multiple nodes and restoreto failover nodes (if needed).Consider running the Tivoli Storage Manager scheduler as active on each nodeto periodically backup the VMs owned by each node. The schedules need to bedefined with non-overlapping start times to avoid contention for commonshared volumes. If the scheduler on each node backs up with -vmlist=*, there isno need for the scheduler service to failover since the scheduler service on theother node will automatically pick up nodes which move over on the nextbackup.Back up and archive Tivoli Storage Manager FastBack dataUse IBM Tivoli Storage Manager FastBack to back up and archive the latestsnapshots for short-term retention.Use the archive fastback and backup fastback commands to archive and back upvolumes that are specified by the fbpolicyname, fbclientname and fbvolumenameoptions for short-term retention.Chapter 4. Backing up your data 151