Veritas volume replicator under sun cluster

Hi,
Can we use VVR under sun cluster server? We want to replicate data on sun cluster nodes to a seperate box which is not part of the sun cluster. Is there any special configuration needed?
Thanks and appreciate any response.

Don't forget you will also need to obtain a VXVM Cluster functionality license to use VXVM in a Sun cluster, which is a separate license key to the base VXVM.

Similar Messages

Beta Refresh Release Now Available! Sun Cluster 3.2 Beta Program

The Sun Cluster 3.2 Release team is pleased to announce a Beta Refresh release. This release is based on our latest and greatest build of Sun Cluster 3.2, build 70, which is close to the final Revenue Release build of the product.
To apply for the Sun Cluster 3.2 Beta program, please visit:
https://feedbackprograms.sun.com/callout/default.html?callid=%7B11B4E37C-D608-433B-AF69-07F6CD714AA1%7D
or contact Eric Redmond <[email protected]>.
New Features in Sun Cluster 3.2
Ease of use
* New Sun Cluster Object Oriented Command Set
* Oracle RAC 10g improved integration and administration
* Agent configuration wizards
* Resources monitoring suspend
* Flexible private interconnect IP address scheme
Availability
* Extended flexibility for fencing protocol
* Disk path failure handling
* Quorum Server
* Cluster support for SMF services
Flexibility
* Solaris Container expanded support
* HA ZFS
* HDS TrueCopy campus cluster
* Veritas Flashsnap Fast Mirror Resynchronization 4.1 and 5.0 option support
* Multi-terabyte disk and EFI label support
* Veritas Volume Replicator 5.0 support
* Veritas Volume Manager 4.1 support on x86 platform
* Veritas Storage Foundation 5.0 File System and Volume Manager
OAMP
* Live upgrade
* Dual partition software swap (aka quantum leap)
* Optional GUI installation
* SNMP event MIB
* Command logging
* Workload system resource monitoring
Note: Veritas 5.0 features are not supported with SC 3.2 Beta.
Sun Cluster 3.2 beta supports the following Data Services
* Apache (shipped with the Solaris OS)
* DNS
* NFS V3
* Java Enterprise System 2005Q4: Application Server, Web Server, Message Queue, HADB

Without speculating on the release date of Sun Cluster 3.x or even its feature list, I would like to understand what risk Sun would take when Sun Cluster would support ZFS as a failover filesystem? Once ZFS is part of Solaris 10, I am sure customers will want to use it in clustered environments.
BTW: this means that even Veritas will have to do something about ZFS!!!
If VCS is a much better option, it would be interesting to understand what features are missing from Sun Cluster to make it really competitive.
Thanks
Hartmut

Sun cluster with netapps filers

Has any one running sun cluster 3 with netapps filers. We would primary running oracle databases but would be running some apps servers as well.
There does appear to be some issues in rgard to the fact that NFS file locking is not the same as on a standard filesystem.
Also I can see how the logical host would be setup to mount a NFS filesystem instead of say mounting a filesystem that is using volume maanager

Today, only Oracle RAC is supported under Sun Cluster 3.1
using NetApp filers as shared storage. RAC has a builtin
distributed lock manager to arbitrate access to the shared
files. If you want to use your own application, then it needs
a lock manager or you can wait for a later Sun Cluster release.
-- richard

Jboss configuration on Sun Cluster 3.1

Hi.
I am using generic Data Services to manage JBoss instance under Sun Cluster. the command is as follows.
scrgadm -a -j jboss_resource -g cluster_failover_rg -t SUNW.gds \
-y Scalable=false -y Start_timeout=900 \
-y Stop_timeout=420 -x Probe_timeout=300 \
-y Port_list="8080/tcp" \
-y Resource_dependencies=oracle_server_resource \
-x Start_command='/bin/su mform -c "/usr/msm40/scripts/startup/jboss.sh start"' \
-x Stop_command='/bin/su mform -c "/usr/msm40/scripts/startup/jboss.sh stop"' \
-x Child_mon_level=0 -x Failover_enabled=true -x Stop_signal=9
My jboss script will take about 8 to 10 minutes to start completely as it is designed to start about 10 child processes. Hence I set the time out as 15 minutes.
But while starting the resource I found following messages on the console.
Oct 6 12:45:29 MFIN-SOL01 SC[SUNW.gds:5,cluster_failover_rg,jboss_resource,gds_
svc_start]: Failed to connect to host msm and port 8080: Connection refused.
Oct 6 12:45:29 MFIN-SOL01 SC[SUNW.gds:5,cluster_failover_rg,jboss_resource,gds_
svc_start]: Failed to connect to the host <msm> and port <8080>.
Oct 6 12:45:31 MFIN-SOL01 SC[SUNW.gds:5,cluster_failover_rg,jboss_resource,gds_
svc_start]: Failed to connect to host msm and port 8080: Connection refused.
Oct 6 12:45:31 MFIN-SOL01 SC[SUNW.gds:5,cluster_failover_rg,jboss_resource,gds_
svc_start]: Failed to connect to the host <msm> and port <8080>.
Oct 6 12:45:33 MFIN-SOL01 SC[SUNW.gds:5,cluster_failover_rg,jboss_resource,gds_
svc_start]: Failed to connect to host msm and port 8080: Connection refused.
Oct 6 12:45:33 MFIN-SOL01 SC[SUNW.gds:5,cluster_failover_rg,jboss_resource,gds_
svc_start]: Failed to connect to the host <msm> and port <8080>.
Oct 6 12:45:35 MFIN-SOL01 SC[SUNW.gds:5,cluster_failover_rg,jboss_resource,gds_
svc_start]: Failed to connect to host msm and port 8080: Connection refused.
Oct 6 12:45:35 MFIN-SOL01 SC[SUNW.gds:5,cluster_failover_rg,jboss_resource,gds_
svc_start]: Failed to connect to the host <msm> and port <8080>.
here msm is the logical hostname i have selected and port 8080 is used by jboss instance.
after throwing these error messages the cluster software failes over to the other node and changes the status to offline after several attempts.
I tried starting the instance manually and it worked fine.
Please let me know if I am missing something.
Thanks in advance for the help.

Found the solution. Added delay at the end of start script. This may be because jboss takes some time to bind the ports and the hostname.

Sun cluster quorum disk

Hi,
I just want to know how to assign quorum disk under Sun cluster. Can I use LUN disk that is shared for both node as quorum disk and do I need to bring the disk first to vxvm control before using it as quorum disk? Appreciate any response/advise.
Thanks.

No you don't need to bring the disk into VXVM control.
First run scdidadm -L from either node. This will give you a list of shared disk devices. Find one that is shared between the nodes and note its DID. ie d21
scconf -a -q globaldev=d21
Once you have added a quorum disk you can set install mode to off.
scconf -c -q installmodeoff
I would also recommend reading this:
http://docs.sun.com/app/docs/doc/816-3384/6m9lu6fig?q=sun+cluster+add+quorum+disk&a=view
Then reset you quorum count.
scconf -c -q reset

QFS Meta data resource on sun cluster failed

Hi,
I'm trying to configure QFS on cluster environment, to configure metadata resource faced error. i tried with different type of qfs none of them worked.
[root @ n1u331]
~ # scrgadm -a -j mds -g qfs-mds-rg -t SUNW.qfs:5 -x QFSFileSystem=/sharedqfs
n1u332 - shqfs: Invalid priority (0) for server n1u332FS shqfs: validate_node() failed.
(C189917) VALIDATE on resource mds, resource group qfs-mds-rg, exited with non-zero exit status.
(C720144) Validation of resource mds in resource group qfs-mds-rg on node n1u332 failed.
[root @ n1u331]
~ # scrgadm -a -j mds -g qfs-mds-rg -t SUNW.qfs:5 -x QFSFileSystem=/global/haqfs
n1u332 - Mount point /global/haqfs does not have the 'shared' option set.
(C189917) VALIDATE on resource mds, resource group qfs-mds-rg, exited with non-zero exit status.
(C720144) Validation of resource mds in resource group qfs-mds-rg on node n1u332 failed.
[root @ n1u331]
~ # scrgadm -a -j mds -g qfs-mds-rg -t SUNW.qfs:5 -x QFSFileSystem=/global/hasharedqfs
n1u332 - has: No /dsk/ string (nodev) in device.Inappropriate path in FS has device component: nodev.FS has: validate_qfsdevs() failed.
(C189917) VALIDATE on resource mds, resource group qfs-mds-rg, exited with non-zero exit status.
(C720144) Validation of resource mds in resource group qfs-mds-rg on node n1u332 failed.
any QFS expert here?

hi
Yes we have 5.2, here is the wiki's link, [ http://wikis.sun.com/display/SAMQFSDocs52/Home|http://wikis.sun.com/display/SAMQFSDocs52/Home]
I have added the file system trough webconsole, and it's mounted and working fine.
after creating the file system i tried to put under sun cluster's management, but it asked for metadata resource and to create metadata resource I have got the mentioned errors.
I need the use QFS file system in non-RAC environment, just mounting and using the file system. I could mount it on two machine in shared mode and high available mode, in both case in the second node it's 3 time slower then the node which has metadata server when you write and the same read speed. could you please let me know if it's the same for your environment or not. if so what do you think of the reason, i see both side is writing to the storage directly but why it's so slow on one node.
regards,

WAAS and Symantec Vertitas Volume Replicator

Hi,
We are forwarding Symantec replication traffic via our WAAS infrastructure over a 20Mb WAN link. The CM appears to register the traffic but does not optimize it at all. Has anyone had any experience with WAAS and Symantec Veritas Volume Replicator (VVR) 4.3?

I tested with VVR in the lab. VVR default uses UDP and using the nerd knob in the GUI did not force VVR to start using TCP. To get VVR to use TCP, I had to input these commands:
vrport data 1999-1999
vrport heartbeat 2000-2000
or use what ever ports you want to use. The previous answer was asking if you were seeing TCP sessions in the WAE's. This can be seen by telneting to the WAE and issueing a "show tfo connection summary". Can you post the output of that command?

Does SUN CLUSTER WARE support ASM?

Does SUN CLUSTER WARE support ASM?
Where can I find the answer ? Thanks.

I am not an expert but here it goes. Sun Cluster is used for clustering machines processes but NOT really used for clustering disks. This has to be done through third party software like Veritas. BUT why Sun Cluster the machines when you can cluster via Oracle CRS? CRS then uses ASM for clustered disks. Bingo you save money on Sun Cluster Software and Veritas software.
One day Oracle will rule the world!

Veritas required for Oracle RAC on Sun Cluster v3?

Hi,
We are planning a 2 node Oracle 9i RAC cluster on Sun Cluster 3.
Can you please explain these 2 questions?
1)
If we have a hardware disk array RAID controller with LUNs etc, then why do we need to have Veritas Volume Manager (VxVM) if all the LUNS are configured at a hardware level?
2)
Do we need to have VxFS? All our Oracle database files will be on raw partitions.
Thanks,
Steve

> We are planning a 2 node Oracle 9i RAC cluster on Sun
Cluster 3.Good. This is a popular configuration.
Can you please explain these 2 questions?
1)
If we have a hardware disk array RAID controller with
LUNs etc, then why do we need to have Veritas Volume
Manager (VxVM) if all the LUNS are configured at a
hardware level?VxVM is not required to run RAC. VxVM has an option (separately
licensable) which is specifically designed for OPS/RAC. But if
you have a highly reliable, multi-pathed, hardware RAID platform,
you are not required to have VxVM.
2)
Do we need to have VxFS? All our Oracle database
files will be on raw partitions.No.
IMHO, simplify is a good philosophy. Adding more software
and layers into a highly available design will tend to reduce
the availability. So, if you are going for maximum availabiliity,
you will want to avoid over-complicating the design. KISS.
In the case of RAC, or Oracle in general, many people do use
raw and Oracle has the ability to manage data in raw devices
pretty well. Oracle 10g further improves along these lines.
A tenet in the design of highly available systems is to keep
the data management as close to the application as possible.
Oracle, and especially 10g, are following this tenet. The only
danger here is that they could try to get too clever, and end up
following policies which are suboptimal as the underlying
technologies change. But even in this case, the policy is
coming from the application rather than the supporting platform.
-- richard

Veritas Volume manager 4.0 with Sun StorEdge 3310 D

I am running into a problem. The vxconfigd deamon always dump core when rebooting.
Our environment is listed below.
OS environemt.
     SunOS server1 5.8 Generic_117350-43 sun4u sparc SUNW,Sun-Fire-V240
Software installed.
     Sun Cluster 3.0
     Veritas Volume Manager 4.0 MP2.
Disk Array associated.
     Sun StorEdge 3310 D.
I looked up veritas.com and find Array Support Library (ASL) for Sun StorEdge 3xxx Series is recommended. But I didn't find this library is running on this server.
Please refer to this following link
http://support.veritas.com/docs/277923
As our system is one of critical systems and I'd like to confirm that I can follow up this procedure without doing harm things to our system.
Jeff

No problem Jeff :)
I took a look at the Veritas doc and you're right it does seem to cover everthing.
Has the vxconfigd core dumped since the start? ie from the moment it was installed?
I have installed VXVM 4.0 with Solaris 8 but without the ASL and this worked ok, I know that's not much help to you but I am not sure the ASL will help. Mind you I have not installed it with Sun Cluster 3.0.

Storagetek 6140 - chunk size? - veritas and sun cluster tuning?

hi, we've just got a 6140 and i did some raw write and read tests -> very nice box!
current config: 16 fc-disks (300gbyte / 2gbit/sec): 1x hotspare, 15x raid5 (512kibyte chunk)
3 logical volumes: vol1: 1.7tbyte, vol2: 1.7tbyte, vol3 rest (about 450gbyte)
on 2x t2000 coolthread server (32gibyte mem each)
it seems the max write perf (from my tests) is:
512kibyte chunk / 1mibyte blocksize / 32 threads
-> 230mibyte/sec (write) transfer rate
my tests:
* chunk size: 16ki / 512ki
* threads: 1/2/4/8/16/32
* blocksize (kibyte): .5/1/2/4/8/16/32/64/128/256/512/1024/2048/4096/8192/16384
did anyone out there some other tests with other chunk size?
how about tuning veritas fs and sun cluster???
veritas fs: i've read so far about write_pref_io, write_nstream...
i guess, setting them to: write_pref_io=1048576, write_nstream=32 would be the best in this scenario, right?

I've responded to your question in the following thread you started:
https://communities.oracle.com/portal/server.pt?open=514&objID=224&mode=2&threadid=570778&aggregatorResults=T578058T570778T568581T574494T565745T572292T569622T568974T568554T564860&sourceCommunityId=465&sourcePortletId=268&doPagination=true&pagedAggregatorPageNo=1&returnUrl=https%3A%2F%2Fcommunities.oracle.com%2Fportal%2Fserver.pt%3Fopen%3Dspace%26name%3DCommunityPage%26id%3D8%26cached%3Dtrue%26in_hi_userid%3D132629%26control%3DSetCommunity%26PageID%3D0%26CommunityID%3D465%26&Portlet=All%20Community%20Discussions&PrevPage=Communities-CommunityHome
Regards
Nicolas

Is Veritas- or Sun Cluster needed for RAC in a Solaris Environment

