04-05-2009
Hi,
we are doing this via 3DNS - the clusters are configured on both sides to connect to the 3DNS IP adress that fails over automatically to the DR site as soon as the PROD site is down.
Works perfectly fine.
Rgds
zxmaus
10 More Discussions You Might Find Interesting
1. High Performance Computing
Hello,
This might not be the right place to post my questions.
- I installed VCS 5.0 on the 2 nodes. What's next? I want to test the HA of NFS: i.e. the shared disk always accessible if one node goes down. How to do that?
- The management console was not installed. This is the GUI to manage... (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
2. Solaris
Is it possible to configure veritas cluster server using 2 Ldoms on same host? I just want to test and learn VCS. We can do a cluster (sun cluster3.2 ) in a box using 2 Ldoms but i 'm not sure if thats possible with veritas cluster or not ? (1 Reply)
Discussion started by: fugitive
1 Replies
3. Solaris
Hi,
We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover?
Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies
4. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
5. Gentoo
How to failover the cluster ? GNU/Linux
By which command,
My Linux version
2008 x86_64 x86_64 x86_64 GNU/Linux
What are the prerequisites we need to take while failover ?
if any
Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies
6. UNIX for Advanced & Expert Users
Hello,
Usually I use "vxresize" to grow vxfs directory in a stand-alone server without any problems, but I am just told to grow vxfs directorys in Veritas Cluster nodes.
Since I never done it before, would like to ask all the experts here to make sure the concept and steps will be fine... (1 Reply)
Discussion started by: sunnychen98
1 Replies
7. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
8. Solaris
Until I really began to explore the practical implications of using ZFS with VCS, I would not have necessarily realised the obstacles that would be put in my path. Data integrity is a must-have for storage in a shared host environment, so it surprised me to learn as I opened this particular... (0 Replies)
Discussion started by: cambridge
0 Replies
9. Red Hat
Hi Guys,
I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me.
How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Discussion started by: munna529
2 Replies
10. UNIX for Beginners Questions & Answers
Hi Experts,
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
#hastatus -sum
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
vxsited(1M) vxsited(1M)
NAME
vxsited - site monitoring daemon
SYNOPSIS
/etc/vx/bin/vxsited [mail_address...]
DESCRIPTION
The vxsited daemon monitors Veritas Volume Manager (VxVM) for disks being attached, and reattaches a detached site if the disks that belong
to that site become accessible.
vxsited analyzes the output of the vxnotify command, and waits for a failed disk to attach. When a disk is attached, vxsited attempts to
online the disk, and tries to reattach the failed site. If a site is successfully reattached, vxsited starts recovery using vxrecover, and
sends mail to root (by default) or to other specified users.
Mail Notification
By default, vxsited sends mail to root with information about the disk status of any attempts to reattach the site. To send mail to other
users, add the user login name to the line that starts vxsited in the startup script, /etc/init.d/vxvm-recover, and reboot the system. For
example, if the line appears as:
nohup vxsited root &
and you want mail also to be sent to user1 and user2, change the line to read:
nohup vxsited root user1 user2 &
Alternatively, kill the vxsite process, and restart it from the command line with the required mail addresses as arguments.
The mail notification has a format that is similar to the following:
Subject : Volume Manager site reattach on host hostname
Reattached site sitename in disk-group diskgroup
Reattachment Procedure
If a disk from a detached site becomes accessible again, vxsited checks whether the relocation daemon, vxrelocd, is running. If vxrelocd
is running, vxsited attempts to reattach the site. The relocation daemon can then try to relocate the failed subdisks using space on the
available disks in the disk group. If the failed objects are successfully relocated, vxrelocd changes the state of the site to RECOVER,
and starts the recovery of volumes at the site. When all the plexes at a site have been recovered, the plexes are put into the ACTIVE
state, and the state of the site is set to ACTIVE.
If vxrelocd is not running, vxsited only reattaches a site when all the disks from that site become accessible. After successfully reat-
taching a site, vxsited changes the site state to ACTIVE, and initiates recovery using vxrecover. When all the plexes from a site have been
recovered, the plexes are put into the ACTIVE state, and the state of the site is set to ACTIVE.
vxsited does not attempt to reattach a site that has been explicitly detached by an administrator. The state OFFLINE is set for sites that
have been detached by using the following command:
vxdg -g dg_name detachsite sitename
Disabling vxsited
If you do not want a site to be recovered automatically, kill the vxsited daemon, and prevent it from restarting. To kill the daemon, run
the following command from the command line, and locate the process table entry for vxsited:
ps -ef
Execute the command:
kill -9 PID
Substitute the process ID of the vxsited process for PID. To prevent vxsited from being restarted, comment out the line that starts
vxsited in the startup script /sbin/init.d/vxvm-recover.
FILES
/sbin/init.d/vxvm-recover The startup file for vxsited.
SEE ALSO
kill(1), mailx(1), ps(1), vxdg(1M), vxrelocd(1M), vxintro(1M), vxnotify(1M), vxrecover(1M)
VxVM 5.0.31.1 24 Mar 2008 vxsited(1M)