RE: Use FSMT on dynamic disks?

Hi,

I'm sorry to hear that my suggestion didn't work.

In fact, we recommmend not to use such third-party application in cluster
server.The work around I provided also not very perfect and we also
recommend not to use. Since the work around didn't work, I'm afraid you
have no choice but temporarily removing Veritas.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
>>Thread-Topic: Use FSMT on dynamic disks?
>>thread-index: AcW5CJimDDQkKMH3SVyZ3wOs7prxfg==
>>X-WBNR-Posting-Host: 130.225.15.40
>>From: =?Utf-8?B?S1RS?= <KTR@xxxxxxxxxxxxxxxxxxxxxxxxx>
>>References: <61094679-E256-4DC7-9C49-67EBA0719773@xxxxxxxxxxxxx>
<X5yOmENuFHA.580@xxxxxxxxxxxxxxxxxxxxx>
>>Subject: RE: Use FSMT on dynamic disks?
>>Date: Wed, 14 Sep 2005 01:45:02 -0700
>>Lines: 80
>>Message-ID: <2F4984FB-A73A-4CB3-8B48-D970F3877337@xxxxxxxxxxxxx>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>>Newsgroups: microsoft.public.windows.server.migration
>>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:11959
>>X-Tomcat-NG: microsoft.public.windows.server.migration
>>
>>Hi Vincent.
>>
>>I have tried the workaround to rename the Volumemanger Disk Group so that
>>they apear in the cluster administrator as Physical Disks, FSMT is not
fooled
>>by it and still detects that it is not a physical disk.
>>
>>I could install all disks as physical disks with dual path disabled, bu
then
>>I would have to backup and restore everything after the migration to
change
>>the disks to dynamic again (1,5TB data).
>>
>>Regards Knud.
>>
>>"Vincent Xu [MSFT]" wrote:
>>
>>> Hi,
>>>
>>> When using third party disk and SAN solutions on a cluster, you cannot
>>> select disks that are not Basic Disk (from the New Project Wizard and
>>> trying to select a Default
>>> Location for Migrated Shared Folders). From your description, you are
using
>>> Veritas Volume Manager.
>>>
>>> File Share Migrator wizard calls OpenCluster and then looks for the
>>> Resource Type of "Physical Disk". The problem occurs when a third party
is
>>> installed is that they utilize their own resource DLL and the Type is
>>> different than "Physical Disk".
>>>
>>> You may be able to work around the problem by either temporarily
removing
>>> Veritas and so that you're dealing just with a Physical Disk resource
type
>>> (must be Basic disk). Another method which is unsupported is to change
the
>>> cluster registry hive so the the Cluster->Resources->GUID->Type is set
to
>>> "Physical Disk". You'll need to change this back to whatever Veritas
sets
>>> it to after the migration
>>>
>>> Hope the information helps.
>>>
>>> Best regards,
>>>
>>> Vincent Xu
>>> Microsoft Online Partner Support
>>>
>>> Get Secure! - www.microsoft.com/security
>>>
>>>
>>> --------------------
>>> >>Thread-Topic: Use FSMT on dynamic disks?
>>> >>thread-index: AcW4X+IAXjeSwgrdRmKr4NG27l94rg==
>>> >>X-WBNR-Posting-Host: 82.143.199.69
>>> >>From: =?Utf-8?B?S1RS?= <KTR@xxxxxxxxxxxxxxxxxxxxxxxxx>
>>> >>Subject: Use FSMT on dynamic disks?
>>> >>Date: Tue, 13 Sep 2005 05:37:20 -0700
>>> >>Lines: 6
>>> >>Message-ID: <61094679-E256-4DC7-9C49-67EBA0719773@xxxxxxxxxxxxx>
>>> >>MIME-Version: 1.0
>>> >>Content-Type: text/plain;
>>> >> charset="Utf-8"
>>> >>Content-Transfer-Encoding: 7bit
>>> >>X-Newsreader: Microsoft CDO for Windows 2000
>>> >>Content-Class: urn:content-classes:message
>>> >>Importance: normal
>>> >>Priority: normal
>>> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>>> >>Newsgroups: microsoft.public.windows.server.migration
>>> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>>> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>>> >>Xref: TK2MSFTNGXA01.phx.gbl
>>> microsoft.public.windows.server.migration:11940
>>> >>X-Tomcat-NG: microsoft.public.windows.server.migration
>>> >>
>>> >>I'm trying to migrate some NT4 file servers to a 3 node file cluster.
>>> Windows
>>> >>2003 SP1.
>>> >>The cluster servers has Veritas Storage Foundation installed (for
dual
>>> path
>>> >>to SAN)and all disks are dynamic disks. DFS works fine in the cluster.
>>> >>FSMT is failing the migration because it looks for Physical disks.
>>> >>Is there a way around this problem?
>>> >>
>>>
>>>
>>

.

Relevant Pages

  • 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)
  • Re: Creating a wide area VMS Cluster
    ... > My goal is to provide a disaster tolerant cluster for both OS and data. ... disrupting the balance of the effect of votes between sites A and B. ... You have the option of a single shadowed system disk between the ...
    (comp.os.vms)
  • RE: Cluster IP Address Does not fail over
    ... The cluster IP has no dependicies at all. ... Node1 disk manager sees LUN5. ... [DiskArb] ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... Isin't the W2K3 Cluster Server Recovery tool designed to ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... >>just fine but not the data drives, basically on step 14 my old drives ...
    (microsoft.public.windows.server.clustering)