BackBox H4.00 User Manual

Product Description
20 BackBox H4.00 User Manual
Creation of virtual volumes
The virtual volumes in each set of created volumes are spread evenly across the
Data Paths on disks that contain enough free space to contain the maximum volume
size of one of these volumes.
For a Volume Group configured as AUTOSCRATCH and associated to a NonStop tape
catalog such as DSM/TC or TMF, the two files .IND and .DAT corresponding to each
empty volume are not actually created as disk files in storage while the volume’s
catalog status is SCRATCH. At volume creation time a few files are created and
immediately deleted, only to verify the disk pool’s configuration and network security
access. The remaining volumes are just registered in BackPak and DSM/TC or TMF.
Free space on remote paths
When the free space on a disk cannot be known (for example, for disks on some
remote file servers), the VTC always considers that there is enough space for the
current volume.
File access security
The files holding the virtual volumes are protected by the MS-Windows file system
security and compatible systems. The MS-Windows account / password entered in
the Data store configuration are used for all file creation and accesses.
The account must allow a successful MS-Windows login in all VTCs that are routes for
the Data store; it must be given full access to all paths specified in Data store
configuration.
The account can be a workgroup account; in this case the account must be defined
with the same password in all file servers providing a share to the Data store.
The account can also be a MS-Windows Active Directory account, and can be a non-
interactive account.
Scripting/Background Migration on Tapes
BackBox is often configured to write the backup object (files representing a virtual
tape volume) on disk for convenience and performance purposes. A migration
process then copies or moves the backup object to physical tape or other storage for
long-term retention.
There are two choices to migrate disk files on tapes: install a general HSM client in
the Windows file system or use the scripting facility of the BackBox to trigger the
archive agent of enterprise backup software, such as VERITAS or Legato.
• The general HSM solution is transparent to the BackBox software.
• The migration through the BackBox scripting is based on user written
Windows command files to run the command-line client of an Enterprise
Backup infrastructure. The user can:
o schedule regular backups in the Enterprise Backup that will
triggers itself the backups
o configure BackBox to trigger Windows command scripts when: