Hello,

We have a Veritas cluster file system in 2 nodes. Now application team has requested to mount the cluster file system in both nodes at same time.

Current status of filesystem  is Active/Passive and customer request is to make that file system as Active/Active.

Is it possible to make Active/Active. If yes, please let me know the procoess...

Regards,

Chaitanya Bezawada. 

[root@cu:~]# /opt/VRTSvcs/bin/hares -modify VolGroup Critical 1
[root@cu ]# /opt/VRTSvcs/bin/hares -modify VolGroup Volume volname
[root@cu:~]# /opt/VRTSvcs/bin/hares -modify VolGroup DiskGroup appsdg
[root@cu:~]# /opt/VRTSvcs/bin/hares -modify VolGroup Enabled 1
[root@cu:~]#

i did mess up on the configuration how do i modify.# opt/VRTSvcs/bin/hares -modify VolGroup Volume volname
to # opt/VRTSvcs/bin/hares -modify VolGroup Volume sgproddata.

mig31

HAllo fellas I am i on the right direction and if you guys can advice on the next step fron here i will really appreciate, am i  formatting the filesystems and create mount points  using vxfs .and when shouls i link them

THANKS,

IN ADVANCE

root@system:scripts]# cd
[root@system:~]# /opt/VRTSvcs/bin/haconf -makerw
[root@system:~]# /opt/VRTSvcs/bin/hagrp-add appsGroup
bash: /opt/VRTSvcs/bin/hagrp-add: No such file or directory
[root@system:~]# /opt/VRTSvcs/bin/hagrp -add appsGroup
VCS NOTICE V-16-1-10136 Group added; populating SystemList and setting the Parallel attribute recommended before adding resources
[root@system:~]# /opt/VRTSvcs/bin/hagrp -modify appsGroup  systemlist system 1 system 2

[root@system:~]# /opt/VRTSvcs/bin/hagrp -autoenable appsGroup -sys system
[root@system:~]# /opt/VRTSvcs/bin/hares -add appsDG DiskGroup appsGroup
VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors
[root@int013:~]# /opt/VRTSvcs/bin/hares -modify appsDG Enabled 1
[root@int013:~]# /opt/VRTSvcs/bin/hares -modify appsDG DiskGroup appsdg
[root@system:~]# /opt/VRTSvcs/bin/hares -modify appsDG StartVolumes 0
[root@system:~]# /opt/VRTSvcs/bin/haconf -dump -makero
[root@system:~]# /opt/VRTSvcs/bin/hares -add SysIP IP appsGroup
VCS WARNING V-16-1-11335 Configuration must be ReadWrite : Use haconf -makerw
[root@system:~]# /opt/VRTSvcs/bin/haconf -makerw
[root@system:~]# /opt/VRTSvcs/bin/hares -add SysIP IP appsGroup
VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors
[root@system:~]# /opt/VRTSvcs/bin/hares -modify SysIP Device bond0:0
[root@system:~]# /opt/VRTSvcs/bin/hares -modify SysIP Address 10.152.179.8
[root@system:~]# /opt/VRTSvcs/bin/hares -modify SysIP Netmask 255.255.255.0
VCS WARNING V-16-1-10575 Attribute Netmask not defined
[root@system:~]# /opt/VRTSvcs/bin/hares -modify SysIP Critical 1
[root@system:~]# /opt/VRTSvcs/bin/hares -modify SysIP Enabled 1
[root@system:~]# /opt/VRTSvcs/bin/haconf -dump -makero
[root@system:~]# /opt/VRTSvcs/bin/hares -add SysNIC NIC appsGroup
VCS WARNING V-16-1-11335 Configuration must be ReadWrite : Use haconf -makerw
[root@system:~]# /opt/VRTSvcs/bin/haconf -makerw
[root@system:~]# /opt/VRTSvcs/bin/hares -add SysNIC NIC appsGroup
VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors
[root@system:~]# /opt/VRTSvcs/bin/hares -modify SysNIC device bond0:0
VCS WARNING V-16-1-10575 Attribute device not defined
[root@system:~]# /opt/VRTSvcs/bin/hares -modify SysNIC Enabled 1
[root@system:~]# /opt/VRTSvcs/bin/hares -add VolGroup Volume appGroup
VCS WARNING V-16-1-10133 Group does not exist: appGroup
[root@system:~]# /opt/VRTSvcs/bin/hares -add VolGroup Volume appsGroup
VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors
[root@system:~]# /opt/VRTSvcs/bin/hares -modify VolGroup Critical 1
[root@system:~]# /opt/VRTSvcs/bin/hares -modify VolGroup Volume volname
[root@system:~]# /opt/VRTSvcs/bin/hares -modify VolGroup DiskGroup appsdg
[root@system:~]# /opt/VRTSvcs/bin/hares -modify VolGroup Enabled 1
[root@system:~]#

