HP Archive Backup System for OpenVMS Guide to Operations

Overview
2.4 Backup Agent
• The location of the save set (disk or tape)
• The original location of the data
• The owner of the data
Figure 2–2 shows the relationship between an ABS catalog and an ABS archive.
Figure 2–2 ABS Catalogs
SYSTEM_BACKUPS
storage policy
USER_BACKUPS
storage policy
ABS_CATALOG
PROJECT_X
storage policy
PROJECT_Y
storage policy
PROJECT_CATALOG
2.4 Backup Agent
After the installation of ABS is complete, ABS provides a default catalog named
ABS_CATALOG. By default, this catalog is associated with all archives unless it is changed by
the creator of the archive. All ABS catalogs, both the default catalog and user-created catalogs,
support lookup and restore capabilities.
ABS catalogs are node specific but in a VMScluster all nodes could share the same catalog files.
ABS uses various backup agents to save and restore data. The backup agent is determined by the
type of data, such as VMS files, Oracle Rdb databases, Oracle Rdb storage areas, UNIX files, or
Windows files. The backup agent is responsible for the actual data movement operation, while
ABS is responsible for invoking the correct backup agent and recording the information about
the save operation.
ABS supports the following backup agents:
CXO5022C
• OpenVMS BACKUP Utility - For OpenVMS files, ABS uses the OpenVMS BACKUP
Utility.
• RMU Backup Utility - For Oracle Rdb databases and storage areas, ABS uses the RMU
Backup Utility.
• gtar (GNU tar) - For UNIX and Microsoft Windows files, ABS uses gtar (aka tape archiver
or tar).
2-6 Overview