Is a Veritas- or Sun Cluster needed for RAC in a Solaris Environment?
Does anyone know, when OCFS will be available for Solaris?

You don't need Veritas Cluster File System, but until OCFS comes out for Solaris you need to think about backups. If you've not got a backup solution that can integrate with rman for an SBT device then backups become more tricky.
If you use ASM then you can take a backup to a "cluster filesystem" (although ASM is raw partitions think of it as a cluster filesystem), that both nodes can see. BUT you then need to get these to tape somehow, unless you've got NetBackup et al. that support RMAN and can backup direct to tape you're more stuck.
Too many people don't think about this. You could create an NFS mount and backup to this from the nodes.

Upgrading Solaris OS (9 to 10) in sun cluster 3.1 environment

Hi all ,
I have to upgrade the solaris OS 9 to 10 in Sun cluster 3.1.
Sun Cluster 3.1
data service - Netbackup 5.1
Questions:
1 .Best ways to upgrade the Solaris 9 to 10 and the Problems while upgrading the OS?
2 .Sun Trunking support in Sun Cluster 3.1?
Regards
Ramana

Hi Ramana
We had used the live upgrade for upgrading Solaris 9 to 10 and its the best method for less downtime and risk but you have to follow the proper procedure as it is not the same for normal solaris. Live upgrade with sun cluster is different . you have to take into consideration about global devices and veritas volume manager. while creating new boot environment.
Thanks/Regards
Sadiq

Does oracle clusterware and oracle RAC require sun cluster

Hi,
I have to setup oracle RAC on solaris 10 SPARC. so is it necessary to install sun cluster 3.2, QFS file system on solaris
I have 2 sun sparc servers with solaris 10 installed on it and shared LUN setup(SAN disk RAID 5 partitions)
Have to have 2 node setup for RAC load balancing.
Regards
Prakash

Hi Prakash,
very interesting point:
As per oracle clusterware documents the cluster manager support is only for windows and linux.
In case of solaris SPARC will the cluster manager get configured ???
The term "Cluster Manager" refers to a "cluster manager" that Oracle used in 9i times and this one was indeed only available on Linux / Windows.
Therefore, let me, please, ask you something: Which version of Oracle RAC do you plan to use?
Because for 9i RAC, you would need Sun or Veritas Cluster on Solaris. The answers given here that Sun Cluster would not be required assume 10g RAC or higher.
Now, you might see other dependencies which can be resolved by Sun Cluster. I cannot comment on those.
For the RAW setup: having RAW disks (not raw logical volumes) will be fine without Veritas and ASM on top.
Hope that helps. Thanks,
Markus

Sun Cluster question

Hello everyone
I've inherited an Oracle Solaris system holding ASE Sybase databases. The system consists of two nodes inside a Sun Cluster. Each of the nodes is hosting 2 Sybase database instances, where one of the nodes is active and other is standing by. The scenario at hand is that when any of the databases on one node fails for whatever reason, the whole system gets shifted to the second node to keep the environment going. That works fine.
My intended scenario:
Each node is holding 2 database instances, both nodes ARE working at the same time so that each one is serving one instance of the database. In the event of failure on one node, the other one should assume the role of BOTH database instances till the first one gets fixed.
The question is: is that possible? and if it is, does that require breaking the whole cluster and rebuilding it? or can this be done online without bringing down the system?
Thanks a lot in advance

What you propose will not work either. E.g. there is no logic implemented to fence the underlying zpool from one node to the other in such a configuration.
Also the current SUNW.HAStoragePlus(5) manpage document:
        Note -   SUNW.HAStoragePlus does not support file sys-
                 tems created on ZFS volumes.
                 You cannot use SUNW.HAStoragePlus to manage a
                 ZFS storage pool that contains a file system for
                 which the ZFS mountpoint property is set to
                 legacy or none.[...]
Greets
Thorsten

Veritas volume replicator under sun cluster

Similar Messages

Maybe you are looking for