Storix Software SBAdmin Commands Reference - Manual (Page 35)

Storix System Backup Administrator - 35 - Version 8.2 Commands Reference
cdrom: This option does not write to the CDROM drive. Therefore, no CDROM is required on
the system used to create the ISO. A CDROM “ISO” filesystem image will be created,
which should then be “burned” to a CDROM/DVD disc. If a server is specified (with the -s
option), the image will be copied to the “Directory for CLIENT CDROM/network boot
images” configured on the server.
disk: This option will make a Local System Backup Disk bootable. The disk to make bootable
must first have been configured as a Local System Backup Disk. Refer to the SBAdmin
User Guide for more information.
tape: Create a bootable tape. The tape images will be created on the local system, but may be
written to a remote tape drive if the –s server option is specified. This option is currently
only available on IBM System p and System i systems, since they are the only supported
systems which have firmware capable of detecting and booting from tapes.
netboot: Create network boot image. You must specify a name for the image using the –l
imagename option. If the specified image already exists, it will be overwritten by the new
image. If a server is specified (with the -s option), the network boot images will be copied
to the “Directory for CLIENT CDROM/network boot images” configured on the server.
netclient: Configure or unconfigure a client for network boot. This option must be performed
on the network boot server. If configuring a network boot client, the –l imagename option
is required as well as the –c client option. The imagename specified must have first been
created using the –t netboot option in a separate stmakeboot command.
initrd-disk: For Linux, this option will create the initrd/initramfs image without updating the
boot loader. This is helpful if you want to create an initrd image and configure your boot
loader manually. You may specify the name of the image to create (with the –o option), or
SBAdmin will create one as /boot/initrd-storix-disk (where disk is the hard disk to boot
from).
If you want to create boot media for a different platform or kernel type than the current
system, you may specify the –p platform and –k kernel options respectively. If you want to
create the boot image suitable for booting the local system, you do not need to specify these
options. If you specify a platform type, the device support for the specified platform must have
been installed onto the local system. Likewise, if a different kernel type is specified, the fileset
containing the specified kernel must also be installed.
On AIX, for instance, the local system is an RSPC system running under the “up”
(uniprocessor) kernel, but you want to create boot media which will boot a CHRP system with
a 64-bit kernel, specify “-p chrp –k 64”. Note that the resulting boot media will not boot the
local system, but can be used to migrate a system backup to new hardware.
Likewise, for Linux, you may specify a specific kernel to use with the –k when creating boot
media or when updating the disk boot loader. You may also use the –R option to specify the
release level of the kernel to use. In this case, the command will search for a kernel which
uses the specified release level as a suffix (in the /boot or /yaboot directories). If specifying a
release level, there must be a matching modules directly as /lib/modules/release. If both –k
and –R are omitted, the release level the system was booted under (displayed with “uname –
m”) will be used.
On Linux, Specify the –C option only if you have a serial terminal attached to the first serial
port of the system and wish to perform the system installation using that display. If –C is
specified, the attached terminal must be set to 9600 baud, 8 bits, 1 stop bit and no parity for
proper communication. Omit the –C option if you want to perform the installation using the
graphical console attached to a graphics adapter.