04-06-2009
Quote:
Originally Posted by
zxmaus
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.
Thanks for the reply.
Unfortunately, we do not have that option.
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
lockd(8c) lockd(8c)
Name
lockd - network lock daemon
Syntax
/usr/etc/lockd [ -t timeout ] [ -g graceperiod ]
Description
The daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking service
makes this advisory locking support possible by using the system call and the subroutine. The daemon forwards lock requests for remote
data to the server site's lock daemon. The daemon then requests the status monitor daemon, for monitor service. The reply to the lock
request is not sent to the kernel until the status daemon and the server site's lock daemon have replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site daemons to submit reclaim requests. Client site daemons are noti-
fied by of the server recovery and promptly resubmit previously granted lock requests. If a client site's daemon fails to secure previ-
ously granted locks at the server site, the daemon sends the signal SIGLOST to all the processes that were previously holding locks and
cannot reclaim them.
Options
-t timeout The daemon uses timeout (in seconds) as the interval instead of the default value of 15 seconds to retransmit a lock
request to the remote server.
-g graceperiod The daemon uses graceperiod (in seconds) as the grace period duration instead of the default value of 45 seconds.
See Also
fcntl(2), lockf(3), signal(3), statd(8c)
lockd(8c)