07-06-2013
Quote:
Originally Posted by
elcounto
Problem is there are now 3 VG's that have been set-up outside of the cluster.
First off, i suggest updating the OS to 5.3 if possible anyhow. 5.2 is not only outdated and no longer supported, it is also a nightmare of bugs and most of them are corrected in 5.3.
Regarding your question: you will need downtime for this: change the VGs to "enhanced concurrent", then varyoff them on their original system and do a "learning import" on the other system. (Corollary: do yourself a favour and make sure you have the same major number for the VGs across all your systems. This makes administration easier.)
Define your new resource groups based on these VGs then and do a "extended verification and synchronisation" via C-SPOC.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. Emergency UNIX and Linux Support
hello Gurus,
My current set up is 3 to 1 Cluster (SUN Cluster 3.2) running oracle database. Task is to reboot the servers. My query is about the procedure to do the same.
My understanding is suspend the databases to avoid switchover. Then execute the command scshutdown to down the cluster... (4 Replies)
Discussion started by: EmbedUX
4 Replies
2. Shell Programming and Scripting
Hello All,
Anybody knows how can I run script on the AIX HACMP offline node, without logon a offline node?
I would like to run a script on the online node and at same time or after the online node on the offline node.
Any IDEA? :confused: (3 Replies)
Discussion started by: kalaso
3 Replies
3. AIX
Hi all,
I was wondering if someone direct me in how to Make system backup for 2 nodes HACMP cluster ( system image ) .
What are the consideration for this task (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies
4. Solaris
Hi
we have 2 solaris 10 servers in veritas cluster.
also we have oracle cluster on the database end.
now we have a requirement to reboot both the servers as it has been running for more than a year.
can any one tell what is the procedure to bring down the cluster services in both the nodes... (7 Replies)
Discussion started by: newtoaixos
7 Replies
5. Red Hat
Hi all.
May I get some expert advice on troubleshooting performance issues of a 1000 nodes Apache LB cluster. Users report slow loading/response of webpages. Different websites are hosted on this cluster for different clients. But all are reporting the same issue.
Could you please let me know... (1 Reply)
Discussion started by: admin_xor
1 Replies
6. AIX
As i have updated a lot of HACMP-nodes lately the question arises how to do it with minimal downtime. Of course it is easily possible to have a downtime and do the version update during this. In the best of worlds you always get the downtime you need - unfortunately we have yet to find this best of... (4 Replies)
Discussion started by: bakunin
4 Replies
7. UNIX for Advanced & Expert Users
Is there any way to create a arbitrary node for ocfs2 on a virtual machine (others are physical servers) so it won't go panic when one of physical server goes down?
This is for load balanced application servers.
Any setting example or tips?
Thanks. (0 Replies)
Discussion started by: malayo
0 Replies
8. Red Hat
Hi All;
I try to build a Redhat Cluster (CentOS 6) on vmware. But each node sees the other down like:
# clustat
Cluster Status for mycluster @ Wed Apr 8 11:01:38 2015
Member Status: Quorate
Member Name ID Status
------ ---- ... (0 Replies)
Discussion started by: Meacham12
0 Replies
9. Red Hat
Hi All;
I try to build a Redhat Cluster (CentOS 6) on vmware. But each node sees the other down like:
# clustat
Cluster Status for mycluster @ Wed Apr 8 11:01:38 2015
Member Status: Quorate
Member Name ID Status
------ ---- ... (1 Reply)
Discussion started by: Meacham12
1 Replies
10. AIX
HI Admin,
I have running 2 node HACMP cluster- AIX 6.1. I just set it up.
It does sync completely without any errors. But it take too long to sync. More than 30 mins... any reasons? Where can I start looking into ?
Same network, same Subnet (1 Reply)
Discussion started by: snchaudhari2
1 Replies
LEARN ABOUT HPUX
cmhaltnode
cmhaltnode(1m) cmhaltnode(1m)
NAME
cmhaltnode - halt a node in a high availability cluster
SYNOPSIS
cmhaltnode [-f] [-v] [-t] [node_name...]
DESCRIPTION
cmhaltnode causes a node to halt its cluster daemon and remove itself from the existing cluster.
To halt cluster on the node, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configu-
ration file. See access policy in cmquerycl.
When cmhaltnode is run on a node, the cluster daemon is halted and, optionally, all packages that were running on that node are moved to
other nodes if possible.
If node_name is not specified, the cluster daemon running on the local node will be halted and removed from the existing cluster.
If you issue this command while a cluster is still in the process of forming, the command will fail with the message "Unable to connect to
daemon." If this happens, wait for the cluster to form successfully, then issue the command again.
Options
cmhaltnode supports the following options:
-f Force the node to halt even if there are packages or group members running on it. The group members on the node will be
terminated. The halt scripts for all packages running on the node will be run; based on priority or dependency relation-
ships, this may affect packages on other nodes. In other words, packages on other nodes may either start or halt based on
this package halting. If the package configuration and current cluster membership permit, and if the package halt script
succeeds, the packages will be started on other nodes. Without this option, if packages are running on the given node,
the command will fail. If a package fails to halt, the node halt will also fail.
-v Verbose output will be displayed.
-t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages.
This option validates the node's eligibility with respect to the package dependencies as well as the external dependencies
such as EMS resources, package subnets, and storage before predicting any package placement decisions. If there is a pack-
age in maintenance mode running on the nodes being halted, the package will always be halted and not failover to another
node; the report will not display an assessment for that package.
node_name...
The name of the node(s) to halt.
RETURN VALUE
cmhaltnode returns the following value:
0 Successful completion.
1 Command failed.
EXAMPLES
Halt the cluster daemon on two other nodes:
cmhaltnode node2 node3
AUTHOR
cmhaltnode was developed by HP.
SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmruncl(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmhaltnode(1m)