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
The wizard failed to discover the user database for instance SQL2
Operation system: Windows server 2012 R2 SFHA 6.1 Microsoft SQL Server 2012 - 11.0.2100.60 (X64)Microsoft SQL Server 2012 - 11.0.2100.60 (X64) I have two SQL instances in two nodes: SQL1 and SQL2. Instaled features: Database Engine Services; SQL server replication; Full-Text Search; Data Quality Services; Analysis Services; Reporting Services; Client Tools Connectivity; Integration Services; Management Tools – Basic; Management Tools – Complete SQL Client Connectivity SDK; Master Data ServicesMaster Data Services. I have configured first instance.First instance was configured without problem. Second inctance: In sql configuration wizard on sql server instance selection I selected SQL2 with SQLagent and Analisys. Then I got VCS warning "The wizard failed to discover the user database for instance SQL2" V-16-13-3535 I connected to SQL and saw all databases.
The error occurs when hastart.
product : sfwha 5.1 os : windows 2003 enterprise issue : The active normal, but when the hastart in the standby to the error occurred. hastart VCS INFO V-16-1-11020 Starting HAD on local node VCS ERROR V-16-11109 Cannot start had. Error=1068, ErrorText=The dependency service or group failed to start. -cluster status active node C:\Users\Administrator.AD> lltstat -n LLT node information: Node State Links 0 TEST1 OPEN 2 * 1 TEST2 OPEN 2 C:\Users\Administrator.AD> gabconfig -a GAB Port Memberships =============================================================== Port a gen 143b01 membership 01 Port h gen 143b03 membership ;1 Port h gen 143b03 visible 0 C:\Users\Administrator.AD> standby node C:\Users\Administrator.AD> lltstat -n LLT node information: Node State Links * 0 TEST1 OPEN 2 1 TEST2 OPEN 2 C:\Users\Administrator.AD> gabconfig -a GAB Port Memberships =============================================================== Port a gen 143b01 membership 01 C:\Users\Administrator.AD>
VSS snapshot of VxVM volumes fails
As the title says, VSS snapshot of my VxVM volumes is failing. System Description: W2k8 R2 SP1, FC-attached diks, SFWHA 6.0.1 installed Backup software being used: EMC NetWorker Problem: At this point, backup of the disks under VxVM (if that's not a totally obsolete terminology to use - I see Windows classes SFHA volumes as such in the registry, anyway) is failing. The strange thing is that it was working up until a certain point on Friday, at which point I did some un/re-configuring of the NetWorker client software on the machine, and then it stopped. Originally I also had VCS installed, and two nodes were acting as part of a cluster, but I removed VCS to try and narrow down the problem. Right now only Storage Foundations for Windows (HA) is installed on both machines. The disks are provisioned via FC, and are configured, one disk each, in disk groups "DG1" and "DG2". One group, "DG2", is imported and the single volume on it is mounted as "Y:\". When I attempt a backup of files on this volume, it just hangs for a long time (~30 minutes), until VSS finally times out, and then finally prodceeds to do a backup without a snapshot (legacy method, as we call it). This is what I get in the system logs through event viewer: Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{45a4f034-f1bb-422c-9ac1-332fe35e6386} - 0000000000000108,0x0053c008,000000000023D000,0,000000000023E010,4096,[0]). hr = 0x80070079, The semaphore timeout period has expired. . Operation: Processing EndPrepareSnapshots Context: Execution Context: System Provider The same happens whether the Veritas VSS provider is registered or not, or whether its service is running or not. In my efforts to troubleshoot this, the only thing I've noticed that may be a bit odd is that I have quite a few entries in the registry for volumes, more than I have actual physical volumes. The system has one "local" drive, and two under VxVM control. These are testing systems, and so have had SFW 5.2 installed previously, plus I have now installed and uninstalled SFW 6.0.1 several times while trying to trouble shoot this. Note that the GUID of one of them does match the error message above. Backup of the local (C:\) disk works normally. For all I know this may not be a SFW/VCS problem at all, but an issue with Microsoft's flaky (in my experience, anyway) VSS implementation. TIA, RyanTop Technotes for Veritas Storage Foundation for Windows - Updated Oct 2012
Here is the list of top Storage Foundation for Windows Support Technotes for the past quarter. Please make sure to browse the list first before you post a question here on Connect, as you may find an answer to the product issue you are seeing. Hope you find your answer here. Article Hyperlink Document Title http://www.symantec.com/docs/TECH152764 High CPU utilization by Symantec Service Management Framework Service (VxSMF.exe) http://www.symantec.com/docs/TECH50804 Troubleshooting missing disks, foreign disks and unknown disk groups (Unknown Dg) in Veritas Storage Foundation for Windows http://www.symantec.com/docs/TECH126804 VCS ERROR V-16-1-10600 Cannot connect to VCS engine http://www.symantec.com/docs/TECH83192 Using VxExplorer.exe to gather logs on servers running Veritas Storage Foundation for Windows and Veritas Storage Foundation for Windows High Availability 4.x, 5.x, and 6.x http://www.symantec.com/docs/TECH24718 How to identify which version of Veritas Volume Manager for Windows 2000 or Veritas Storage Foundation for Windows has been installed, using the product build number http://www.symantec.com/docs/TECH152806 Hardware Compatibility List (HCL) for Veritas Storage Foundation and High Availability Solutions 6.0, and 6.0 DDI_Q4_2011 for Windows and Veritas Dynamic Multi-Pathing 6.0 for Windows http://www.symantec.com/docs/TECH188801 How to install Microsoft SQL Server 2005 Service Pack 4 on one or more servers that are running Veritas Storage Foundation and High Availability Solutions for Windows http://www.symantec.com/docs/TECH153742 Software Compatibility List (SCL) for Veritas Storage Foundation and High Availability Solutions 6.0 for Windows and Veritas Cluster Server 6.0 for Windows http://www.symantec.com/docs/TECH49393 Disk read or write errors are reported by "vxio" in the Windows Event Viewer with Storage Foundation for Windows installed http://www.symantec.com/docs/TECH87418 Veritas Cluster Server(VCS) could not rebuild heartbeat and port membership since system reboot as SEP installed. http://www.symantec.com/docs/TECH84157 Configuration recommendations for Veritas Cluster Server Heartbeat communication within Storage Foundation for Windows with High Availability (SFW-HA) http://www.symantec.com/docs/TECH72086 How to use the SCSIcmd utility to perform various SCSI-2 and SCSI-3 reservation related actions. http://www.symantec.com/docs/TECH144432 Unable to access Windows Server 2008 file shares through the UNC path to a virtual server name or virtual server IP Address. http://www.symantec.com/docs/TECH27732 Why does SCSI-3 Persistent Group Reservation (PGR) need to be enabled when using Storage Foundation (tm) for Windows (SFW) Dynamic Multipathing (DMP) with the Active / Active I/O policy in a cluster environment? http://www.symantec.com/docs/TECH138719 Hardware Compatibility List (HCL) for Veritas Storage Foundation and High Availability Solutions 5.1 Service Pack 2 (SP2), and SP2 DDI_Q4_2011 for Windows and Veritas Dynamic Multi-Pathing 5.1 for Windows http://www.symantec.com/docs/TECH59755 Late Breaking News (LBN) Veritas Storage Foundation for Windows and High Availability Solutions 5.1.x for Windows and VeritasDynamic Multi-Pathing 5.1 for Windows http://www.symantec.com/docs/TECH83441 Ports that are used by Veritas Storage Foundation for Windows and Storage Foundation HA for Windows http://www.symantec.com/docs/TECH51494 How to restart the Veritas Enterprise Administrator and Storage Agent services in Veritas Storage Foundation for Windows http://www.symantec.com/docs/TECH37592 The description for Event ID ( 0 ) in Source ( VCS_AGFW ) cannot be found. http://www.symantec.com/docs/TECH66217 How to prevent split brain scenario in Storage Foundation for Windows High Availability (SFW HA) http://www.symantec.com/docs/TECH50295 Veritas Cluster Server 5.0 Administrator's Guide http://www.symantec.com/docs/TECH61937 V-76-58628-3 - Failed to write the disk signature. http://www.symantec.com/docs/TECH179175 Device Driver Installation Package Q4 2011 (DDI Q4 2011 package) for Veritas Storage Foundation 5.1 Service Pack 1 (SP1) and Higher for Windows and Veritas Dynamic Multi-Pathing 5.1 and higher for Windows http://www.symantec.com/docs/TECH48073 When executing SYMCLI syscalls when the array load balancing algorithm is set to round robin, they may hang and fail. http://www.symantec.com/docs/TECH138722 Software Compatibility List (SCL) for Veritas Storage Foundation and High Availability Solutions 5.1 Service Pack 2 (SP2) for Windows