HP Archive Backup System for OpenVMS Guide to Operations

Saving and Restoring Data
3.5 Saves and Restores
3.4.12 Profile
3.5 Saves and Restores
– COMPLETE - Sends notification at the completion of a save or restore request with any
status (success or failure)
– WARNING - Sends notification if the request completes with a warning, error or fatal
status
– ERROR - Sends notification if the request completes with an error or fatal status
– FATAL - Sends notification if the request completes with a fatal status
You associate a TYPE and WHEN for each MAIL or OPCOM option provided. If you do not
specify a TYPE and/or WHEN, a notification option acquires a TYPE of BRIEF and a WHEN of
COMPLETE.
If you specify no notification options, then by default ABS sends a brief OPCOM message to
class TAPES on completion of every request executed under the environment.
ABS allows you to specify the user name, node name, cluster name, rights and privileges under
which save or restore requests in the environment will execute. ABS supports three main options
for username:
• ABS - This option specifies that all save and restore requests execute in the context of the
ABS user (and account). You should not change the cluster, nodes, rights or privileges with
this option, otherwise the saves and restores may not execute correctly. This is the default
option, and is recommended for all system backup operations. It is also the required option
for both UNIX and Windows client operations.
• - This option (including the angle brackets) instructs ABS to run associated
save and restore requests under the user profile of the associated save or restore request.
The save and restore user profile (which is not normally displayed and not is changeable) is
that of the user who created the save or restore request. This option should be used for user
backups. With this option you should not adjust node or cluster, but you can manipulate
rights and privileges if the user’s normal rights and privileges are not sufficient to run ABS
save and restore requests.
• Other user - This option instructs ABS to run associated save and restore requests under the
profile of a third user (not the save/restore creator or ABS). With this option, you can
manipulate rights and privileges if the user’s normal rights and privileges are not sufficient
to run ABS save and restore requests. In addition, you should also define node and/or cluster
to uniquely identify the user in the domain. Wildcard node and cluster names are supported.
It is recommended that you only specify a user profile for user backups. All other backups
should run under the default ABS user profile.
The purpose of a save request is to backup data from primary online disk storage to either alternative
disk or optical storage, or to tape storage. Saves are typically performed on a regular basis
to provide protection in the event of a disk hardware failure, data corruption or deletion, or site
disaster. Saves can also be used for archiving data that must be kept for a relatively long time for
business purposes, but does not need to be online.
The purpose of a restore request is to return data from tape or alternate disk or optical storage
back to primary online storage. In most cases, restores are performed after a disk hardware failure
or user file corruption or deletion - these are usually one-time events. However, sometimes it
is necessary to bring archived data online, and restores (perhaps scheduled restores) can be used
for this purpose also.
3-16 Saving and Restoring Data