02-18-2010
Since you're using a NIM server, I'd assume you are using an lpp_source and matching spot to do upgrades. If you recently upgraded your client LPAR, you could also try re-creating your mksysb NIM object - not the actual mksysb, just the NIM object. When we upgraded from 5.3 to 6.1, I had to re-create all my mksysb NIM objects because the version of the mksysb is determined, I think, when it is created. I'm sure there is a NIM command to show the version of a mksysb, but I can't find it.
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. AIX
Hello all....
I am trying to backup a client from the NIM master. While doing so, I get this error:
backup: 0511-089
can not open /tmp/6282.mnt0/<hostname>_mksysb_<date>
0042-001 m_mkbosi: processing error encountered on client
0042-001 m_mkbosi: processing error encountered on master... (0 Replies)
Discussion started by: solaix14
0 Replies
5. AIX
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
6. AIX
Friends ,
In our production server , we are using oracle10g in IBM AIX 5.3 unix server. From last 7 days , I got the below error :
------------------------------
LABEL: TS_NIM_ERROR_STUCK_
IDENTIFIER: 864D2CE3
Date/Time: Mon Sep 7 19:34:38 NOVST 2009
Sequence Number:... (1 Reply)
Discussion started by: shipon_97
1 Replies
7. AIX
When I am running following command to take mksysb backup I am getting error as below:
nim -o define -t mksysb -a server=master \
-a location=/nim/mksysb/client1_bkup_mksysb -a source=client1_bkup \
-a mk_image=yes -a mksysb_flags='e' client1_bkup_mksysb
Here my nim client name is :... (1 Reply)
Discussion started by: SiddhV
1 Replies
8. AIX
Hi to all,
i am trying to make mksysb backup of a NIM client machine from NIM master and while i am reading that the backup is done successfully i get an error message below and it doesnt exit the smit screen. also the status of the command appears to be running.
is there anybody who knows why... (3 Replies)
Discussion started by: omonoiatis9
3 Replies
9. AIX
I have added our DR to NIM server and tried to create bosinstall image with smitty nim_bosinst command. But ended up with below error.
warning: 0042-229 m_bos_inst: When installing a system using a mksysb as the
source for the installation, the level of the SPOT used for the
... (3 Replies)
Discussion started by: newaix
3 Replies
10. AIX
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
LEARN ABOUT DEBIAN
bup-margin
bup-margin(1) General Commands Manual bup-margin(1)
NAME
bup-margin - figure out your deduplication safety margin
SYNOPSIS
bup margin [options...]
DESCRIPTION
bup margin iterates through all objects in your bup repository, calculating the largest number of prefix bits shared between any two
entries. This number, n, identifies the longest subset of SHA-1 you could use and still encounter a collision between your object ids.
For example, one system that was tested had a collection of 11 million objects (70 GB), and bup margin returned 45. That means a 46-bit
hash would be sufficient to avoid all collisions among that set of objects; each object in that repository could be uniquely identified by
its first 46 bits.
The number of bits needed seems to increase by about 1 or 2 for every doubling of the number of objects. Since SHA-1 hashes have 160 bits,
that leaves 115 bits of margin. Of course, because SHA-1 hashes are essentially random, it's theoretically possible to use many more bits
with far fewer objects.
If you're paranoid about the possibility of SHA-1 collisions, you can monitor your repository by running bup margin occasionally to see if
you're getting dangerously close to 160 bits.
OPTIONS
--predict
Guess the offset into each index file where a particular object will appear, and report the maximum deviation of the correct answer
from the guess. This is potentially useful for tuning an interpolation search algorithm.
--ignore-midx
don't use .midx files, use only .idx files. This is only really useful when used with --predict.
EXAMPLE
$ bup margin
Reading indexes: 100.00% (1612581/1612581), done.
40
40 matching prefix bits
1.94 bits per doubling
120 bits (61.86 doublings) remaining
4.19338e+18 times larger is possible
Everyone on earth could have 625878182 data sets
like yours, all in one repository, and we would
expect 1 object collision.
$ bup margin --predict
PackIdxList: using 1 index.
Reading indexes: 100.00% (1612581/1612581), done.
915 of 1612581 (0.057%)
SEE ALSO
bup-midx(1), bup-save(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-margin(1)