In regards to #2; unfortunately the introduction of UNC naming does
result in a given device being seen as two different filespaces, depending
on which of the two machines in the cluster is backing it up.  Our
workaround was to back out the installation of PTF5 clients on these
NT machines, and revert to PTF3, where the filespace name is generated
from the label of the volume.  In this way it doesn't matter which node
backs up the filespace.  Each node has it's own C:\ drive, and these have
different labels, so there is no conflict there.

The ADSM backup/archive client is not "cluster aware".  IBM would do
well to address this shortcoming as soon as possible.