Apple Qmaster: Optimizing cluster storage capacity
By default, the Apple Qmaster distributed processing system saves temporary process files in the /var/spool/qmaster directory on the cluster controller's startup disk. Computers in the cluster will access this location as needed. If you are processing large source media files that exceed the available storage space on the startup disk, you may run out of storage space on that disk.
Hi
I want the Sync file server together (at the moment)
All server to a web server
What can I do to update Joomla or WordPress files even when taken together are equal
Databases together are replicated
What is the solutions ?
Thanks (2 Replies)
HI AIX experts,
We have a 2-node cluster version 6.1. Running 7 oracle dbs. Everything is on symmetrix. We are going to have a storage migration from one array to another. There will be SRDF setup between two arrays. I will be getting all the luns from new array. I am just looking for the... (7 Replies)
Hi Bros,
I am a newbie to this cluster environment...my workplace is a mess of Sun solaris server, oracle database, Cisco switch, router, MS Server, Windows PC..so and so..now my boss ask me to come out with a procedure for maintenance of storage array in our sun cluster environment..I read few... (12 Replies)
After much hitting my head to the wall with this meesages
root@crasher /workzone/dvd4_sfb-sol_x64]#./installer -verbose -installonly
5.0MP3 Installation Program
Copyright (c) 2008 Symantec Corporation. All rights reserved. Symantec, the Symantec... (1 Reply)
cmrunnode(1m)cmrunnode(1m)NAME
cmrunnode - run a node in a high availability cluster
SYNOPSIS
cmrunnode [-v] [node_name...] [-t | -w none]
DESCRIPTION
cmrunnode causes a node to start its cluster daemon to join the existing cluster. This command verifies the network configuration before
causing the node to start its cluster daemon.
To start a cluster on one of its nodes, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the clus-
ter configuration file. See access policy in cmquerycl(1m).
Starting a node will not cause any active packages to be moved to the new node. However, if a package is DOWN, has its switching enabled,
and is able to run on the new node, that package will automatically run there.
If node_name is not specified, the cluster daemon will be started on the local node and will join the existing cluster.
Options
cmrunnode supports the following options:
-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. The -w
option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet
any external dependencies such as EMS resources, package subnets, and storage.
node_name...
Start the cluster daemon on the specified node(s).
-w none
By default network probing is performed to check that the network connectivity is the same as when the cluster was configured.
Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should
only be used if this network configuration is known to be correct from a recent check.
RETURN VALUE
cmrunnode returns the following value:
0 Successful completion.
1 Command failed.
EXAMPLES
Run the cluster daemon on the current node:
cmrunnode
Run the cluster daemons on node1 and node2:
cmrunnode node1 node2
AUTHOR
cmrunnode was developed by HP.
SEE ALSO cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmruncl(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmrunnode(1m)