Re: BAD BAD CLUSTER - NEED TO REMOVE and RESTART - Some Valued Opinion

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Simon,

I understand the pain.... and I have experienced some "interesting" behavior
with Veritas on Clusters as well, and to-date, uninstall Veritas was
definitely my preferred solution for these mis-behaviors. MSCS can only take
basic disk for clustered disk resources.

You are facing a dillema, not really signature related, but you are having
dynamic disks created by Veritas, and you want to move to basic disk, so
here goes

If you have a "Simple DynamicVolume" which is a dynamic volume on one
physical disk, you can convert back to basic, without data-loss.

If you have a "Mirrored Dynamic Volume" which is 1 dynamic volume, mirrored
on two physical disks, you can convert back to basic.

If you have any other form of dynamic disk, such as "Spanned volume" or
"Striped volume" you can NOT convert back to basic.

Although you can convert some dynamics; I would strongly recommend you
commission new disks from your storage, and do a data-migration. Just for
the fact that you will start with fresh new NTFS basic volumes for your
cluster.

It is a bit of pain to go through, but if you carefully plan, with help of
your storage vendor to help you with the commission of new disk and
migration of data, you probably will benifit of a more stable system in the
long run.

Rgds,
Edwin.



"Simon" <Simon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:224B3D8D-C79F-48DB-AFA0-FE4A48D7E476@xxxxxxxxxxxxxxxx
Hello everyone
Base setup for your info:

2 x Node Cluster Win2k3 SP1
Each Node has "Veritas Storage Foundation" installed and configured. This
application was to make basic disks into dynamic, integrate into the
cluster,
allow you to change disks on the fly, increase, decrease size, ect! It
does
other stuff, but in my opinion and experience, its been a HUGE HUGE
nightmare!!!!
The disks are created from a HP EVA SAN Based Solution - Currently each
node
acts as a FILE SERVER and hosts 8 disks.

PROBLEM: Need to remove the cluster and rebuild. BIG PROBLEM: The Veritas
Storage Foundation Software appears to have made a "signature" on these
disk
volumes. It means, that they cannot be presented to any other windows
server
system, unless we install the Veritas software on another box!

We DONT want this software - its been the clusters problem all along, and
I
need to get shot of it.

Trouble is, does anyone have any experience of this product, more so, is
there a way to "release" these disks so that a bog standard Win2k3 Server
can
see the disks and treat then as just disks that contain data. At the
moment,
when these disks are presented to any other server, they are known as
Foreign
and Windows wants to blat them :-)

As they contain TB of data, its not an option.

WORSE CASE: Create brand new disks from my EVA, basic, restore data from
backup tapes (which is long and hard, but can be done). Dont want to try
this
just yet. Hence, any opinions are welcome.

I am sure the Veritas product is good ... in my professional view....
trying
to make a basic disk into dynamic and making it sing and dance is not what
I
wish to achieve.

And whats wrong with Diskpart - something I have used all the time and
will
continue to use to change my disk size.

Cheers
Simon


.



Relevant Pages

  • Sun Cluster 3.1 and 3510FC and Veritas and Failed Drive
    ... I have a 2 node cluster running Sun Cluster 3.1 ... with Sol 8 and Veritas VxVM and VxFS, I have a 3510fc with a controller ... These partitions were then presented to the cluster nodes ... So I have a disk I can use to replace it with... ...
    (SunManagers)
  • Re: BAD BAD CLUSTER - NEED TO REMOVE and RESTART - Some Valued Opi
    ... Yet my VM Cluster (which uses basic disks) resources take 30 seconds! ... I think in a way there is a signature written within the Veritas Software. ... If you have a "Simple DynamicVolume" which is a dynamic volume on one ...
    (microsoft.public.windows.server.clustering)
  • RE: Use FSMT on dynamic disks?
    ... When using third party disk and SAN solutions on a cluster, ... Veritas Volume Manager. ... Resource Type of "Physical Disk". ... >>I'm trying to migrate some NT4 file servers to a 3 node file cluster. ...
    (microsoft.public.windows.server.migration)
  • SUMMARY: changed WWID on cluster member boot disk
    ... disk and quorum disk of a single-member cluster, ... I could no longer boot from the cluster disks, ... the pre-cluster stand-alone system disk; ... the root1_domain on LUN containing the member boot disk was found ...
    (Tru64-UNIX-Managers)
  • Join an existing cluster
    ... I had a cluster setup with 2 computers running windows ... shared disk array. ... Creating a dummy Local Quorum resource. ... on the same storage bus as the boot disk... ...
    (microsoft.public.windows.server.clustering)