08-11-2008
nim mksysb - 0042-124 c_ch_nfsexp error
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 979345 (957 MB) Available = 10474116 (10229 MB)
Creating information file (/image.data) for rootvg.
/usr/bin/savevg[33]: 1016,07: syntax error
0042-001 nim : pocessing error detected "master" :
0042-124 c_ch_nfsexp : option NFS sec=sys isn't supported
rc=1
0042-001 m_mkbosi : processing error detected on "client_1" :
10 More Discussions You Might Find Interesting
1. AIX
I have multiple LPARS on p650 with mix of AIX5.2 and AIX5.1 with different rml level
My understanding is creating mksysb nim on NIM server is for new installation of LPARS
Then;
How do I do mksysb backup on existing lpars for recovery purpose or how do I do all mksysb to a NFS mounted Filesystem... (1 Reply)
Discussion started by: melindaj
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I'm trying to use my NIM server to get a mksysb of an lpar on another machine on my network.
I'm trying to define a resource through smitty and i've entered the resource name, Server of resource & location of resource, they are as follows
Resource Name : gmt_fail_mksysb
Server of... (1 Reply)
Discussion started by: KeesH
1 Replies
3. Shell Programming and Scripting
#!/bin/ksh
#
# nim_mksysb
# get mksysb from each client machine specified with -m. If no
# machines specified, get mksysb from ALL machines. -r flag says
# remove oldest existing mksysb for the machines being backed up.
# use -n no_make flag with -r to remove a generation of mksysb,
#... (0 Replies)
Discussion started by: barkath
0 Replies
4. AIX
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
5. AIX
--------------------------------------------------------------------------------
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies
6. AIX
Hi,
I am trying to backup a system ("client") through a slow network using "nim mksysb" on a nim server ("master")
The backup starts, but doesn't success.
Thanks if you can help me to resolve this problem :
Creating information file (/image.data) for rootvg...
Creating list of files to... (2 Replies)
Discussion started by: astjen
2 Replies
7. AIX
Hello,
I need to install "bos.adt.libm 5.3.0.0" on a server (AIX5.3 power 5).
How to install it from a nim mksysb of an another partition ?
Thank you (3 Replies)
Discussion started by: astjen
3 Replies
8. AIX
Hi All,
Please excuse the possibly naive question but I'm trying to clone/install a new AIX 5.3 LPAR on a p570 from a mksysb image file using nim. Has anyone done this before and if so, what would the exact command look like?
Does it even remotely resemble something like
nim -o... (1 Reply)
Discussion started by: combustables
1 Replies
9. AIX
Hi,
I just want to ask whether anyone has experience on restoring mksysb backup in NIM. We have taken the mksysb backup and the SPOT has been configured on NIM also. I just want to know the checkpoints before doing this. Is there any checkpoints we need to do? Do we need to unmirrorvg? This... (12 Replies)
Discussion started by: depam
12 Replies
10. AIX
I am implementing mksysb backups using NIM. I am using nimsh as client communication and mksysb backup are working fine, but this requires remote logon to be enabled for root.
Any thoughts on how can I implement mksysb backups using NIM without enabling remote logon for "root" ? (1 Reply)
Discussion started by: mk8570
1 Replies
LEARN ABOUT REDHAT
stderr
STDIN(3) BSD Library Functions Manual STDIN(3)
NAME
stdin, stdout, stderr -- standard I/O streams
SYNOPSIS
#include <stdio.h>
extern FILE *stdin;
extern FILE *stdout;
extern FILE *stderr;
DESCRIPTION
Under normal circumstances every Unix program has three streams opened for it when it starts up, one for input, one for output, and one for
printing diagnostic or error messages. These are typically attached to the user's terminal (see tty(4)) but might instead refer to files or
other devices, depending on what the parent process chose to set up. (See also the ``Redirection'' section of sh(1) .)
The input stream is referred to as ``standard input''; the output stream is referred to as ``standard output''; and the error stream is
referred to as ``standard error''. These terms are abbreviated to form the symbols used to refer to these files, namely stdin, stdout, and
stderr.
Each of these symbols is a stdio(3) macro of type pointer to FILE, and can be used with functions like fprintf(3) or fread(3).
Since FILEs are a buffering wrapper around Unix file descriptors, the same underlying files may also be accessed using the raw Unix file
interface, that is, the functions like read(2) and lseek(2). The integer file descriptors associated with the streams stdin, stdout, and
stderr are 0, 1, and 2, respectively. The preprocessor symbols STDIN_FILENO, STDOUT_FILENO, and STDERR_FILENO are defined with these values
in <unistd.h>.
Note that mixing use of FILEs and raw file descriptors can produce unexpected results and should generally be avoided. (For the masochistic
among you: POSIX.1, section 8.2.3, describes in detail how this interaction is supposed to work.) A general rule is that file descriptors
are handled in the kernel, while stdio is just a library. This means for example, that after an exec, the child inherits all open file
descriptors, but all old streams have become inaccessible.
Since the symbols stdin, stdout, and stderr are specified to be macros, assigning to them is non-portable. The standard streams can be made
to refer to different files with help of the library function freopen(3), specially introduced to make it possible to reassign stdin, stdout,
and stderr. The standard streams are closed by a call to exit(3) and by normal program termination.
SEE ALSO
sh(1), csh(1), open(2), fopen(3), stdio(3)
CONSIDERATIONS
The stream stderr is unbuffered. The stream stdout is line-buffered when it points to a terminal. Partial lines will not appear until
fflush(3) or exit(3) is called, or a newline is printed. This can produce unexpected results, especially with debugging output. The buffer-
ing mode of the standard streams (or any other stream) can be changed using the setbuf(3) or setvbuf(3) call. Note that in case stdin is
associated with a terminal, there may also be input buffering in the terminal driver, entirely unrelated to stdio buffering. (Indeed, nor-
mally terminal input is line buffered in the kernel.) This kernel input handling can be modified using calls like tcsetattr(3); see also
stty(1), and termios(3).
CONFORMING TO
The stdin, stdout, and stderr macros conform to ANSI X3.159-1989 (``ANSI C89''), and this standard also stipulates that these three streams
shall be open at program startup.
Linux 2.0 March 24, 1998 Linux 2.0