Stephan,
I apologize for misunderstanding your intent. In this case, you can modify the 'ManageFaults' attribute of the resource. The attribute defaults to ALL, I believe. You can change this setting to NONE and configure VCS to leave the service group running as normal and pretty much ignore the resource fault. It will, however, hang the resource group and all other groups in the cluster by placing the cluster into an ADMIN_WAIT state, requiring intervention to clear the fault manually. When the ManageFaults attribute is set to none, the cluster calls a trigger that you can configure to determine how the cluster responds. If this trigger isn't configred, the default action VCS takes when a resource comes offline unexpectedly is to take the group offline. You can change that behavior by modifying the trigger. The trigger name is 'resadminwait'. Please see pgs 424 and 501 in the VCS Admin Guide for further reference in this configuration.
Hope this helps!
J