Unknown Dg appears in Disk Groups with some or all disks
Hello, Since support from Symantec is slow (not every case, but this time), I am asking this on forum. I am doing a new installation and suddenly I have this new DG called "Unknown Dg". There are disks with status foreign and type Dynamic. I cannot do anything with these disk (oh powerfull SFW). Usually I can destroy DG or remove disk from DG etc, but not in this case. Reason for having this situation: - I made two cluster Disk Groups with same name on different servers with different disks and suddenly disks from this Disk groups are in disk group Unknown Dg - I reinstalled SFW and suddenly all disks from all dynamic Disk groups are in Unknown Dg I searched documentation and found this: If the cluster software attempts to fail over a disk group to another node that has a disk group with the same name or if you move a disk group to another node that has a disk group with the same name, unpredictable results can occur. (well now we know the result). I searched internet and found this: http://seer.entsupport.symantec.com/docs/287444.htm (there is part telling you to reinstall SFW - but this makes it even worse) I found also this: vxtool is used to clear the SFW Private Region from a disk and would be used in instances when you were attempting to destroy a Disk Group or remove a problem Disk that has a corrupted private region on it. The resetmbr clears the private region and writes a new signature to the disk. Do you think that vxtool can help me with this ? my config: w2k3 r2 sp2, VSFW 5.1 sp1, fiber HBA qlogic QLE2460, and IBM DS8300 arraySolved3.5KViews0likes11Comments
Doc for Storage Foundation for Windows 5.1 NTFS Volume Size Limit
Hi, I was not able to find a KB doc on the NTFS volume size limit when using Storage foundation for windows 5.1. What is the ntfs volume size limit when formated with default cluster size on 32-bit windows 2003 with sp2? Is it 16TB ir 15.xTB? Thanks, SteveSolved2.3KViews0likes6Comments
Storage Foundation 5.1 and MSCS not working
Hi. We want to use Storage Foundation 5.1 to manage our dual path disk. We are clustering MS BizTalk 2006 so we need to use MSCS to Cluster BizTalk. Problem is that MSCS cannot see the disk group created in SF. We are using Windows 2003 Enterprise Server R2 We installed SF first and the disk groups appear fine. Then we tried to configure MSCS and it could not see the disk. During some investigation we discovered we needed the MSCS Option, so we added our "VRTS STORAGE FOUNDATION OPTION MICROSOFT CLUSTER 5.1 WIN FOR OS TIER ENTERPRISE EDITION STD LIC" license key and it indicated that the MSCS option is available. However, when we go back to Add/Remove programs to select this option, it does not appear as a choice in the add/remove SF options. How should we proceed? Is there a seperate plug in we need to download or should it appear in the list of options in the SF installation screen? Do we need to have MSCS configured before we install SF so it can detect it? Any advice would be appreciated. WarrenSolved1.9KViews0likes4Comments
Storage Foundation 3.2.542.0 error message
Hi all, we have a veritas enterprise administrator runnning on windows 2003 server cluster running. Now i see an exclamation mark on some volumes and hd's. If opne a volume and see one of the disks i see this alerts: Warning V-76-58645-1000 Aler Propagated and Error V-76-58645-1080 Subdisk Detached If i take a look on my SAN it seems that all HD's are ok. At the moment I'm not really know what it means and what i have to do. Can anyone help me here? Or i have just to reactivate the harddisks? or just du cluster turn to the other cluster node? Thank you very much!Solved1.8KViews0likes11Comments
Volume Status description vs Volume State in vxprint output
The Admin guide has a list of Volume Status descriptions but some of the listed statuses are not what they appear in vxprint output. I have managed to simulate some States/Status but not all. For example, for the "Healthy" status, vxprint output will show "ACTIVE". Similarly for the "Degraded" status, vxprint output will simply show "-". In the below output sample, "Failed" status is accurately shown as "Failed". Diskgroup = OTL2K801-Dg0 TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 v HarddiskVolume2 - - 8192 - - - - v Volume - - 16384 - Failed - - v Volume2 - ENABLED 14336 - ACTIVE - - Is there a tabulated list of vxprint output Volume State values vs Volume Status that you see on the VEA concole? Or, what would be corresponding vxprint output Volume State values for Volume Status: - Resynching - Regenerating - Formatting - Missing - Failing I am trying to write something that will interpret the vxprint output so I need the above information. Am I in the wrong place asking for such info? Thanks.Solved1.7KViews0likes8Comments
Using SFHA on Windows, under VMware
We are considering options for clustering Windows (2k3R2, 2k8R2, X64) nodes that are actually VMware VMs (ESX 4.1). Is there documentation that describes setting this up, and what limitations might exist? For example, does using cluster effectively kill the ability to VMotion? Do you have to use RDMs for storage? Sorry for being vague, I don't know enough (yet) to ask targeted questions. Thanks in advance!Solved1.7KViews1like4CommentsSF Basic missing features?
Hi! Just trying out SF Basic on a freshly-built Windows 2008 R2 Standard server. The GUI installer won't allow me to check any of the features except the one to replace the Windows storage MMC. According to the SF 6.0 compatability guide, the array I'm using, an IBM DS3524, is supported, and Windows 2008 R2 is definately supported. The docs on the Basic version would seem to imply that DMP is included, too. I'm logged in with administrator rights (and have tried it logging in directly as the Administrator, too...). The MPIO feature is installed in the Windows Server Manager. Any idea why I can't install DMP, or any of the other features? The web page http://www.symantec.com/business/storage-foundation-basic clearly indicates that Dynamic Multipathing is part of the package... If DMP isn't part of SF Basic anymore, what's the advantage to use of SF? Are there any performance benefits anymore over the standard vendor DSM and Windows LDM? Thanks! -BenSolved1.5KViews2likes7CommentsHow do I migrate from MSCS to SFWHA?
Hi, I'm in the middle of a proposal and the customer ask us to describe the way (step by step) to migrate their MSCS (2003) to SFWHA (VCS)? do you know if Symantec has a procedure? Any recommendation? The customer requires minimal impact and smooth process? Thanks for your help. Gonzalo GomezSolved1.5KViews0likes7Comments
Multiple Shares issue
We have four Windows 2008 R2 SP1 SFW 5.1 HA clusters haring Files. The all have same configuration in terms of service pack, version of SFW 5.1 CP8 and Windows 2008 R2 SP1 however the way sharing works differ between these clusters. If SFW creates a share on Cluster 1 nodes, the share is available when addresses the node hostname. For example, we create virtual name with Lanman Resource \\VIRTUAL01\SHARE01 When the share resource is brought up on cluster #1 we can access SHARE01 using \\CLUSTER01\SHARE01 as well as \\VIRTUAL01\SHARE01 When the same share resoure is brought on Cluster #2 we cannot do it using \\CLUSTER02\SHARE02 and can only do it \\VIRTUAL01\SHARE01 CLUSTER01 and CLUSTER02 are physical nodes hostnames. There's also another difference. When Storage Foundation creaes a Lanman Vistual Name on Cluster #1, we can see all the root windows drives with that virtual name e.g. \\VIRTUAL01\c$ When the same virtual name is created on cluster 2, we cannot access trhe root drives. This essentially leads to interesting scenarios: on the node where the SFW does not mix with the Windows sharing we can create two identical sharenames and point them to different locations. e.g. on Cluster Node 2 we can do "SHARE01" -> pointing to c:\Dir1 from Windows and also bring a Vierual Cluster Resource and Create "SHARE01" pointing to D:\Dir2 but accessingle only via the Virtual Lanman Resoirce name, created by the Storage Foundation. When looking at the Share and Storage management from Windows - we can see both Shares identically named pointing to different locations. We cannot do so on Cluster 1 as creating the same share name will conflict with existing share name. We are trying to nail this down but so far went through the setu (which was done from same image of OS and enabled same features).. Server Policy, SFW 5.1 version and updates - all to no avail. We need to understand this behaviour and what it coudl be related to. Any feedback is appreciated. Thank you.Solved1.3KViews0likes4Comments
How to use local disk on all nodes to configue VCS+VVR+GCO configuration
Hi all: I need a solution, please help, thank you. Environment: Main site windows 2008 R2 + DR site Windows 2008 R2 SFHA6.0 Requirements: Between the two sites do data replication using VVR But our IT system does not have a disk array, we need to use the PC server's local disk storage space do VCS application resource group. But VCS resource group does not support the server's local disk, VCS Configuration Wizard only supports Cluster disk group. What mode of operation can be achieved using PC Server local disk and DR VVR do it?Solved1.2KViews1like2Comments