Configured system backup disk, Configuring local system backup disks, Disk – Storix Software SBAdmin User Guide User Manual

Page 53: Local system backup disks

Advertising
background image

In the Disk(s) for Local System Backups field, select the arrow to the right to display and select one or more
disks to use. When selecting more than one disk Volume Groups or Zpools will be used to combine the disks
into a single device. If disks are to be used in rotation they must be configured individually. If no disks appear in
the list, then there are no spare disks available on the system. Those disks which appear in the list are those
believed to be unused by other data. Select one or more disks from the list.

Be absolutely sure the disk you select does not contain any needed data! Using this
option will overwrite the entire contents of the disk!


Disks labeled IN_USE are disks marked removable and may be mounted by the
operating system. They will be automatically un-mounted if used.

Disks containing partitions (Linux) or slices (Solaris) are considered available for a
Local System Backup Device if they are not mounted or defined to be mounted.

Disks configured as LVM Physical Volumes (Linux/AIX) are considered available if
they are either not assigned to a Volume Group or the Volume Group was exported.
Although not mounted, if there is an entry in the /etc/fstab (Linux
) or /etc/vfstab
(Solaris
), SBAdmin will consider the disk not available.


In the Disk Label field, enter something that may be used to identify the physical disk(s).

By default SBDIR will be used as the disk label. All disks may use this label and will
still contain a unique identifier for telling devices apart.

In the Maximum Volume Size field, enter the size (in MB) the maximum file size of the backup image that
will be created. Enter “0” for unlimited. See section Maximum Volume Size for more information.

A small amount of disk space at the beginning of each disk is reserved for making the disk bootable. The
contents of the remainder of the disk depend on the option selected, and will depend on the operating
system of the client:

Configure using LVM (AIX and Linux) – If Logical Volume Management is installed on Linux, then
it may be used to configure one or more disks into a Volume Group. This is the default and only
option for AIX systems. Within this volume group, a Logical Volume is created, containing the
backup filesystem. This filesystem may be limited in size using the Maximum Volume Size field,
or it can span the entire volume group, and therefore more than one physical disk.

Configure using ZFS (Solaris) – For systems using ZFS, one or more disks may be used to create
a ZFS pool and ZFS filesystem for used for system backup and recovery.

Configure using Partition/Slice (Linux/Solaris) – For systems that do not have LVM or ZFS, a
single disk may be configured for system backup/recovery by creating the backup filesystem in a
disk partition/slice. A single partition/slice will be created using the entire disk space (minus the
bootable portion). Since a partition/slice may not span multiple disks, the disk used in this case
must be large enough to write an entire system backup.

Partition Table Type (Linux) – It is recommended that a GPT partition table be used when
configuring a system backup disk larger than 2 TB. However, when using a GPT partition table, the
disk will only be configured to boot from UEFI firmware and not BIOS. The default is MSDOS.

UEFI Boot Support (Linux) – This option is only enabled for systems that have support for booting
from UEFI firmware, and selecting “Yes” to this option will make the disk bootable from UEFI
firmware. When using a MSDOS partition table, the disk will be made bootable for both UEFI and
BIOS. When using a GPT partition table, the disk will be made bootable from UEFI only.

Storix System Backup Administrator

53

Version 8.2 User Guide


Advertising