[root@system:~]# /opt/VRTSvcs/bin/hares -modify VolGroup Critical 1
[root@system:~]# /opt/VRTSvcs/bin/hares -modify VolGroup Volume volname
[root@system:~]# /opt/VRTSvcs/bin/hares -modify VolGroup DiskGroup appsdg
[root@system:~]# /opt/VRTSvcs/bin/hares -modify VolGroup Enabled 1
[root@system:~]# /opt/VRTSvcs/bin/hares -add mntGroup Mount appsGroup
VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors
[root@system:~]# /opt/VRTSvcs/bin/hares -modify mntGroup BlockDevice /dev/vx/dsk/appsdg/Volname
[root@system:~]# /opt/VRTSvcs/bin/hares -modify mntGroup MountPoint /mntpoint
VCS WARNING V-16-1-10575 Attribute Mountpoint not defined
[root@system:~]# /opt/VRTSvcs/bin/hares -modify mntGroup FSType vxfs
[root@system:~]# /opt/VRTSvcs/bin/hares -modify mntGroup Critical 1
[root@system:~]# /opt/VRTSvcs/bin/hares -modify mntGroup Enabled

mig31

Virtualization, cloud and other new technologies are making the IT environment more complex to ensure continuity of services. And with disruption coming in many forms—from security threats and configuration errors to power outages and natural disasters—how do you protect your sprawling data, meet Service Level Agreements, stop malware and other threats or manage those virtual machines that seem to multiply like rabbits? Attend our webcast on May 21st at 10am PDT to learn best practices and get technology tips to protect your data wherever it resides, keep your critical applications highly available, and implement the right business continuity strategy for your virtual environment. If your only choice is, “Up” and “Running,” register for our webcast today. http://bit.ly/12vIzZ4

Why is the state of the second system showing uknown

[root@system1:log]# /opt/VRTSvcs/bin/hastatus -summary

-- SYSTEM STATE
-- System               State                Frozen

A  system1       RUNNING              0
A  system2       UNKNOWN              0

-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State        

B  ClusterService  system1       Y          N               ONLINE       
B  ClusterService  system2       Y          N               OFFLINE      
B  appsGroup       system1       N          Y               OFFLINE      
B  appsGroup       system2       Y          Y               OFFLINE      
B  vxfen           system1       Y          N               OFFLINE      
B  vxfen           system2       Y          Y               OFFLINE      

-- RESOURCES NOT PROBED
-- Group           Type                 Resource             System             

E  ClusterService  IP                   webip                system2     
E  ClusterService  NIC                  csgnic               system2     
E  appsGroup       DiskGroup            appsDG               system2     
E  appsGroup       IP                   SysIP                system1     
E  appsGroup       IP                   SysIP                system2     
E  appsGroup       Mount                mntGroup             system1     
E  appsGroup       Mount                mntGroup             system2     
E  appsGroup       NIC                  SysNIC               system1     
E  appsGroup       NIC                  SysNIC               system2     
E  appsGroup       Volume               VolGroup             system2     
E  vxfen           CoordPoint           coordpoint           system2     
[root@system1:log]#

Hello,

Could anyone please advise what is a proper way to migrate from existing Storage Foundation (for Windows) DMP support - to EMC PowerPath DMP?

I haven't seen any decent Tech Notes, White papers or other articles for this.

There is also Veritas Cluster Server and VVR Replication on top of existing SF DMP.

Any help would be very appreciated!

Would like to have the ability to issue a "notification blackout" for Oracle's OEM product, prior to database resources going down.  The use of a "pre-offline type trigger" would be very beneficial, as this is needed per DB resource.

5.0mp3rp2  on aix6106,

two disks' one primary path disabled, has changed dmp log level to 9, still no more logs, any tips?

==============

===========dmp event log

Having worked with Clustering for nearly fifteen years I believe this still qualifies me as  a total novice. It’s a bit like saying I work with cars, if I drive formula one car I won’t have much knowledge about stock car racing.  When we talk about cluster computing it normally refers to a number of computers working in some coordinated fashion. These will typically fall into two types,  shared disk and shared nothing.

