10-09-2007
NIM Server Issue
Quote:
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 8623776 (8422 MB) Available = 10535156 (10288 MB)
Data compression will be used by the system backup utilities which
create the system backup image. This may reduce the required space
by up to 50 percent.
Creating information file (/image.data) for rootvg...
Creating list of files to back up
Backing up 90237 files..............................
4274 of 90237 files backed up (4%)..............................
16449 of 90237 files backed up (18%)..............................
31029 of 90237 files backed up (34%)..............................
71495 of 90237 files backed up (79%)..........................
0512-003 savevg may not have been able to archive some files.
The messages displayed on the Standard Error contained additional
information.
0042-001 nim: processing error encountered on "master":
cannot access ./var/tmp/Ex20678: No such file or directory
Hi,
I'm getting the above error while trying to take a MKSYSB image via NIM. I've only just started getting this and don't know why it is failing.
Any one got any suggestions?
Thanks
Kees
10 More Discussions You Might Find Interesting
1. AIX
Hi, I'a a new member here.
My company just bought p570 with 8 LPAR (previously we have p650 with 4 LPAR).
Did anyone have procedure how to setup NIM server (NIM LPAR) and how to install other new LPAR to use the NIM server (as client).
Appreciate your help and thank you very much.
Rgds,
David (0 Replies)
Discussion started by: dshg
0 Replies
2. AIX
Is anybody using a NIM server for DR recovery purposes? If so, how are you handling Volume Groups outside of root? (0 Replies)
Discussion started by: kd30185
0 Replies
3. AIX
Hi Guys..
Got a NIM issue.. Am trying to pull a image of a client from NIM server.
am getting the following error... in standard error output..
0042-001 nim: processing error encountered on "master":
Usage: rm File...
Am using the same script to pull image and it works fine..... (1 Reply)
Discussion started by: balaji_prk
1 Replies
4. AIX
I try to migrate a NIM server from one server to another.
I try to do a mksysb on NIM server
restore the NIM server's mksysb to a client through NIM installation
shutdown NIM server
start newly installed client as NIM server
Does anyone do this before? who can give me some suggestion? (1 Reply)
Discussion started by: yanzhang
1 Replies
5. AIX
Hello All,
I believe my NIM master is fine. lsnim and cat /etc/niminfo gives me the right output. While doing "lsnim" on a client machine, I get ksh:lsnim:"not found".
Please someone be nice enough to explain what are the steps to verify the master and client connectivity to do all the NIM... (3 Replies)
Discussion started by: solaix14
3 Replies
6. AIX
Can any one help.....
How will do migration through NIM server? (4 Replies)
Discussion started by: AIXlearner
4 Replies
7. AIX
I have never used NIM. Please help with the steps for configuring NIM server and client.
thanks
Pchangba (3 Replies)
Discussion started by: pchangba
3 Replies
8. AIX
hello folks,
Can someone help me troubleshoot the NIM Server
NIM MASTER: >>
# hostname
oldbcoedv
# cat /etc/hostname
192.52.100.29 bcoeqa bcoeqa.bin.com.sa
192.52.100.66 oldbcoedv
# cat /etc/bootptab
.....
# T180 -- (xstation only) -- enable virtual screen
#NO CLIENTS... (6 Replies)
Discussion started by: filosophizer
6 Replies
9. AIX
Hi.
I would like to try installation via NIM server. I have set up :
lsnim
master machines master
boot resources boot
nim_script resources nim_script
NET_EN0 networks ent
mksysb_AIX_6141 resources ... (4 Replies)
Discussion started by: phobus
4 Replies
10. AIX
I have configured the NIM Master using AIX 5.3.7, I am getting below message bootp:bootp request fail:0 while booting nim client.
Though both system are able to ping each other.
Regards
Manoj (5 Replies)
Discussion started by: manoj.solaris
5 Replies
LEARN ABOUT HPUX
backup_dbverify
BACKUP_DBVERIFY(8) AFS Command Reference BACKUP_DBVERIFY(8)
NAME
backup_dbverify - Checks the integrity of the Backup Database
SYNOPSIS
backup dbverify [-detail] [-localauth]
[-cell <cell name>]
[-help]
backup db [-d] [-l] [-c <cell name>] [-h]
DESCRIPTION
The backup dbverify command checks the integrity of the Backup Database. The command's output indicates whether the Backup Database is
damaged (data is corrupted) or not. If the Backup Database is undamaged, it is safe to continue using it. If it is corrupted, discontinue
any backup operations until it is repaired.
CAUTIONS
While this command runs, no other backup operation can access the Backup Database; the other commands do not run until this command
completes. Avoid issuing this command when other backup operations are likely to run. The backup savedb command repairs some types of
corruption.
OPTIONS
-detail
Reports the number of orphaned blocks found, any inconsistencies, and the name of the server machine running the Backup Server that is
checking its copy of the database.
-localauth
Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to
the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more
details, see backup(8).
-cell <cell name>
Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8).
-help
Prints the online help for this command. All other valid options are ignored.
OUTPUT
The command displays one of the following two messages:
Database OK
The database is undamaged and can be used.
Database not OK
The database is damaged. You can use the backup savedb command to repair many kinds of corruption as it creates a backup copy. For
more detailed instructions, see the OpenAFS Administration Guide chapter about performing backup operations.
The -detail flag provides additional information:
o The number of orphan blocks found. These are ranges of memory that the Backup Server preallocated in the database but cannot use.
Orphan blocks do not interfere with database access, but do waste disk space. To free the unusable space, dump the database to tape by
using the backup savedb command, and then restore it by using the backup restoredb command.
o Any inconsistencies in the database, such as invalid hostnames for Tape Coordinator machines.
o The name of the database server machine on which the Backup Database was checked, designated as the "Database checker". For a detailed
trace of the verification operation, see the /var/log/openafs/BackupLog file on the indicated machine. You can use the bos getlog
command to display it.
EXAMPLES
The following command confirms that the Backup Database is undamaged:
% backup dbverify
Database OK
The following command confirms that the Backup Database is undamaged and that it has no orphan blocks or invalid Tape Coordinator entries.
The Backup Server running on the machine "db1.abc.com" checked its copy of the Database.
% backup dbverify -detail
Database OK
Orphan blocks 0
Database checker was db1.abc.com
PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged
onto a server machine as the local superuser "root" if the -localauth flag is included.
SEE ALSO
BackupLog(5), backup(8), backup_restoredb(8), backup_savedb(8), bos_getlog(8)
COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2012-03-26 BACKUP_DBVERIFY(8)