Cluster Disk timed out, then failed event ID 1069
Hi. I have a six nodes Microsoft cluster nodes, Symantec Storage Foundation with SP1 is running. Recently I added a new node. Whenever I do a failover, the disk resources times out and failed then I have bring the disk resources online manually. Two error messages reported. One for timing out, 2nd for failure. Eror #1 (Event ID 1045) - Cluster resource<DiskResourceName>timed out. If the pending timeout is too short for this resource, consider increasing the pending timeout value Error #2 (Event ID 1069) - Cluster resource '<DiskName>' in Resource Group '<GroupName> Group' failed. Your help would be appreciated. Thanks Hatif9.4KViews0likes5CommentsHow to destroy a DG?
We removed some disk we no longer need but made an error in that a DG lost (unrecoverable) all its diskes. As this DG is not critical and we found some other small issues we want to remove the complete DG and create a new one. BUT. As the disks are in a deported state I am unbale to remove the DG. Is there a way around this issue? IvoSolved5KViews0likes6CommentsWindows File Share keeps getting lost on reboot of server
I wonder if anyone here can assist with this problem. We have a backup server which uses SFW5.0 which has a FC SAN connected o it. When we reboot the server it loses its File Share which we use to save all our backups to. The file share is located on a single volume, on an imported disk group. The volume comes up fine, but the share is always missing when we reboot. The only thing we can think of is that we had to implement a latestart on the Vertias service because it wasn't importing the disks correctly without this. Our feeling is that it might be to do with Microsoft waiting for the disk volume, when it doesn't see it, it stops trying to share the folder, perhaps because it is coming in so late as a result of the latestart. Has anyone encountered this or have a workaround to keep the shared folder coming up on reboots? NickSolved4.7KViews1like5CommentsUnknown 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.4KViews0likes11CommentsThe 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>2.8KViews1like6CommentsVM backup failing after installing SF Basic on Hyper-V Core server
Hi all, We have Hyper-V server with 10 virtual machines. We are using NetBackup 7.1.0.4 as backup software. Before installing SF Basic 6.0 , backup of all VM's was going fine. Now the backup of all VM's that are in running state is failing with error: Snapshot error encountered (156). Backup of VM's that are not running is going fine. I've installed SF Basic on a second Hyper-V server and I got the same situation. After that I've uninstalled SF Basic from this server and all backups are working fine. In the VEA console I can see the snapshots for the VM volumes created and after 2 minutes they are deleted. (screenshot in attacment) This is the error in the bpfis log from the NetBackup client: 10:58:01.940 [996.2672] <2> onlfi_vfms_logf: INF - snapshot services: vss:Thu May 10 2012 10:58:01.940000 <Thread id - 2672> VSS API ERROR:- API [QueryStatus] status = 42309 [VSS_S_ASYNC_PENDING] 10:58:31.332 [996.5336] <2> send_keep_alive: INF - sending keep alive 10:59:32.174 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:00:33.017 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:01:33.860 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:02:34.702 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:03:35.544 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:04:36.385 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:05:17.632 [996.4896] <2> onlfi_vfms_logf: INF - snapshot services: vss:Thu May 10 2012 11:05:17.632000 <Thread id - 4896> VssNode::getSelectedWriterStatus: GetWriterStatus FAILED for Selected writer [Microsoft Hyper-V VSS Writer], writer is in state [5] [VSS_WS_WAITING_FOR_BACKUP_COMPLETE]. hrWriterFailure [800423f4] [-2147212300] 11:05:17.632 [996.4896] <2> onlfi_vfms_logf: INF - snapshot services: vss:Thu May 10 2012 11:05:17.632000 <Thread id - 4896> VssNode::make getSelectedWriterStatus FAILED 11:05:17.632 [996.4896] <2> onlfi_vfms_logf: INF - vfm_freeze_commit: vfm_method_errno=[38] 11:05:17.632 [996.4896] <32> onlfi_fim_split: FTL - VfMS error 11; see following messages: 11:05:17.632 [996.4896] <32> onlfi_fim_split: FTL - Fatal method error was reported 11:05:17.632 [996.4896] <32> onlfi_fim_split: FTL - vfm_freeze_commit: method: Hyper-V, type: FIM, function: Hyper-V_make Does someone know what could be the problem? Are there any debuglogs in Storage Foundation to help me with this problem and where can I enable/find them?2.7KViews0likes3CommentsWindows 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? Thanks2.4KViews0likes1CommentError #1516 'Partition improperly dismounted' by PartitionMagic
Hi: Does anyone know how to fix a Partition described as 'improperly dismounted' (Error #1516) after running the chkdsk-scan within the PartitionMagic...? My PC-configuration is as follows: - Pentium II with 512 Meg RAM - DUAL-BOOT configuration consisting of Windows 98SE & XP-Home Edition where a separated (internal) Hard Disk is the one 'improperly dismounted' with WIN XP-Home Edition installed and which can NOT be boot to. - Have run the 'chkdsk /r /p' -scan several times from the Windows RECOVERY CONSOLE and the 'improperly dismounted' Partition problem has NOT been fixed. Any advice how to rectify this problem would be greatly appreciated...!Solved2.2KViews0likes1CommentStorage 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