Problems with two node cluster running Veritas 4.3 MP 1

I have a two node cluster (Windows 2003 SP1) running Veritas Storage
Foundation for Windows 4.3 MP 1. Everything is working fine with the
resources on there so far, but that's fairly light load.

I'm now trying to migrate a large volume of data (~ 1 TB) using
ScriptLogic's SecureCopy, which is multi-threaded. What I find is that
frequently the job will be running for some time (could be an hour,
could be four hours) and the network name resource fails and takes a
minute or two to come back online.

Microsoft looked at the dumps and said "kernel lock caused by
vxio.sys". Veritas have come back and said they think it could be a
problem whereby large copies can cause their cluster software to fault.

Has anybody come across this before? This is going to be a high-load
cluster, and it seems like it might just be easiest to take Veritas out
of the loop.

.

Relevant Pages

  • Re: Help Again! Cluster Resources Moving Takes Ages & unreliable
    ... I'm not at all shocked to hear that the Veritas resources are causing ... groups are taking an excessive amount of time to go offline and online. ... Use the Cluster Administrator GUI and watch the ...
    (microsoft.public.windows.server.clustering)
  • Re: Lost Quorum
    ... I'm by no means an expert in this subject matter of Veritas Volume Manager, ... is that we don't support Dynamic Disk on a Cluster. ... > terminate resource... ...
    (microsoft.public.windows.server.clustering)
  • Re: Changing Node & Virtual IPs for Print Server Cluster
    ... It's a clustered print server. ... Cluster Node 1 Name: cluster1a.domain.com ... Move all resources to Node A. ... IP addresses for all virtual servers including the cluster itself. ...
    (microsoft.public.windows.server.clustering)
  • Re: Exch 2003 SP2 - applied on one node, but cant move resources
    ... resources to Node2, the failover did not complete because 'system attendant' ... Virtual Exchange server and failover occurred normally again upon taking ... cluster resources oline. ...
    (microsoft.public.exchange.admin)
  • Re: Failed cluster node confusion!
    ... Blue exclamation marks usually means that the cluster service has terminated ... If this fails then the heartbeat will go over the teamed NIC ... the second node did NOT failover the resources. ... working node when one node has completely died (blue screen, ...
    (microsoft.public.windows.server.clustering)
Loading