Restoring files from mksysb backup

Restoring the /image.data from the mksysb tape backup:.

 /image.data is stored on the 2nd block of the tape.

1) Change the block size of the tape drive to 512.
# chdev -l rmt0 -a block_size=512

2) Check to make sure the block size of the tape drive has been changed:
# tctl -f /dev/rmt0 status

rmt0 Available 10-60-00-1,0 4.0 GB 4mm Tape Drive
attribute value description user_settable
block_size 512 BLOCK size (0=variable length) True
compress yes Use data COMPRESSION True
mode yes Use DEVICE BUFFERS during writes True
ret_error no RETURN error on tape change or reset True

3) Change the location where you would like to restore the /image.data
# restore -s2 -xqvf /dev/rmt0.1 ./image.data.

Restoring the /image.data from the mksysb file backup:
Change the location to restore the backup.
# restore -xqvf <location of mksysb backup> ./image.data

Memory Checking in all the UNIX machines

Solaris

1. dmesg grep mem
2. prtdiag grep Memory
3. prtconf -v grep Memory

AIX

1. bootinfo -r
2. lsattr -E1 sys0 -a realmem
3. getconf REAL_MEMORY

HPUX

1. dmesg grep Physical
2. /opt/ignite/bin/print_manifest grep Memory
3. machinfo grep Memory

Linux

1. dmesg grep Memory
2. grep -i memtotal /proc/meminfo
3. free

OpenVMS

1. show mem /page

Update:

FreeBSD

1. dmesg grep memory
2. grep memory /var/run/dmesg.boot
3. sysctl -a grep mem

How to delete file with special characters

If you have files with the name of any special characters they are handled:

Eg: Filename is -s.

# cat -- -s : View the file with the name -s
# ls -l -- -s : To list the file.
# rm -- -s : Remove the file.

Listing and Restoring a mksysb content

# listvgbackup -f /dev/rmt0 : List the mksysb files in the tape backup.

# listvgbackup -f /filename : List the mksysb files in the file backup.

# restorevgfiles -r -f '/dev/rmt0' /dir : To restore the /dir from the tape /dev/rmt0

Migrating Users from One AIX System to Another AIX System

Files that can be copied over

/etc/group
/etc/passwd
/etc/security/group
/etc/security/limits
/etc/security/passwd
/etc/security/.ids
/etc/security/environ
/etc/security/.profile

NOTE: Edit the passwd file so the root entry is as follows:

root:!:0:0::/:/usr/bin/ksh

When you copy the /etc/passwd and /etc/group files, make sure they contain at least a minimum set of essential user and group definitions.

Listed specifically as users are the following:

• root
• daemon
• bin
• sys
• adm
• uucp
• guest
• nobody
• lpd

Listed specifically as groups are the following:

• system
• staff
• bin
• sys
• adm
• uucp
• mail
• security
• cron
• printq
• audit
• ecs
• nobody
• usr

If the bos.compat.links fileset is installed, you can copy the /etc/security/mkuser.defaults file over. If it is not installed, the file belongs in the /usr/lib/security directory.

If you copy over mkuser.defaults, changes must be made to the stanzas.
Replace group with pgrp, and program with

shell. A proper stanza should look like the following:

user:
            pgrp = staff
            groups = staff
            shell = /usr/bin/ksh
            home = /home/$USER

The following files may also be copied over, as long as the AIX version in the
new machine is the same:

/etc/security/login.cfg
   /etc/security/user

NOTE: If you decide to copy these two files, open the
/etc/security/user
file and make sure that variables such as tty, registry, auth1 and so forth are
set properly with the new machine. Otherwise, do not copy these two files, and
just add all the user stanzas to the new created files in the new machine.
Once the files are moved over, execute the following:

usrck -t ALL
    pwdck -t ALL
    grpck -t ALL

This will clear up any discrepancies (such as uucp not having an entry in
/etc/security/passwd). Ideally this should be run on the source system
before
copying over the files as well as after porting these files to the new system.
NOTE: It is possible to find user ID conflicts when migrating users from
older versions of AIX to newer versions. AIX has added new user IDs in
different release cycles. These are reserved IDs and should not be deleted.
If your old user IDs conflict with the newer AIX system user IDs, it is advised
that you assign new user IDs to these older IDs.