Shared disk is the most recognized architecture and as the name would suggest simply means that all storage is available to all nodes in the cluster. Examples of this could be Oracle RAC or Storage Foundation Cluster Filesystem.  In both these instances a lock manager is required to manage to the coordinated access to the data. Shared disk architecture offers the highest levels of availability. Depending on the application it can often scale very badly in true parallel shared clusters. I often see this in Oracle RAC environments where due to the cache kept on each node the database is constantly chasing memory segments from other cluster nodes severely impacting database performance. Shared disk is normally the most costly and widely used of the architectures.

Shared nothing is another cluster mechanism which exists. Shared nothing does not involve concurrent access to disks, so no lock manager is required. Some would suggest that VERITAS Cluster Server could be considered a shared nothing technology since only one node in the cluster can access the data at a time. This is true unless you are using Veritas ClusterFilesystem. Ultimately though you are using shared storage which is presented to all hosts in the cluster. True shared nothing eliminates the need for expensive SAN shared storage and acts as an enabler for leveraging non shared storage. For example if I bought an X86 server with two internal drives, I could have my Operating system on one and an application on the other.  This however offers no resiliency in the face of hardware failures of either  server or storage. Using a shared nothing approach we could mirror our application data  to one or many servers in our cluster. Those  servers do not need to see the application data disk (not shared) the data will simply be replicated over the cluster interconnects and a synchronous copy will appear on the passive servers. Thus removing the need for expensive shared SAN storage. If you then consider a solution like VERITAS Cluster Server now you are able to monitor the application and if there was a failure of disk/server or application then control could be passed to one of the passive servers to restart the application with a consistent up to date copy of the data.  

Storage Foundation High Availability 6.1 is due out in October 2013 will make shared nothing clustering as described here a reality. There is already the building blocks in place which enable “data shipping” across the cluster interconnects. So for example in the event of loss of storage connectivity of a node, that node could continue to process requests and write the data over the interconnects on another server. This is the underlying technology that the shared nothing implementation uses. VERITAS Cluster Server today offers a standardized approach to application availability with the traditional active passive approach.  Storage Foundation HA will offer enterprises a very cost effective simple design to making their application highly available without any of the associated storage costs. As with all forms Business Continuity it is important to understand the service levels you need to maintain and map the solution accordingly. I would anticipate that the shared nothing approach may not fit the 99999 applications but will certainly be a good fit for less critical applications. The shared nothing implementation is branded Shared Storage Sharing and will available in October this year.

In case # 04360304 we had a problem with DHC and DHC MAPS which not could be solved and there is no workaround.

We would like to be able to administer /switch off DHC/DHC MAP

Environment:

OS = Linux (RHEL 6.4)

SFHA version 6.0.2

Kernel version = Linux secphoenix 2.6.32-358.el6.x86_64

I am trying to install SFHA version 6.0.2 on RHEL 6.4

All required package dependencies were resolved.

Checking system communication ..................................... Done
    Checking release compatibility .................................... Done
    Checking installed product ........................................ Done
    Checking prerequisite patches and rpms ............................ Done
    Checking platform version ......................................... Done
    Checking file system free space ................................... Done
    Checking product licensing ........................................ Done
    Performing product prechecks ...................................... Done

System verification checks completed successfully

While installing rpms, VRTSvxfs ended up with error but all other rpms installed successfully.

Veritas Storage Foundation and High Availability Install did not complete successfully

VRTSvxfs rpm failed to install on priphoenix
VRTSvxfs rpm failed to install on secphoenix

What could be the possible causes of this issue?

Hi Experts,

I would like to know if there is any other way to check what is causing some resources to go down unexpectedly?

[root@system1]# /opt/VRTSvcs/bin/hastatus -sum                  
-- SYSTEM STATE
-- System               State                Frozen

A  system1       RUNNING              0
A  system2       RUNNING              0

-- GROUP STATE
-- Group           System      Probed     AutoDisabled    State        

B  ClusterService  system1       Y          N               ONLINE       
B  ClusterService  system2       Y          N               OFFLINE      
B  appsGroup       system1       N          N               PARTIAL      
B  appsGroup       system2       N          N               OFFLINE      
B  vxfen           system1       Y          N               OFFLINE      
B  vxfen           system2       Y          N               OFFLINE      

-- RESOURCES NOT PROBED
-- Group           Type                 Resource             System             

E  appsGroup       IP                   SysIP                system1     
E  appsGroup       IP                   SysIP                system2     
E  appsGroup       Mount                mntGroup             system1     
E  appsGroup       Mount                mntGroup             system2     
E  appsGroup       NIC                  SysNIC               system1     
E  appsGroup       NIC                  SysNIC               system2     
 

cant get my SysIP online because the resource has not been probed how do you probe the appsgroups in bold

thanks

mig31

I have a problem that to add a low pri LLT with a public bond NIC with public IP on it.

bond0 is a bond of 2 eth NICs and each NIC connecting to a different router, and there is connection between 2 routers. The 2 IPs are in the same subnet, so there is no route issue.

After configure the bond0 as low pri LLT, lltstat shows the link DOWN on the other node from each side:

# lltstat -nvv|head
LLT node information:
Node State Link Status Address
0 server1 OPEN
eth1 UP E4:1F:13:2D:92:3P
eth3 UP 00:10:18:8C:3U:4D
bond0 DOWN
* 1 server2 OPEN
eth1 UP E4:1F:13:62:39:49
eth3 UP 00:10:18:8C:0B:93
bond0 UP E4:1F:13:62:94:05

[root@cdceap1d ~]# lltstat -nvv|head
LLT node information:
Node State Link Status Address
* 0 server1 OPEN
eth1 UP E4:1F:13:2D:92:3P
eth3 UP 00:10:18:8C:3U:4D
bond0 UP E4:1F:13:2D:0E:6D
1 server2 OPEN
eth1 UP E4:1F:13:62:39:49
eth3 UP 00:10:18:8C:0B:93
bond0 DOWN

LLT work on 2nd layer "Data Link Layer",  /opt/VRTSllt/lltping test cannot get through to each other. But arping with broadcast package can get through.

So my question is if the low pri LLT support public bond NIC with public IP ?

I found some notes :

LLT supports NIC bonding
You can configure NIC bonds (aggregated interfaces) as private links under LLT.
LLT treats each aggregated interface as a single link. So, you must configure these NICs that form the bond in such a way that the NICs are connected to the same switch or hub.
Note: If the NICs are connected to different switches or hubs, you must establish connection between the switches or hubs.

So according to the note, LLT only support NIC bonding as private links? Not with public IP ?

Any one has the experience would be huge appreciate.

Environment

OS = Windows 2008 SP2 (32bit)

SFHA = 5.1 SP2

Query

Few days ago my replication between two nodes was stopped and I saw the below message when I start replication. I ordered the License(VRTS STORAGE FOUNDATION HA 6.0 WIN NFR LIC) and applied the new License (and also removed the old License) from Control Panel=>Programs and Features=>SFHA 5.1SP2(Server components)=>Change=>License Management. But still I am seeing the below message when I start Replication.

How i can add Virtual ip for the groups in cluster service .

Thanks 

Regards

Solaris 10 ,SFRAC 5.1sp1rp2

===========

after reboot:

Hi,

We  have the following license:-

1.VRTS STORAGE FOUNDATION 6.0 WIN FOR OS TIER STANDARD EDITION PER SERVER STD LIC EXPRESS BAND S

2.VRTS STORAGE FOUNDATION OPTION VOLUME REPLICATOR 6.0 WIN FOR OS TIER STANDARD EDITION PER SERVER STD LIC EXPRESS BAND S

We the following infra:-

1. OS - Windows 2008 R2 Ent.

2. Application - Oracle database 11.2g.(Without RAC)

3. Hardware - RAM - 24GB; HDD - C:, D:, E:.

4. HDD - RAID configured in local system.

5. Oracle application is installed in C Driave and Database is in D Drive.

6. Bandwidth - 24mbps/18-20ms (Shared)

I am new in storage foundation.

Please, help me with my query.

1. Will the above license is enough to replicate the drives.

2. Oracle is in D drive will the software able to replicate the drive.

3. Is the shared bandwidth is enough to replicate in real time.

4. Is there any thing I need to check before installations.

5. Any por and corns ...(if any).

Please, provide the doc links for the same.

Thanks.

We have install SFHA 5.1SP1RP3 in Solaris 10 update 10.

When we configure the VCS zone agent to handle the Solaris 9 Branded Zone. It can online, offline the Solaris 9 Branded Zone in SFHA, but we see that Online the zone in agent, it show boot single user mode first, and then reboot to multi user mode. After boot in multi user mode, it is normal in VCS.

Is that any solution for boot multi user mode only?