Failover

24 Topics

Storage Foundation
Hi im new to the product and the field, so really any advice would be great. where exactly do you install VOM in your SAN environment and does the SF s/w collide with the storage vendor management s/w. And how do you control a heterogenous storage with SF Also can someone explain the licensing.
Solved
Amal_Jacob_John
9 years ago Place Storage Foundation for Windows
2KViews
0likes
7Comments
Windows 2012 R2 Failover cluster and SF Volume Manager Disk Group
Hi, I just found this article and its quite the problem I'm facing right now: https://www-secure.symantec.com/connect/forums/one-cooperation-issue-about-windows-2012-r2-failover-cluster-and-sf-cluster-shared-disk-group I created a new Windows Server 2012 R2 Failover Cluster with several mirrored Disks in DynamicDiskGroups in StorageFoundation. As a next step, I wanted to add the Diskgroups from SF as a Ressource to my Failover Roles. Actual scenario: Cluster Role Name: C0002Z DiskGroupName in SF: DG_C0002Z_1 Then I added a Ressource to the Cluster Role via Add Resource -> More Resources -> Volume Manager Disk Group I changed the Name of the VMDG in "General" to "DG_C0002Z_1", apply, ok. Then I wanted to add the Name of the DiskGroup in Properties -> Properties -> DiskGroupName of the VMDG to "DG_C0002Z_1". And thats where I dont get any further. It doesn't matter which Name I want to enter into DiskGroupName, theres always this Error: There was an error saving properties for 'DG_C0002Z_1'. Failed to execute control code '20971654'. Error Code: 0x800700a0 One or more arguments are not correct I also tried to enter Names without special characters but that doesnt help eather. Do you have any Idea how to fix or bypass this issue? Thanks
CHPost
10 years ago Place Storage Foundation for Windows
2.4KViews
0likes
1Comment
ForceImport
Hi all, I need help to good understand attribute ForceImport. There is a table "Failure situations" in Symantec Storage Foundatio and High Availability Solutions Solutions Guide. (221p.) I don't understant situation number 7 Split-brain situation andstorage interconnect lost. ForceImport set to 0 - No interruption of service.Can’t import with only 50% of disks available. Disks on the same node are functioning. Mirroring is not working. ForceImport set to 1 - Automatically imports disks on secondary site. Now disks are online in both locations—data can be kept from only one. Who can unswer this question: "Now disks are online in both locations—data can be kept from only one" What is the purpes? What we will get if first 50% of disks will imported on 1 site and second 50% will imported on 2 site?
Solved
KANSTANTSIN
10 years ago Place Storage Foundation for Windows
1.3KViews
0likes
5Comments
Failed to get the MSDTC Security configuration for VCS from registry
Hi, I created campus cluster with 2 servers (Operating system: Windows server 2012 R2. SQL server 2012. Symantec Storage Foundation 6.1.) Service group became online through time. In first time - Faulted. I clear fault on this server and try up service group. Service online. I made it offline then try up and got faulted. Then online, faulted and so on... Faulted SQL agent. In SQL server logs I didn't find any errors. In C:\Program Files\Veritas\cluster server\log\SQLserver_A.txt I got errors 2015/05/16 20:41:33 VCS NOTICE V-16-20093-75 SQLServer:SQLServer-SQL1:online:Failed to get the MSDTC Security configuration for VCS from registry.Error : [2, 2] 2015/05/16 20:47:50 VCS ERROR V-16-20093-11 SQLServer:SQLServer-SQL1:online:Failed to wait for the service 'MSSQL$SQL1' to start. Error = [2 ,258] 2015/05/16 20:47:50 VCS DBG_21 V-16-50-0 SQLServer:SQLServer-SQL1:online:*** Start of debug information dump for troubleshooting *** LibLogger.cpp:VLibThreadLogQueue::Dump[206] 2015/05/16 20:47:50 VCS DBG_21 V-16-50-0 SQLServer:SQLServer-SQL1:online:(2) CRegKey::Open failed for Software\Veritas\VCS\EnterpriseAgents\SQLServer\SQLServer-SQL1. LibVcsHive.cpp:VLibVcsHive::_GetDWORDValue[435] 2015/05/16 20:47:50 VCS DBG_21 V-16-50-0 SQLServer:SQLServer-SQL1:online:(2) CRegKey::Open failed for Software\Veritas\VCS\EnterpriseAgents\SQLServer\__Global__. LibVcsHive.cpp:VLibVcsHive::_GetDWORDValue[435] 2015/05/16 20:47:50 VCS DBG_21 V-16-50-0 SQLServer:SQLServer-SQL1:online:(2) _GetDWORDValue failed. Subkey = Software\Veritas\VCS\EnterpriseAgents\SQLServer\__Global__, Name = IgnoreMSDTCSecurity LibVcsHive.cpp:VLibVcsHive::GetValue[401] 2015/05/16 20:47:50 VCS DBG_21 V-16-50-0 SQLServer:SQLServer-SQL1:online:Wait timed out for service MSSQL$SQL1 LibService.cpp:VLibService::WaitForServiceStatus[275] 2015/05/16 20:47:50 VCS DBG_21 V-16-50-0 SQLServer:SQLServer-SQL1:online:*** End of debug information dump for troubleshooting *** LibLogger.cpp:VLibThreadLogQueue::Dump[217] 2015/05/16 20:47:50 VCS WARNING V-16-2-13140 Thread(10516) Could not find timer entry with id 274 2015/05/16 20:47:50 VCS INFO V-16-20093-29 SQLServer:SQLServer-SQL1:monitor:The 'MSSQL$SQL1' service is not in stopped or running state. State = 2. 2015/05/16 20:48:50 VCS INFO V-16-20093-29 SQLServer:SQLServer-SQL1:monitor:The 'MSSQL$SQL1' service is not in stopped or running state. State = 2. 2015/05/16 20:49:50 VCS INFO V-16-20093-29 SQLServer:SQLServer-SQL1:monitor:The 'MSSQL$SQL1' service is not in stopped or running state. State = 2. 2015/05/16 20:49:50 VCS ERROR V-16-2-13066 Thread(9380) Agent is calling clean for resource(SQLServer-SQL1) because the resource is not up even after online completed. 2015/05/16 20:49:50 VCS WARNING V-16-20093-55 SQLServer:SQLServer-SQL1:clean:The service 'MSSQL$SQL1' is not in running state. Attempt to stop it might be unsuccessful. 2015/05/16 20:53:32 VCS WARNING V-16-2-13140 Thread(9380) Could not find timer entry with id 279 2015/05/16 20:53:32 VCS ERROR V-16-2-13068 Thread(9380) Resource(SQLServer-SQL1) - clean completed successfully. 2015/05/16 20:53:32 VCS ERROR V-16-2-13071 Thread(9380) Resource(SQLServer-SQL1): reached OnlineRetryLimit(0). 2015/05/16 20:56:41 VCS NOTICE V-16-20093-75 SQLServer:SQLServer-SQL1:online:Failed to get the MSDTC Security configuration for VCS from registry.Error : [2, 2] There are two massages when service group became online 2015/05/16 20:58:58 VCS INFO V-16-20093-30002 SQLServer:SQLServer-SQL1:imf_register:Registering with IMF for online monitoring 2015/05/16 21:08:28 VCS INFO V-16-20093-30001 SQLServer:SQLServer-SQL1:imf_register:Registering with IMF for offline monitoring Can you heip me resolve this issue? Thanks in advance.
KANSTANTSIN
10 years ago Place Storage Foundation for Windows
1.3KViews
2likes
4Comments
vxio: Cluster software communication timeout. Reservation refresh has been suspended
Hi, We are experiencing this error on one of our clusters. It'sa two-node campus cluster with the following specifications SiteA Node1 is a Windows Server 2008 R2virtual machine residing on a ESXi 5.1 host in this site Disk1 and 3areLUNs in an enclosure in this site SiteB Node2 is a Windows Server 2008 R2 virtual machine residing on a ESXi 5.1 host in this site Disk2and 4areLUNs in an enclosure in this site We havecreated twoVMDGs, one contains Disk 1 and 2, while the other contains Disk 3 and 4.On these VMDGs, wehave created mirrored dynamic volumes.TheVMDGs arethen presented to the failover cluster. The quorum type on the failover cluster is a file share witness, onanother server. We are also running Microsoft System Center Configuration Manager to install updates and patches on Node 1 and 2. Whenever patches are installed on a node, it gets restarted. Whenever that occurs, failover from Node 1 to Node 2 occurs for the cluster resource group. Everything seems to failover just fine, and the VMDG is imported successfully (according to the log). But 10 minutes after the VMDG has been imported, the following error is logged on Node 2 http://s28.postimg.org/ubh8skfh9/vmdg2.png If I check the status of the VMDGs in VEA its Deported for both VMDGs. http://s3.postimg.org/72ort9683/vmdg3.png But even if the disks and VMDGs seem to be offline on the active node, failover does not occur, as in Failover Cluster Manager, the VMDG is online, but there are no volumes enumerated on it. http://s12.postimg.org/p31vncct9/vmdg1.png Has anyone else experienced the same, and knows why the status of the disks change to deported, without failover occuring?
Solved
Balthier35
10 years ago Place Storage Foundation for Windows
2.6KViews
2likes
6Comments
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?
Solved
bao0077
10 years ago Place Storage Foundation for Windows
1.2KViews
1like
2Comments
Blue Disk Icon in SFWHA against disk
I would like to know whether the blue information icon that I am seeing on the passive node of a sfwha cluster will clear when a failover is initiated. The issue has arisen following a recent disk expansion which all went well apart from the odd issue described, which was as follows: Break the Mirror on EMC CX4 Mirrorview Group on Unisphere Remove secondary image lun on Unisphere Delete the Mirrorview Group on Unisphere Expand lun attached to live server on CX4 within Unisphere Go into VEA on the active serverand do a rescan Then run the resize wizard to expand the disk, which in turn will show accordingly in windows explorer (Done on the fly without downtime to production system) Remove the secondary lun from the storage Group on the passive node of the CX4 array Expand the secondary lun on CX4 within Unispshere (encountered error on cx4 and ended up deleting lun and recreating at the new size) Recreate the Mirrorvirew Group using the active lunfrom the active node of the array on Unisphere Add the secondary lun back in to the Mirrorview Group on Unisphere This willstart the mirroring of luns from active to passive luns Lastly add the secondary lun back into the Storage group within Unisphere on the passive node of the array Once the above was done a final rescan was done on the passive server within VEA to ensure the disk could be seen. It is visible be with a blue informational icon against it and the only options you have is to reactivate. This is the same against all the other disks on in VEA in the passive node as well. The only thing I can think of is the we had an issue on cx4 when trying to expand the lun, so i ended up deleting the lun and recreating at the new size. It is not asking for a signature to be written, but I am wondering if the issue will write itself once a failover has been initiated in VCS from active to passive server, since there must be information within the dynamic disk cluster group, which this disk is apart of on the live server. Information on this in the administrator guides is as shown per attached. Do the server (passive node need a restart), I am assured there is no data loss etc, but I want to be sure thaty I can failover in a emergency. Any guidance would be appreciated. Thankyou
Solved
slick1
11 years ago Place Storage Foundation for Windows
1.9KViews
0likes
5Comments
Volume drive letters are not enumerated
Hello, I have a two node failover cluster which is running SQL Server 2008R2. The OS on the nodes is Server 2008 R2, and we are utilizing Veritas Storage Foundation for Windows 6.0.1 The issue is that at failover from Node01 to Node02, the Dynamic Disk Groups (of which there are 4) are imported just fine, but the volumes are not enumerated with Drive Letters. Therefore the SQL Instance fails, and no one is able to connect to the SQL database. In Failover Cluster Manager, the VMDG is imported just fine, and it is online, but the volumes have no drive letter, instead it says "failed to obtain the partition information" To rectify the issue, I have tried to install CP3 for VSFW 6.0.1 This CP inlucdes the following hotfix [11] Hotfix name: Hotfix_6_0_10012_308_3347495 Symptom: After a failover, VEA sometimes does not show the drive letter or mounted folder paths of a successfully-mounted volume. Description: This issue may occur after a failover when VEA sometimes does not show the drive letter or mounted folder paths of a volume even though the volume is successfully mounted with the expected drive letter or folder paths. During a failover, when a disk group gets imported, SFW mounts all volumes of the disk group by querying the mount points using Microsoft API GetVolumePathNamesForVolumeName(). Sometimes, this API fails to return the correct drive letter or mounted folder paths because of which VEA fails to update the same. Resolution: NOTE: Please note that using the following workaround has a performance impact on the service group offline and failover operations. This happens because, during the service group offline or failover operation, the performance of the disk group deport operation is impacted by "n/2" seconds maximum, where "n" is the number of volumes in the disk group. To resolve this issue, the operation needs to be retried after a few milliseconds so that the Microsoft API GetVolumePathNamesForVolumeName() returns correct information. As a workaround, a new retry logic is added to the GetVolumePathNamesForVolumeName() API so that it retries the operation in case the mount path returned is empty. It will retry after every 100 milliseconds for "n" number of attempts (5 by default), which can be configured using the registry. This retry logic is disabled by default. To use the workaround, do the following: 1. Enable the retry logic by changing the value of the registry entry "RetryEnumMountPoint" from 0 to 1 under the registry key - HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\VolumeManager 2. Configure the number of retry attempts by changing the value of the registry entry "RetryEnumMPAttempts" under the registry key - HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\VolumeManager Binary / Version: mount.dll / 6.0.10012.308 After installing the hotfix, two Dword Values were added to HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\VolumeManager They are called"RetryEnumMountPoint" and "RetryEnumMPAttempts", value of the former is 0, while value of the latter is 5. I did not change these values. At the next failover (to Node02) the drive letters were enumerated just fine. So I thought I had fixed the issue, but at the subsequent failover (to Node02), I had the same problem again. So from what I can gather, I have to change the value of"RetryEnumMountPoint"from 0 to 1. Which leads to my question. Has anyone ever experienced this issue, and if you have, could you please share your experience?
Solved
Balthier35
11 years ago Place Storage Foundation for Windows
2.1KViews
0likes
5Comments
Network connectivity loss solution
Hi all, Some time ago we experienced a total network failure between our to Datacenters. This failure only took place for a couple of seconds but it resulted in a active node and a node that was trying to start all instances. When connectivity was restored both nodes stopt working (to prevent splitbrain) My question: Is there a way to increase the timeinterval that dictates the nodes to take action in such a case? e.g.That the inactive node only starts when connectivity is lost for more than 5 minutes. Ivo
eu22106
13 years ago Place Storage Foundation for Windows
1.8KViews
1like
4Comments
Deporting/Importing Disk Group in VMware.
Hello. I am running SFHA 5.1 in a VMware environment. I created a 2 node cluster and the nodes failover perfectly. However when i create a disk group on a shared bus and deport it from the current node. It does not show up for importing in the other node. I have created the IP, NIC and VmDG resources and they are all online on the node the disk group was created on. However when i try to fail them over. the VmDG faults as it is not able to import itself on the other node. I tried both Windows server 2003 and 2008 and the problem persisted. Please note that i ran the '' Vxclus usesystembus ON '' command to enable the shared bus. I would really appreciate your help in this regard. Thanks Umair.
Solved
Umair_K
13 years ago Place Storage Foundation for Windows
1.5KViews
0likes
7Comments