NetWorker: Cluster DISASTER_RECOVERY:\ backup failing in Passive node

File system backup fails for DISASTER_RECOVER:\ save set but works for local drives in a two-node cluster.

Environment:

• Windows Server Cluster Client. The configuration involves backups of the physical nodes and a "virtual client" resource that backs up the Cluster Shared Volumes (CSV)
• Cluster_Name. Save set details: Shared drive Q:\ and CSV (C:\ClusterStorage\Volume1).
• ClusterNode-1: Saveset details > C:\ and DISASTER_RECOVERY:\
• ClusterNode-2: Save set details > C:\ and DISASTER_RECOVERY:\

The DISASTER_RECOVERY:\ backup fails for a passive node, the following error is observed:

99128:save:Disaster Recovery: critical volume C:\ClusterStorage\Volume1\ identified for disaster recovery backup has been created on a CSV volume. Backup of critical volume on CSV volume is not supported.

This means that some application is installed on the Cluster Shared Volume (CSV), hence it is considering CSV as critical drive.

save -o VSS:LCV=yes should not list CSV as critical volume on the physical nodes. If CSV is listed as critical, then the DISASTER_RECOVERY:\ backup fails.

Remove installed application from CSV.

The output is from one of the nodes in the Cluster. This shows CSV as critical volume and hence backup works for C:\ and fails for DISASTER_RECOVERY:\ save set from this node.

C:\Windows\system32>save -o VSS:LCV=yes
181407:save: Step (1 of 5) for PID-7600: Save has been started on the client 'clu_node1'.
175312:save: Identified a save for the manual backup with PID-7600 on the client 'clu_node1'. Updating the total number of steps from 5 to 7.
175313:save: Step (2 of 7) for PID-7600: Running the backup on the client 'clu_node1' for the selected save sets.
3817:save: Using YYYYY as server
99128:save:Disaster Recovery: critical volume C:\ClusterStorage\Volume1\ identified for disaster recovery backup has been created on a CSV volume. Backup of critical volume on CSV volume is not supported.
The following volumes are determined as critical by the system state writers:
C:\ (disk num 0)
The following volumes are critical because they are parents for one or more mounted critical volumes:
The following volumes are critical because they are in the same dynamic disk pack with one or more critical volumes:
The output is from another node from Cluster which doesn't show CSV as critical volume and hence backup works for both C:\ and DR saveset.
C:\Windows\system32>save -o VSS:LCV=yes
181407:save: Step (1 of 5) for PID-8172: Save has been started on the client 'cluster_node2'.
175312:save: Identified a save for the manual backup with PID-8172 on the client 'cluster_node2'. Updating the total number of steps from 5 to 7.
175313:save: Step (2 of 7) for PID-8172: Running the backup on the client 'cluster_node2' for the selected save sets.
3817:save: Using YYYYY as server
The following volumes are determined as critical by the system state writers:
C:\ (disk num 0)
The following volumes are critical because they are parents for one or more mounted critical volumes:
The following volumes are critical because they are in the same dynamic disk pack with one or more critical volumes: