After talking to Ed directly we confirmed a correction in 6.5.2 would address LiveUpdate in clusters as well as other installs with busy jobs.  Since there has been some new information shared about LU on this thread, Symantec will pursue a technote documenting this information until manuals are updated.

Etrack Incident = ET1053371

Description: 

    We now cancel a LiveUpdate if any of the following specific processes

    are running on the machine:  bpbkar (bpbkar32), tar (tar32), bpbrm, bptm,

    or bpdm.  This avoids the problem of the install process canceling

    running jobs. 

-----Original Message-----

On Thu, Feb 12, 2009 at 11:09:51 AM, Wilts, Ed <ewilts at ewilts.org>

One of the biggest gotchas for us is that it's pretty much unusable in a

cluster environment.  One of its checks is to see if the client is actually

doing a backup before it tries to upgrade itself.  If you have multiple

names for your hosts - and this is the case for close to 100% of the cluster

users - this check can fail and your backup and/or upgrade job will fail.

Bill_Coleman AT symantec DOT com

Office: 651 746 7118