Sponsored Content
Full Discussion: backup NIM client
Operating Systems AIX backup NIM client Post 302297107 by lo-lp-kl on Thursday 12th of March 2009 01:28:33 PM
Old 03-12-2009
backup NIM client

Thanks for the response bakunin

I tried to to that option too, but I got this message when I try to backup a client.


Command: failed stdout: yes stderr: no

Before command completion, additional instructions may appear below.

0042-001 nim: processing error encountered on "master":
0042-081 m_mkbosi: a resource already exists on "master" at
location "/export/nim/lpp_source/aix53TL7"; due to NFS export restrictions, the
new location "/export/nim/lpp_source" may not be used
 

10 More Discussions You Might Find Interesting

1. AIX

NIM client mksysb restore

Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies

2. AIX

problem adding NIM client

Hello All, While trying to add NIM client to the NIM environment from NIM client machine, I get the following error: 1800-109 There are currently no additional SMIT screen entries available for this item. This may require installation of additional software before it can be accessed. ... (1 Reply)
Discussion started by: solaix14
1 Replies

3. AIX

Back up a client NIM from nim master

Hello everyone Im trying to backup a nim client from nim master but I got this message COMMAND STATUS Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. 0042-001 nim:... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies

4. AIX

aix-configure nim client

:b:Hi... I need help to configure nim client on nim server.. can i define aix 5.3.4.0 on aix 5.3.7.0 nim server.. while i m configuring nim client on nim server its getting msg that images not same.. i need to confirm that both version should be same or not.. Thanks.. (5 Replies)
Discussion started by: sumathi.k
5 Replies

5. AIX

NIM client boot problem

Hi all, I have created VIO Server which serves 3 lpars. All of them are on VLAN ID 50. From one lpar I installed and set up NIM master server called testAIX1. I have created client and allocated resources to it: testAIX1:/ > lsnim -l test_lpar test_lpar: class = machines ... (4 Replies)
Discussion started by: phobus
4 Replies

6. AIX

filesets nim client

Hello everyone I was looking for the filesets to install a nim client on a linux box. (red hat 5 for power) I have the nim master on aix box and I have different nim client with aix. I download some filesets fron aix cd to linux box, but Im still hang up. Some one know where I can find... (1 Reply)
Discussion started by: lo-lp-kl
1 Replies

7. AIX

NIM : remove nim client info from the client

Hi. I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ? Tks (2 Replies)
Discussion started by: stephnane
2 Replies

8. AIX

Nim client with different subnet to Master

Iam attempting to add a client to NIM however the new client has a different subnet than master 10... & 193... , I've established from redbooks that it should be possible but can't find anything that states how? Does anyone use nim in this way? (5 Replies)
Discussion started by: gefa
5 Replies

9. AIX

Problem in communication nim client with nim master

Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client... (0 Replies)
Discussion started by: omonoiatis9
0 Replies

10. AIX

How to know NIM name from NIM client?

Friend's, I was playing around with NIM in my environment & had a quick question in mind which I didn't/couldn't find answer to, which is -- how to find the name of the NIM server sitting on the NIM client? All leads to the answer would be much appreciated, many thanks! -- Souvik (2 Replies)
Discussion started by: thisissouvik
2 Replies
OCF_HEARTBEAT_EXPORT(7) 					OCF resource agents					   OCF_HEARTBEAT_EXPORT(7)

NAME
ocf_heartbeat_exportfs - Manages NFS exports SYNOPSIS
exportfs [start | stop | monitor | meta-data | validate-all] DESCRIPTION
Exportfs uses the exportfs command to add/remove nfs exports. It does NOT manage the nfs server daemon. It depends on Linux specific NFS implementation details, so is considered not portable to other platforms yet. SUPPORTED PARAMETERS
clientspec The client specification allowing remote machines to mount the directory over NFS. (required, string, no default) options The options to pass to exportfs for the exported directory. (optional, string, no default) directory The directory which you wish to export using NFS. (required, string, no default) fsid The fsid option to pass to exportfs. This can be a unique positive integer, a UUID, or the special string "root" which is functionally identical to numeric fsid of 0. 0 (root) identifies the export as the root of an NFSv4 pseudofilesystem -- avoid this setting unless you understand its special status. This value will override any fsid provided via the options parameter. (unique, required, string, no default) unlock_on_stop Relinquish NFS locks associated with this filesystem when the resource stops. Enabling this parameter is highly recommended unless the path exported by this exportfs resource is also exported by a different resource. (optional, boolean, default 0) wait_for_leasetime_on_stop When stopping (unexporting), wait out the NFSv4 lease time. Only after all leases have expired does the NFS kernel server relinquish all server-side handles on the exported filesystem. If this exportfs resource manages an export that resides on a mount point designed to fail over along with the NFS export itself, then enabling this parameter will ensure such failover is working properly. Note that when this parameter is set, your stop timeout MUST accommodate for the wait period. This parameter is safe to disable if none of your NFS clients are using NFS version 4 or later. (optional, boolean, default 0) rmtab_backup Back up those entries from the NFS rmtab that apply to the exported directory, to the specified backup file. The filename is interpreted as relative to the exported directory. This backup is required if clients are connecting to the export via NFSv3 over TCP. Note that a configured monitor operation is required for this functionality. .sp To disable rmtab backups, set this parameter to the special string "none". (optional, string, default .rmtab) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 40. stop Stops the resource. Suggested minimum timeout: 10. monitor Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 30. EXAMPLE
The following is an example configuration for a exportfs resource using the crm(8) shell: primitive p_exportfs ocf:heartbeat:exportfs params clientspec=string directory=string fsid=string op monitor depth="0" timeout="20" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/exportfs_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_EXPORT(7)
All times are GMT -4. The time now is 07:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy