Sponsored Content
Full Discussion: mksysb
Operating Systems AIX mksysb Post 302216003 by shockneck on Thursday 17th of July 2008 06:00:41 PM
Old 07-17-2008
Quote:
Originally Posted by TinWalrus
i think the best way to do this is to have part of your paging on rootvg (memory*2) which is mirrored (or should be) then have an additional non-mirrored disk for additional paging space[...]
Well... Let's look at an example: my server has 48GB of RAM so my paging space should be as big as 96GB?

Let's have a look at shockneck's top four tips about AIX paging space:
1) If AIX uses paging space you lack RAM or/and you configured vmo wrong. If tuning cannot help anymore get more RAM chips. Best thing is not to use paging space.
2) There is no such thing as an "official" recommendation about how big paging space should be (beside some application vendors such as SAP and/or your app's allocation policy) for many years now. Default settings for AIX have become pretty small since AIX 5L. Paging space shall be as big as necessary but as small as possible. I.e. it depends on how you use the server.
3) If AIX uses paging space it stores data that does not fit into RAM (and is not stored on disk already). Thus losing paging space is equivalent to losing a memory chip. Hence if you don't mirror it the other (SAN) storage should be at least as safe as it would be on mirrored disks.
4) If you use several paging spaces keep them at about the same size. If you want to you can make hd6 slightly bigger as it is used during boot. Furthermore speed of different disks used for paging should not differ to a large extend. Don't use two or more paging spaces on the same disk.
 

10 More Discussions You Might Find Interesting

1. AIX

mksysb...

Hi friends.. My one problem is not resolved yet I have another. I am planning to take an OS backup of my p550 using "mksysb". Now i am confussed. suppose I give the command to take the backup into a tape drive and my backup size exceeds the tape capacity.. what will happen? will it ask for... (2 Replies)
Discussion started by: balaji_prk
2 Replies

2. AIX

Problem with MKSYSB

Am taking a tape backup and the error output shows this. ---------------------------------------------------------------- ====== mksysb errors from /opt/uss/log/run_mksysb.stdout: 0512-038 mksysb: Backup Completed Successfully. ====== mksysb errors from /opt/uss/log/run_mksysb.stderr: ... (1 Reply)
Discussion started by: balaji_prk
1 Replies

3. AIX

mksysb

I dont have either a tape drive or a DVD Writer attached to the AIX box. Can you let me know the possibilities of making an mksysb in a bootable media? This is required as we have a requirement to upgrade the OS. (2 Replies)
Discussion started by: chrisanto_2000
2 Replies

4. AIX

mksysb issue

Hi, guys I have experience in UNIX, but more in hpux, have done an mksysb in an Aix server 5.3, and then restore in other server with same model, everithing fine but no TCP/IP configuration and hostname its like "localhost" after the restore. It's something wrong? I've change the configuration,... (5 Replies)
Discussion started by: uadm26
5 Replies

5. AIX

mksysb backup

hi guys, i just want to take my server's mksysb backup through dvd-rom.but am having the doubt that, while am taking the mksysb backup in image it shows 8GB. So can i confirm that it takes 2 dvds and after writing in 1st cd it will ask for 2nd cd?????? please help me out. (1 Reply)
Discussion started by: rrlog
1 Replies

6. AIX

Mksysb message

Hello, I'm starting a mksysb with the help of a unix script and the crontab. The script is scheduled with crontab and executes "mksysb -i -X /dev/rmt0". When the mksysb is completed the script displays the endtime. But I also get a lot of cat messages (see below). When I look with "ps -ef... (2 Replies)
Discussion started by: Peter_e
2 Replies

7. AIX

Help with mksysb

Hi All, Working on AIX 4.2 system. On this server there is no tape drive or a DVD Writer attached to the AIX box. I was able to do mksysb, but I got warning message saying it will not be bootable. On the new system, I did install 5.3 and now I need to restore this mksysb image from the... (5 Replies)
Discussion started by: samnyc
5 Replies

8. AIX

Need to take MKSYSB backup

Hi, Can any one suggest me how to take the mksysb backup in CD (VCD/DVD). I have tried like #mkcd -d /dev/cd0, but its not working. (3 Replies)
Discussion started by: oprakash
3 Replies

9. AIX

mksysb backup

hi we are having one rootvg in that we created one lv named mksysb_backuplv and normally script will run accordingly to take the backup in the cron,here i just want to know if any rootfilesystem was correpted like /usr or /tmp ,then how could i restore the particular filesystme from the... (1 Reply)
Discussion started by: senmak
1 Replies

10. AIX

savevg - mksysb

Hello, I use commands savevg & mksysb to do backups on an AIX server. Frequently, I have a return code 3. I would know why, but after searches, I did'nt find. If somebody know ... Tell me. Thanks. emetra (2 Replies)
Discussion started by: emetra
2 Replies
MLOCK(2)						     Linux Programmer's Manual							  MLOCK(2)

NAME
mlock - disable paging for some parts of memory SYNOPSIS
#include <sys/mman.h> int mlock(const void *addr, size_t len); DESCRIPTION
mlock disables paging for the memory in the range starting at addr with length len bytes. All pages which contain a part of the specified memory range are guaranteed be resident in RAM when the mlock system call returns successfully and they are guaranteed to stay in RAM until the pages are unlocked by munlock or munlockall, until the pages are unmapped via munmap, or until the process terminates or starts another program with exec. Child processes do not inherit page locks across a fork. Memory locking has two main applications: real-time algorithms and high-security data processing. Real-time applications require determin- istic timing, and, like scheduling, paging is one major cause of unexpected program execution delays. Real-time applications will usually also switch to a real-time scheduler with sched_setscheduler. Cryptographic security software often handles critical bytes like passwords or secret keys as data structures. As a result of paging, these secrets could be transfered onto a persistent swap store medium, where they might be accessible to the enemy long after the security software has erased the secrets in RAM and terminated. Memory locks do not stack, i.e., pages which have been locked several times by calls to mlock or mlockall will be unlocked by a single call to munlock for the corresponding range or by munlockall. Pages which are mapped to several locations or by several processes stay locked into RAM as long as they are locked at least at one location or by at least one process. On POSIX systems on which mlock and munlock are available, _POSIX_MEMLOCK_RANGE is defined in <unistd.h> and the value PAGESIZE from <lim- its.h> indicates the number of bytes per page. NOTES
With the Linux system call, addr is automatically rounded down to the nearest page boundary. However, POSIX 1003.1-2001 allows an imple- mentation to require that addr is page aligned, so portable applications should ensure this. RETURN VALUE
On success, mlock returns zero. On error, -1 is returned, errno is set appropriately, and no changes are made to any locks in the address space of the process. ERRORS
ENOMEM Some of the specified address range does not correspond to mapped pages in the address space of the process or the process tried to exceed the maximum number of allowed locked pages. EPERM The calling process does not have appropriate privileges. Only root processes are allowed to lock pages. EINVAL len was not a positive number. CONFORMING TO
POSIX.1b, SVr4. SVr4 documents an additional EAGAIN error code. SEE ALSO
mlockall(2), munlock(2), munlockall(2), munmap(2), setrlimit(2) Linux 1.3.43 1995-11-26 MLOCK(2)
All times are GMT -4. The time now is 06:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy