detaching vmdk files on vmware vm
When the application failover happens in VMware Guest enviorments, the VCS is responsible for failing over the application to other vm/vcs node on diffrent ESX host. In a scenario where the ESX/ESXi host itself faults, the VCS agents begin to fail over the application to the failover target system that resides on another host. The VMwareDisks agent communicates with the new ESX/ESXi host and initiates a disk detach operation on the faulted virtual machine. The agent then attaches the disk to the new failover target virtual machine. In this senario, how are the stale i/o from failing over guest/ESX host avoided? Are we on the mercy of VMware to take care of it? With SCSI3 PR this was the main problem that was solved. Moreover in such senario's even a garceful online detach wouldnt have gone through. I didnt find any references on VMware discussions forums as well. My customer wants to know about it, before he can deploy the application. Thanks, Raf
‘vxdmppr’ utility information
Hello, With VxVM, we get ‘vxdmppr’ utility which performs SCSI 3 PR operations on the disks similar to sg_persist on Linux. But we don’t find much documentation around this utility. In one of the blogs we saw that its unsupported utility. Can someone throw light on it. Has someone used it in the past? Or does anyone know how this utility is getting used in VxVM? How to know if this is supported or not? Rafiq
NFS agent for CFS share
Dear All, I have setup CFSshare. I can see under cfsshare display, but if I run "cfsshare share /emm2 rw" is NOT sharing but from the Java Console of the cluster. The NFS resource has got a question MARK. So I am really not too what to do now., root@node_1# cfsmount /emm5 rw Mounting... [/dev/vx/dsk/mobile_dg/mobile_vol_4] already mounted at /emm5 onnode_0 [/dev/vx/dsk/mobile_dg/mobile_vol_4] already mounted at /emm5 on node_1 root@node_1# cfsshare share /emm5 Warning: V-35-465: Resource [share3] is not online on system [node_0]. Warning: V-35-465: Resource [share3] is not online on system [node_1]. root@node_1# cfsshare display CNFS metadata filesystem : /locks Protocols Configured : NFS #RESOURCE MOUNTPOINT PROTOCOL OPTIONS share1 /emm2 NFS rw share2 /emm3 NFS rw share3 /emm5 NFS rw root@node_1# Regards, ThokozaniSymantec High Availability 6.1 Solution: Configuration in VMware Site Recovery Manager (SRM) environment
The Symantec High Availability 6.1 Solution provides scripts to perform some of the configuration tasks required for application monitoring continuity in a VMware SRM environment. In the event of a failure, when the SRM recovery plan is executed, the Symantec High Availability recovery command retrieves the application status, and the Symantec Cluster Server (VCS) network and application-specific agents bring the network and application components online. This ensures application monitoring continuity after the failover. For information about configuring the Symantec High Availability Solution in a VMware SRM environment, see: Configuring Symantec High Availability Solution in VMware SRM environment This quick reference guide provides: Acomplete workflow of the configuration tasks involved Aquick start for each high-level task Alist of reference documents and their download location Storage Foundation and High Availability and ApplicationHA documentation for other releases and platforms can be found on theSORT website.
Veritas InfoScale 7.0: Configuring I/O fencing
I/O fencing protects the data on shared disks when nodes in a cluster detect a change in the cluster membership that indicates a split-brain condition. In a partitioned cluster, a split-brain condition occurs where one side of the partition thinks the other side is down and takes over its resources. When you install Veritas InfoScale Enterprise, the installer installs the I/O fencing driver, which is part of the VRTSvxfen package. After you install and configure the product, you must configure I/O fencing so that it can protect your data on shared disks. You can configure disk-based I/O fencing, server-based I/O fencing, or majority-based I/O fencing. Before you configure I/O fencing, make sure that you meet the I/O fencing requirements. After you meet the requirements, you can refer to About planning to configure I/O fencing to perform the preparatory tasks and then configure I/O fencing. For more details about I/O fencing configuration, see: Cluster Server Configuration and Upgrade Guide Veritas InfoScale documentation for other releases andplatforms can be found on the SORT website.
