Nfs backups, Tsm backups – Storix Software SBAdmin User Guide User Manual
Page 19
Storix System Backup Administrator
19
Version 8.2 User Guide
choose to use a name such as “ClientSystemBackups” if the directory will be used solely for
System
Backups
of clients, which may be used as network install images.
Each backup job will be assigned a unique
Backup ID
, and each client backup within the job will have a
unique
backup sequence number
. Unlike tape backups, each disk backup will have a unique name, so
there is no danger of overwriting a prior backup. Instead, the user must
expire
disk backups manually to
prevent excessive use of disk space. When doing so, not only the backup labels, but also the actual backup
files are removed from the disk. The admin may also set the
(also known as the
overwrite policy) so that a disk backup that has aged over a certain number of days, or exceeded a certain
number to retain, is automatically expired and removed when the same backup job is re-run. These options
will prevent filesystems containing disk backups from filling up while ensuring that the latest backups are
kept on file.
When you configure a directory device, you can specify multiple directories on the server as the
destination. When doing so, a backup that fills the first filesystem will be automatically continued onto the
next directory. This assumes, of course, the directories are in separate filesystems, providing the same type
of functionality as a sequential tape device with multiple drives.
When configuring a
client
(Network Edition), you can also configure a dedicated disk or disks for System
Backups of that client (often referred to as a local system backup disk, or SBDIR). This will allow a System
Backup of the client without the use of a server or network traffic, and the client can restore data or be
completely reinstalled from this local disk backup. In other words, you can boot and reinstall the system
from locally-attached (or even SAN-attached) disks, providing complete system backup and recovery using
only a local disk. You can also use this disk as portable media, which can be directly attached and used to
install other systems. More information can be found in
Configuring Local System Backup Disks
Backup status, output, and label information may be displayed for disk backups just as with tape backups.
NFS Backups
Backups may be written to locally mounted NFS shares. Writing to a locally mounted NFS share minimizes
network in that only the backup client and the NFS server are creating network traffic. This feature requires
that each backup client, and the admin system, be able to mount the NFS share read-write. It is also not
expected that any SBAdmin software is installed on the physical NFS server. More importantly, the
configuration of the NFS server that is exporting the share is the sole responsibility of the user.
When using Network Edition, you will configure the NFS share to be used by the backup clients using a
. When using Workstation Edition, you will configure a
Backup status, output, and label information may be displayed and managed for backups to NFS just as
with directory devices.
TSM Backups
Any backup may be written to a TSM server. With TSM backups, each filesystem or logical volume within
the backup is stored in a different TSM object, so access to the data is much faster than reading the entire
backup.
Refer to the
SBAdmin TSM Edition User Guide
to view only the options available
when using TSM Edition.
The TSM Client Backup Feature (for Network Edition) provides all backup types and options of a TSM
client (node) to a TSM server. In this case, TSM is simply an added backup media option to the existing
administrator license. When the TSM Edition is installed, however, the TSM server will be the only backup
media option, and only System Backups are supported. This provides a more cost-effective means for
users of TSM to simply add system backup and adaptable system recovery (ASR) to their daily backup
routine.