DMP, MPIO, MSDSM, SCSI-3 and ALUA configuration settings
Ok, I'm somewhat confused and the more I read the more confused I think I'm getting. I'm going to be setting up a 4 node active/active cluster for SQL. All of the nodes will have 2 seperate fiber channel HBAs connecting through 2 seperate switches to our NetApp. The NetApp supports ALUA, so the storage guy wants to use it. It is my understanding that I need to use SCSI-3 to get this to work. Sounds good to me so far. My question is, do I need to use any of Microsoft's MPIO or MSDSM? This is on Win 2008 R2. Or does Veritas take care of all of that? Also, I read that in a new cluster set up, only connect 1 path first and then install and then connect the 2nd path and let Veritas detect it and configure it. Is that accurate? Any info or directions you can point me will be greatly appreciated. Thanks!SolvedUnknown 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 SFWPrivate 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.4KViews0likes11CommentsTroubles with Lanman on Fileshare
Hi there ok i have some Troubles since i made the upgrade from 5.0 to 5.1 The resource lanman for a file share fails all the time, but the fileshare is working fine. First question: do i need the lanman resource for a fileshare? In the template there is the lanman too.. i see no error in the lanman.txt 2009/08/07 12:25:18 VCS DBG_21 V-16-50-0 Lanman:APPLP_Lanman:monitor:*** Start of debug information dump for troubleshooting *** LibLogger.cpp:VLibThreadLogQueue::Dump[206] 2009/08/07 12:25:18 VCS DBG_21 V-16-50-0 Lanman:APPLP_Lanman:monitor:Listing resource (APPLP_Lanman) attributes: LanmanAgent.cpp:CLanmanAttributes::Parse[2693] 2009/08/07 12:25:18 VCS DBG_21 V-16-50-0 Lanman:APPLP_Lanman:monitor:m_VirtualName = Sharename_xxxx LanmanAgent.cpp:CLanmanAttributes::Parse[2707] 2009/08/07 12:25:18 VCS DBG_21 V-16-50-0 Lanman:APPLP_Lanman:monitor:m_IsMultiNet = 0 LanmanAgent.cpp:CLanmanAttributes::Parse[2718] 2009/08/07 12:25:18 VCS DBG_21 V-16-50-0 Lanman:APPLP_Lanman:monitor:ipAddress = xxx.xx.xx.xx, 0x414815AC LanmanAgent.cpp:CLanmanAttributes::Parse[2743] 2009/08/07 12:25:18 VCS DBG_21 V-16-50-0 Lanman:APPLP_Lanman:monitor:subnetMask = 255.255.255.0, 0x00FFFFFF LanmanAgent.cpp:CLanmanAttributes::Parse[2767] 2009/08/07 12:25:18 VCS DBG_21 V-16-50-0 Lanman:APPLP_Lanman:monitor:*** End of debug information dump for troubleshooting *** LibLogger.cpp:VLibThreadLogQueue::Dump[217] I deleted the resource and build it new but with the same result: the resource has a big red question mark There are no errors in the Eventog neither System: Windows Server 2003 SP2 Standard Edition x86 Storage Foundation HA for Windows 5.1 Thanks3KViews0likes11CommentsMaking Virtual IP as source IP on Windows 2008 R2 node
We are running SFHA v5.1 for Windows 2008 R2 and we would like the floating virtual IP assigned to resource group to the be the source IP of the node instead of the default IP assigned to the interface. I'm a little fuzzy on how Windows chooses which IP is the source IP if there are multiple IP's assigned to an interface, but I was wondering if there is any configuration setting that can be chosen within SF. This is important because the firewall team only wants to allow through the VIP of the resource group.Solved2.2KViews1like3CommentsVeritas Storage Foundation for Windows 5.1 Volume Manager Disk Group fails to come online
We are trying to implement a 2 Node SQL server cluster on Windows 2008 R2 for last few days. We have so far successfully completed Windows cluster part and have tested quorum failover and single basic disk failover. Our challenge is that for shared storage between two nodes where we have got 30 LUNs from SAN but we need to have single drive. Since merging LUNs at SAN level is not an option for us and MSCS does not understand dynamic disk group created using winodws disk manager we have to use Veritas Storage Foundation for windows 5.1. We have successfully installed SFW 5.1 and created Cluster Dynamic Disk group and Volume on this disk group. This volume is visible in Windows Explorer without any issue. To add this disk group in cluster we followed below steps 1. In "Failover Cluster Manager" we created "Empty Service or Application" 2. Added "Volume Manager Disk Group" resource in the application. 3. After right clicking on the resource and selecting "Bring this resource online option" the disk group was brought online. To test the failover we rebooted the first node. The disk group failed over to the second node without any issue. To bring back disk group on node one again we restarted the second node, however this time on the first node the disk group could not come online with status was shown as "Failed". Since then we have tried rebooting both nodes alternatively, refreshed , rescaned disks but everything has failed to bring back the resource online. We have again followed all the steps from the start but same result. Can anybody suggest forward path?2.2KViews0likes4CommentsCan I use the Mirror Disk for MS-Cluster?
Dear All My Environment is MS-Windows 2003 Ent 32bit + Storage Foundation 5.0 Local Disk for C: 50GB Local Disk for D: 86GB LUN SAN #1 = 300GB LUN SAN #2 = 300GB I use Storage Foundation 5.0 to create the mirror disk (LUN SAN #1 and #2) It's working good. Then I have plan to make the Windows 2003 Cluster by Windows Cluster Service I heard that the dynamic disk (not use Veritas Disk Management, it can do the Dynamic Disk and make Mirror Volume) can't use in Cluster Service Can I use the Veritas File System that make Mirror Disk for MS-Windows Cluster 2003 Ent. Best Regards PiyabootSolved1.9KViews0likes4CommentsFile-Server | physical or over VMware vSphere? Need advice
Dear all, maybe you have a suggestion for me. We are running two SF 5.1 SP1 [Enterprise with Option MS Cluster Enterprise] on two MS Server 2003 Enterprise R2 x64 Cluster Nodes right know. There are some storage-arrays [DAS] directly on the server-machines - clustering is possible, because of two controllers in the disk-arrays. And there is some real SAN-storage over FC. My vision/planning for the future is to build up more storage in the SAN over FC or iSCSI to get away from DAS-storage and to manage all of it over SF (again). We also planning to virtualize our servers (up to 6-7 servers (Exchange, DFS, DC/DNS, Lizenzmanager-Server, etc.)) to run all of them on one or two physical servers; maybe a third standby-ESX. So there is the question to virtualize both of the enterprise cluster nodes and let them run as virtual machines or let them stay as physical machines? My pros: • "double failsafe", because the enterprise servers are cluster nodes right know [failsafe 1] and if the physical ESX is going down this virtual machine(s) will switch automatically to the second ESX [failsafe 2]. • Faster server-hardware change in the future. Build up a new ESX on more performant hardware; move the vm-server to it; shut down the old ESX which isn't performant enough anymore - no downtime. ...ok, ok, I have a cluster, so changing hardware would be possible without downtime, too. • Maybe better possibility to trunk the networkports. I'm not using vSphere right now, I only remembering some stuff from VMware webcasts. • Betterutilization of the physical hardware! That's why you will virtualize all servers. • Making snapshots before upgrade software on the servers. Faster "recovery" of the old status. "Never touch a running system" is the past. • Better allocation of the physical RAM to different servers. My cons: • Will SF run as good as it does on the physical environment right now? Or are there any restrictions - maybe because of drivers, the hypervisor, anything else? • Will SF be (more) performant than right now or will it slow down everything, especially if I use VxCache with 8GB RAM or more? • I need lots of RAM Would be nice to here some comments or another ideas from you. Thanks in advance.1.9KViews0likes4CommentsEvent ID ( 12 ) in Source ( Veritas VSS Provider )
Hello All, The following message makes sense to anyone? I need urgent help. I couldn't reach any technote,..etc. Any comment? Event Type: Error Event Source: Veritas VSS Provider Event Category: None Event ID: 12 Date: 4/7/2009 Time: 9:23:30 AM User: N/A Computer: xxxxxxx Description: The description for Event ID ( 12 ) in Source ( Veritas VSS Provider ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: . Thanks. Servet1.8KViews0likes0Comments