Unit 11

Backup and restore

Copyright IBM Corporation 2009

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

5.2

Unit objectives
IBM Power Systems

After completing this unit, you should be able to:

Explain how to back up the Operating System
Create and restore a mksysb image
Explain and understand the role of both the image.data and
bosinst.data files
Back up and restore a custom volume group
Use standard UNIX and AIX backup, restore, and compression
utilities

Backup introduction
IBM Power Systems

Why back up?

Data is very important, it is expensive to re-create.

Hardware failure
Accidental deletion
Damage due to software installation or hardware repair
Create a system image for installation cloning
Long term archive
Disaster recovery
Generally handled by enterprise

Types of backup:

backup mgnt solutions, for

example TSM

Volume group
mksysb utility which records an image backup of the operating system
savevg utility which performs a full backup of a user-created VG

Full
Backs up all specified data

Incremental
Records changes since previous backups

System image backup

IBM Power Systems

Backs up rootvg only using the mksysb command

Unmounted file systems are not backed up
If device selected is tape, bootable tape is created in backup
format
Can be completed over a network to a NIM server
Provides facilities for a non-interactive installation
Saves system-created paging space definitions
Saves LV policies and file system attributes
There should be minimal user and application activity

Creating a mksysb image

IBM Power Systems

smit mksysb

/usr/bin/mksysb -i /backups/my_mksysb
Back
Back Up
Up the
the System
System

** Backup
Backup DEVICE
DEVICE or
or FILE
FILE
Create
MAP
files?
Create MAP files?
EXCLUDE
EXCLUDE files?
files?
List
List files
files as
as they
they are
are backed
backed up?
up?
Verify
Verify readability
readability if
if tape
tape device?
device?
Generate
Generate new
new /image.data
/image.data file?
file?
EXPAND
EXPAND /tmp
/tmp if
if needed?
needed?
Disable
Disable software
software packing
packing of
of backup?
backup?
Backup
Backup extended
extended attributes?
attributes?
(Leave
blank
to
use
a
system
(Leave blank to use a system default)
default)
Location
Location of
of existing
existing mksysb
mksysb image
image
File
File system
system to
to use
use for
for temporary
temporary work
work space
space
(If
blank,
/tmp
will
be
used.)
(If blank, /tmp will be used.)
Back
Back up
up encrypted
encrypted files?
files?
Back
up
DMAPI
Back up DMAPI filesystem
filesystem files?
files?

[/backups/my_mksysb]
[/backups/my_mksysb]
no
no
no
no
no
no
Backup to tape, for
no
no
example /dev/rmt0 is
yes
yes
also popular
no
no
no
no
yes
yes
[]
[]
[]
[]
yes
yes
No
No

+/
+/
++
++
++
++
++
++
++
++
//
//
++
++

SMIT also provides facilities to do a system backup to CD and

DVD, see smit sysbackup

image.data file
IBM Power Systems

The image.data file contains information describing the image

installed during the BOS installation process. This includes:
Sizes, names, maps, and mount points of logical volumes and file
systems in the root volume group

It is a large file arranged in stanza format

Is not recommended that the user modify the file, apart from the
shrink field

New image.data can be created during a mksysb operation or

by calling the mkszfile command.
image_data:
image_data:
IMAGE_TYPE= bff
IMAGE_TYPE= bff
DATE_TIME= Mon 20 Oct 17:54:07 2008
DATE_TIME= Mon 20 Oct 17:54:07 2008
UNAME_INFO= AIX neo 1 6 00CBE2FE4C00
UNAME_INFO= AIX neo 1 6 00CBE2FE4C00
PRODUCT_TAPE= no
PRODUCT_TAPE= no
USERVG_LIST=
USERVG_LIST=
PLATFORM= chrp
PLATFORM= chrp
OSLEVEL= 6.1.1.0
OSLEVEL= 6.1.1.0
OSLEVEL_R= 6100-01
OSLEVEL_R= 6100-01
CPU_ID= 00CBE2FE4C00
CPU_ID= 00CBE2FE4C00
LPAR_ID= 4
LPAR_ID= 4
logical_volume_policy:
logical_volume_policy:
SHRINK= no
SHRINK= no
EXACT_FIT= no
EXACT_FIT= no

The SHINK field can be set

to yes.

bosinst.data file
IBM Power Systems

Defines defaults for variables controlling an installation

Can be used to created non-prompted installations
Key options below, for a full description see:
/usr/lpp/bosinst/bosinst.template.README
control_flow:
control_flow:
CONSOLE = Default
CONSOLE = Default
INSTALL_METHOD = overwrite
INSTALL_METHOD = overwrite
PROMPT = no
PROMPT = no
EXISTING_SYSTEM_OVERWRITE = yes
EXISTING_SYSTEM_OVERWRITE = yes
INSTALL_X_IF_ADAPTER = no
INSTALL_X_IF_ADAPTER = no
RUN_STARTUP = yes
RUN_STARTUP = yes
RM_INST_ROOTS = no
RM_INST_ROOTS = no
ERROR_EXIT =
ERROR_EXIT =
CUSTOMIZATION_FILE = SCREEN
CUSTOMIZATION_FILE = SCREEN
TCB = no
TCB = no
INSTALL_TYPE =
INSTALL_TYPE =
BUNDLES =
BUNDLES =
SWITCH_TO_PRODUCT_TAPE =
SWITCH_TO_PRODUCT_TAPE =
RECOVER_DEVICES = no
RECOVER_DEVICES = no
BOSINST_DEBUG = no
BOSINST_DEBUG = no
ACCEPT_LICENSES =
ACCEPT_LICENSES =
DESKTOP = CDE
DESKTOP = CDE
INSTALL_DEVICES_AND_UPDATES = yes
INSTALL_DEVICES_AND_UPDATES = yes
IMPORT_USER_VGS =
IMPORT_USER_VGS =
ENABLE_64BIT_KERNEL = Default
ENABLE_64BIT_KERNEL = Default
CREATE_JFS2_FS = yes
CREATE_JFS2_FS = yes
ALL_DEVICES_KERNELS = no
ALL_DEVICES_KERNELS = no
ALT_DISK_INSTALL_BUNDLE = no
ALT_DISK_INSTALL_BUNDLE = no

GRAPHICS_BUNDLE = yes
MOZILLA_BUNDLE = no
KERBEROS_5_BUNDLE = no
SERVER_BUNDLE = yes
ALT_DISK_INSTALL_BUNDLE = no
locale:
BOSINST_LANG = en_US
CULTURAL_CONVENTION = en_GB
MESSAGES = en_US
KEYBOARD = en_GB
target_disk_data:
PVID =
PHYSICAL_LOCATION =
CONNECTION =
LOCATION =
SIZE_MB =
HDISKNAME = hdisk0

mksysb tape image format

IBM Power Systems

Blocksize =
512

Blocksize =
512

Blocksize =
512

Tape Drive
Blocksize

BOS Boot

mkinsttape

dummy

rootvg

image

image

1st Section

2nd Section

1
Kernel
Device Drivers

backup image

.toc
3rd Section

2
./image.data
./bosinst.data
./tapeblksz

4th Section

3
Dummy TOC

To list files in the backup image on a mksysb

tctl -f /dev/rmt0 rewind
tctl -f /dev/rmt0.1 fsf 3
restore -Tvf /dev/rmt0

OR

restore -Tv s4 -f /dev/rmt0

Backup
by name

Restoring a mksysb, from tape device (1 of 2)

IBM Power Systems

From the SMS Menu, boot the system from the tape device.
Restore mksysb image from the device, that is, tape
(/dev/rmt0), as follows:
Welcome
Welcome to
to Base
Base Operating
Operating System
System
Installation
and
Installation and Maintenance
Maintenance
11
22
>>
>> 33
44

>>
>>

11
22
33
44
66

Tape
Tape Drive
Drive
>>
>> 11

Start
Start Install
Install Now
Now With
With Default
Default Settings
Settings
Change/Show
Change/Show Installation
Installation Settings
Settings and
and Install
Install
Start
Maintenance
Mode
for
System
Recovery
Start Maintenance Mode for System Recovery
Configure
Configure Network
Network Disks
Disks (iSCSI)
(iSCSI)
Access
Access AA Root
Root Volume
Volume Group
Group
Copy
Copy aa System
System Dump
Dump to
to Removable
Removable Media
Media
Access
Advanced
Maintenance
Access Advanced Maintenance Functions
Functions
Erase
Erase Disks
Disks
Install
Install from
from aa System
System Backup
Backup

tape/scsi/4mm/2GB
tape/scsi/4mm/2GB

Path
Path Name
Name
/dev/rmt0
/dev/rmt0

Restoring a mksysb, from tape device (2 of 2)

IBM Power Systems

Welcome
Welcome to
to Base
Base Operating
Operating System
System
Installation
Installation and
and Maintenance
Maintenance
Type
Type the
the number
number of
of your
your choice
choice and
and press
press Enter.
Enter. Choice
Choice is
is indicated
indicated by
by >>.
>>.
11
Start
Install
Now
With
Default
Settings
Start Install Now With Default Settings
>>
22
Change/Show
>>
Change/Show Installation
Installation Settings
Settings and
and Install
Install
33
Start
Maintenance
Mode
for
System
Recovery
Start Maintenance Mode for System Recovery
44
Configure
Configure Network
Network Disks
Disks (iSCSI)
(iSCSI)
55
Select
Select Storage
Storage Adapters
Adapters
System
System Backup
Backup Installation
Installation and
and Settings
Settings
Type
Type the
the number
number of
of your
your choice
choice and
and press
press Enter.
Enter.
11

Disk(s)
hdisk0
Disk(s) where
where you
you want
want to
to install
install
hdisk0
Use
No
Use Maps
Maps
No
Shrink
No
Shrink Filesystems
Filesystems
No
Import
No
Import User
User Volume
Volume Groups
Groups
No
Recover
No
Recover devices
devices
No
Install
Install with
with the
the settings
settings listed
listed above
above

22
33
44
00

Installing
Installing Base
Base Operating
Operating System
System
Please
Please wait...
wait...
Approximate
Elapsed
Approximate
Elapsed time
time
%% tasks
tasks complete
complete (in
(in minutes)
minutes)
33

00

Making
Making logical
logical volumes
volumes

Restoring a mksysb, from a NIM server (1 of 2)

IBM Power Systems

Restore a mksysb image from a NIM Server, using the SMS

menu.

Note: NIM server configuration is covered in the AU08G NIM course.

PowerPC
PowerPC Firmware
Firmware
Version
Version SF240_338
SF240_338
SMS
1.6
SMS 1.6 (c)
(c) Copyright
Copyright IBM
IBM Corp.
Corp. 2000,2005
2000,2005 All
All rights
rights reserved.
reserved.
------------------------------------------------------------------------------------------------------------------------------------------------------------Main
Main Menu
Menu
1.
1. Select
Select Language
Language
2.
2. Setup
Setup Remote
Remote IPL
IPL (Initial
(Initial Program
Program Load)
Load) #then
#then select
select the
the adapter
adapter && IP
IP Parameters
Parameters
3.
Change
SCSI
Settings
3.
Change SCSI Settings
4.
4. Select
Select Console
Console
5.
Select
5.
Select Boot
Boot Options
Options

IP
IP Parameters
Parameters
Interpartition
Interpartition Logical
Logical LAN:
LAN: U9113.550.65F2E7F-V9-C3-T1
U9113.550.65F2E7F-V9-C3-T1
1.
[10.47.1.21]
1. Client
Client IP
IP Address
Address
[10.47.1.21]
2.
Server
IP
Address
[10.47.1.33]
2.
Server IP Address
[10.47.1.33]
3.
[000.000.000.000]
3. Gateway
Gateway IP
IP Address
Address
[000.000.000.000]
4.
[255.255.0.0]
4. Subnet
Subnet Mask
Mask
[255.255.0.0]

Enter client and NIM

server IP details.

Restoring a mksysb, from NIM sever (2 of 2)

IBM Power Systems

Return to main menu, by selecting option 5 Boot Options. Then, select:

1. Select Install/Boot Device
6. Network -- followed by the network adapter to the boot from
2. Normal Mode Boot
1. Yes -- to exit System Management Services
BOOTP:
BOOTP: chosen-network-type
chosen-network-type == ethernet,auto,none,auto
ethernet,auto,none,auto
BOOTP:
10.47.1.33
BOOTP: server
server IP
IP ==
10.47.1.33
BOOTP:
BOOTP: requested
requested filename
filename ==
BOOTP:
10.47.1.21
BOOTP: client
client IP
IP ==
10.47.1.21
BOOTP:
client
HW
addr
=
BOOTP: client
HW addr = ea
ea 48
48 f0
f0 00 90
90 33
BOOTP:
0.0.0.0
BOOTP: gateway
gateway IP
IP ==
0.0.0.0
BOOTP:
/vdevice/l-lan@30000003
BOOTP: device
device
/vdevice/l-lan@30000003
BOOTP:
loc-code
BOOTP: loc-code U9113.550.65F2E7F-V9-C3-T1
U9113.550.65F2E7F-V9-C3-T1

BOOTP R = 1 BOOTP S = 2
FILE: /tftpboot/alex.lpar.co.uk
FINAL Packet Count = 27900
FINAL File Size = 14284288 bytes.
load-base=0x4000
real-base=0x2000000

Client issues a bootp request

to NIM master and downloads
the boot image via tftp

Installing
Installing Base
Base Operating
Operating System
System
Please wait...
Please wait...
Approximate
Elapsed time
Approximate
Elapsed time
% tasks complete
(in minutes)
% tasks complete
(in minutes)
3
3

0
0

Making logical volumes

Making logical volumes

Creating a backup of a data volume group

IBM Power Systems

smit savevg

/usr/bin/savevg f /tmp/datavg_bk_svg -i datavg

Back
Back Up
Up aa Volume
Volume Group
Group to
to Tape/File
Tape/File

** Backup
Backup DEVICE
DEVICE or
or FILE
FILE
** VOLUME
GROUP
to
VOLUME GROUP to back
back up
up
List
List files
files as
as they
they are
are backed
backed up?
up?
Generate
new
vg.data
file?
Generate new vg.data file?
Create
Create MAP
MAP files?
files?
EXCLUDE
EXCLUDE files?
files?
EXPAND
EXPAND /tmp
/tmp if
if needed?
needed?
Disable
software
Disable software packing
packing of
of backup?
backup?
Backup
Backup extended
extended attributes?
attributes?
Number
of
BLOCKS
to
write
in
Number of BLOCKS to write in aa single
single output
output
(Leave
blank
to
use
a
system
(Leave blank to use a system default)
default)
Verify
Verify readability
readability if
if tape
tape device?
device?
Back
up
Volume
Group
information
Back up Volume Group information files
files only?
only?
Back
Back up
up encrypted
encrypted files?
files?
Back
Back up
up DMAPI
DMAPI filesystem
filesystem files?
files?

[/tmp/datavg_bk_svg]
[/tmp/datavg_bk_svg]
[datavg]
[datavg]
no
no
yes
yes
no
no
no
no
no
no
no
no
yes
yes
[]
[]
no
no
no
no
yes
yes
no
no

+/
+/
++
++
++
++
++
++
++
++
##
++
++
++
++

SMIT also provides facilities to do a VG backup to CD and

DVD (smit vgbackup).

Restoring a backup of a data volume group

IBM Power Systems

smit restvg

/usr/bin/restvg -q f /tmp/datavg_bk_svg
Remake
Remake aa Volume
Volume Group
Group

** Restore
[/tmp/datavg_bk_svg]
Restore DEVICE
DEVICE or
or FILE
FILE
[/tmp/datavg_bk_svg]
SHRINK
no
SHRINK the
the filesystems?
filesystems?
no
Recreate
logical
volumes
and
filesystems
only?
no
Recreate logical volumes and filesystems only?
no
PHYSICAL
[]
PHYSICAL VOLUME
VOLUME names
names
[]
(Leave
(Leave blank
blank to
to use
use the
the PHYSICAL
PHYSICAL VOLUMES
VOLUMES listed
listed
in
in the
the vgname.data
vgname.data file
file in
in the
the backup
backup image)
image)
Use
yes
Use existing
existing MAP
MAP files?
files?
yes
Physical
[]
Physical partition
partition SIZE
SIZE in
in megabytes
megabytes
[]
(Leave
(Leave blank
blank to
to have
have the
the SIZE
SIZE determined
determined
based
based on
on disk
disk size)
size)
Number
of
BLOCKS
to
read
in
a
single
[]
Number of BLOCKS to read in a single input
input
[]
(Leave
blank
to
use
a
system
default)
(Leave blank to use a system default)
Alternate
[]
Alternate vg.data
vg.data file
file
[]
(Leave
blank
to
use
vg.data
stored
in
(Leave blank to use vg.data stored in
backup
backup image)
image)

Prior to restoring the VG

Unmount all file systems which are part of that VG.
Varyoff and export the volume group.

+/
+/
++
++
++
++
+#
+#
##
//

Traditional UNIX and AIX backup commands

IBM Power Systems

AIX
Backup and restore

Other popular backup, restore commands across UNIX

platforms:

tar
cpio
pax
dd

Compression Utilities
Compress, restore using uncompress or zcat
gzip, restore using gunzip

Backup by filename and restore

IBM Power Systems

File names are read from standard input

## cat
cat listfile
listfile
/home/aix/file1
/home/aix/file1
/home/aix/file2
/home/aix/file2
/home/aix/file3
/home/aix/file3
## backup
backup -iqvf
-iqvf /dev/rmt0
/dev/rmt0 << listfile
listfile

Absolute Paths

## find
find /home/aix
/home/aix || backup
backup -iqvf
-iqvf /dev/rmt0
/dev/rmt0

Relative Paths

## cd
cd /home/aix
/home/aix
## find
find .. || backup
backup -iqvf
-iqvf /backup/aix.backup
/backup/aix.backup
List files

## restore
restore -Tvf
-Tvf /backup/aix.backup
/backup/aix.backup
## restore
restore -xvf
-xvf /backup/aix.backup
/backup/aix.backup
## restore
restore -xvf
-xvf /tmp/aix.backup
/tmp/aix.backup ./file1
./file1

Extract (restore)
files

Extract individual
file

Backup and restore by inode

IBM Power Systems

Only supported if filesystems are unmounted!

Full backup

## backup
backup -u
-u -0
-0 -f
-f /tmp/databkup_21Oct_level0
/tmp/databkup_21Oct_level0 /data
/data
## backup
backup -u
-u -1
-1 -f
-f /tmp/databkup_21Oct_level1
/tmp/databkup_21Oct_level1 /data
/data
## cat
cat /etc/dumpdates
/etc/dumpdates
/dev/rfslv00
/dev/rfslv00 11 Tue
Tue Oct
Oct 21
21 15:45:21
15:45:21 2008
2008
/dev/rfslv00
0
Tue
Oct
21
15:40:54
2008
/dev/rfslv00 0 Tue Oct 21 15:40:54 2008

Incremental backup

Backup history

## restore
restore -rqvf
-rqvf /tmp/databkup_21Nov_level0
/tmp/databkup_21Nov_level0
## restore
restore -rqvf
-rqvf /tmp/databkup_21Nov_level1
/tmp/databkup_21Nov_level1

Must restore first to the last level 0 then

followed by each incremental

tar command
IBM Power Systems

tar is derived from tape archive

Create a tar backup (-c)
## tar
tar cvf
cvf /dev/rmt0
/dev/rmt0 /home
/home
## tar
-cvf
/backup/home.tar
tar -cvf /backup/home.tar /home
/home

List files in a tar backup (-t)

## tar
tar tvf
tvf /dev/rmt0
/dev/rmt0

Extract files from a tar backup (-x)

## tar
tar xvf
xvf /dev/rmt0
/dev/rmt0

Copying directories and files using tar

## cd
cd /data
/data
## tar
tar cf
cf || (cd
(cd /data_backup
/data_backup &&
&& tar
tar xBpf
xBpf -)
-)

cpio command
IBM Power Systems

cpio is derived from copy in and out

Create a cpio backup (-o)
# find /home | cpio ov > /backup/home.bk
# find /home | cpio ov > /backup/home.bk

List files in a cpio backup (-t)

## cpio
cpio -itv
-itv << /backup/home.bk
/backup/home.bk

Extract files from a cpio backup (-i)

## cpio
cpio idv
idv << /backup/home.bk
/backup/home.bk

Copy the contents of the current location to /mydir

## find
find .. -depth
-depth || cpio
cpio -pd
-pd /mydir
/mydir

pax command
IBM Power Systems

tar and cpio syntax differ slightly between UNIX platforms.

IEEE addressed this problem with pax, meaning peace in Latin.
Create a pax backup of /home (-w)
# pax -wf /backup/home_pax.ar /home
# pax -wf /backup/home_pax.ar /home

List files in a pax backup (-v)

# pax -v f /backup/home_pax.ar
# pax -v f /backup/home_pax.ar

Extract files in a pax backup (-r)

## pax
pax -rvf
-rvf /backup/home_pax.ar
/backup/home_pax.ar

dd command
IBM Power Systems

The primary purpose of dd is the low-level copying and

conversion of raw data.
Copy tape to tape. Tape1 block size=1KB. Tape2 block size=2KB
# dd if=/dev/rmt0 ibs=1024 obs=2048 of=/dev/rmt1
# dd if=/dev/rmt0 ibs=1024 obs=2048 of=/dev/rmt1

Perform a raw data backup of /home to tape, then restore

## tar
tar -cvf
-cvf -- /home
/home || dd
dd obs=1024k
obs=1024k of=/dev/rmt0
of=/dev/rmt0
## tar
-cvf
/home
|
rsh
<system>
dd
tar -cvf - /home | rsh <system> dd obs=1024k
obs=1024k of=/dev/rmt0
of=/dev/rmt0
## dd
dd if=/dev/rmt0
if=/dev/rmt0 ibs=1024k
ibs=1024k || tar
tar xvf
xvf --

Writing to a tape
drive on a remote
machine

Convert /etc/passwd from ascii to ebcdic

## dd
dd if=/etc/passwd
if=/etc/passwd of=/etc/passwd.ebcdic
of=/etc/passwd.ebcdic conv=ebcdic
conv=ebcdic

Compression commands (1 of 2)
IBM Power Systems

Archives created with backup utilities are usually compressed.

Reduce the size of the backup.
This can be done using a number of utilities, such as compress.

Examples (using compress, uncompress, and zcat):

## compress
compress -v
-v /tmp/data.tar
/tmp/data.tar
/tmp/data.tar:
/tmp/data.tar: Compression:
Compression: 95.50%
95.50% This
This file
file is
is replaced
replaced
with
/tmp/data.tar.Z.
with /tmp/data.tar.Z.
## uncompress
uncompress /tmp/data.tar.Z
/tmp/data.tar.Z
/tmp/data.tar.Z:
/tmp/data.tar.Z: This
This file
file is
is replaced
replaced with
with /tmp/data.tar.
/tmp/data.tar.
## zcat
zcat /tmp/data.tar.Z
/tmp/data.tar.Z || tar
tar -xvf
-xvf --

zcat, expands a
compressed file to
standard out.

Compression commands (2 of 2)
IBM Power Systems

Examples (gzip and gunzip)

## gzip
gzip -v
-v /tmp/data.tar
/tmp/data.tar
/tmp/data.tar:
97.7%
/tmp/data.tar:
97.7% --- replaced
replaced with
with
/tmp/data.tar.gz
/tmp/data.tar.gz
## gunzip
gunzip -v
-v /tmp/data.tar.gz
/tmp/data.tar.gz
/tmp/data.tar.gz:
97.7%
/tmp/data.tar.gz:
97.7% --- replaced
replaced with
with
/tmp/data.tar
/tmp/data.tar
## tar
tar -cvf
-cvf -- /data
/data || gzip
gzip -c
-c >> data_tar.gz
data_tar.gz
## gunzip
gunzip -c
-c data_tar.gz
data_tar.gz || tar
tar xvf
xvf -Decompresses
and extracts the
compressed
tarball (.tar.gz).

Creates a
compressed
tarball (.tar.gz)
of the /data
directory.

Good practices
IBM Power Systems

Take regular backups.

Verify your backups.
Check the tape device(s).
Label tapes.

Keep old backups.

Keep a copy of the backups securely offsite.
Test recovery procedures before you have to use them!
Consider deploying an enterprise storage management
solution like Tivoli Storage Manager (TSM).

Checkpoint
IBM Power Systems

1.

What is the difference between the following two commands?

2.

On a mksysb tape, if you entered tctl rewind and then tctl

-f/dev/rmt0.1 fsf 3, which element on the tape could you look at?
_________________________________________________________
_________________________________________________________

3.

Which command could you use to restore these files?

_________________________________________________________

4.

True or False: smit mksysb backs up all file systems, provided they
are mounted.
________________________________________________
_________________________________________________________

find /home/fred | backup -ivf /dev/rmt0

cd /home/fred; find . | backup -ivf /dev/rmt0
___________________________________________________
___________________________________________________
___________________________________________________

Checkpoint solutions
IBM Power Systems

1.

What is the difference between the following two commands?

find /home/fred | backup -ivf /dev/rmt0
cd /home/fred; find . | backup -ivf /dev/rmt0
Option a) backs up the files using the full path names, whereas
option b) backs up the file names using the relative path names.
Therefore, b)s files can be restored into any directory.

2.

On a mksysb tape, if you entered tctl rewind and then tctl

-f/dev/rmt0.1 fsf 3, which element on the tape could you look at?
You would be at the start of the backed up images of the files, having
skipped over the first three sections of the tape (boot image, mkinsttape,
and dummy toc).

3.

Which command could you use to restore these files? The files were
backed up using the backup command so you would have to use the
restore command.

4.

True or False: smit mksysb backs up all file systems, provided they
are mounted. mksysb only backs up rootvg file systems. To back up
other volume groups, you must use the savevg command.

Exercise 11
IBM Power Systems

Backup and restore

Unit summary
IBM Power Systems

Having completed this unit, you should be able to:

Explain how to back up the operating system
Create and restore a mksysb image
Explain and understand the role of both the image.data
and bosinst.data files
Back up and restore a custom volume group
Use standard AIX/UNIX backup, restore, and
compression utilities