Prerequisites

This section covers the CA ACF2 for VM components that are important for backup and recovery.

BACKUP VMO Record

The BACKUP VMO record defines various backup options. Complete information on the BACKUP VMO record is in the chapter “Defining Structured Infostorage Records” of this guide.

ACFFDR @DDSN Macro

The @DDSN macro defines the name of a group of CA ACF2 for VM databases and the filenames (or VSAM data set names) of the three CA ACF2 for VM databases. You can define up to 16 @DDSN macros. This lets you have a primary set of databases and multiple sets of alternate databases. You must also define a @DDSN macro for backups. This could be any @DDSN, including PRIMARY, as long as it is for CMS databases. We recommend you define at least one set of alternate databases.

FORCEID Users

The FORCEID= operand of the VMXAOPTS macro in HCPAC0 defines the user IDs that can log on when CA ACF2 for VM is not active (NOAUTO mode).

Noauto Update Users

Besides FORCEIDs, CA ACF2 for VM also provides a user ID that enables authorized users to log onto CA ACF2 for VM in NOAUTO mode and update the databases. You must identify these user IDs with the NOAUTOU parameter in VMXAOPTS in HCPAC0. These user IDs become part of the NOAUTOU list. All user IDs defined in the NOAUTOU list must also be defined in the FORCEID list. The user IDs defined in both the NOAUTOU list and in the FORCEID list are called noauto update users. Only these users can log onto CA ACF2 for VM in NOAUTO mode and issue the appropriate ACFSERVE commands to update the databases. For more information on these ACFSERVE commands, see the “Updating the Databases in NOAUTO Mode” chapter.

ACFFDR @SMF Macro

The @SMF macro defines options related to SMF processing. This is a very important component for backup and recovery because it defines the number of defined SMF minidisks and their virtual addresses.

SMF Minidisks and Files

Database recovery procedures use historical SMF data. The recovery procedures can access the SMF data in any of the following formats:

Old format SMF files.
New format historical SMF files
Dumped and archived SMF disks.
ACFSMCOP copied and archived SMF disks. (For additional information on the ACFSMCOP utility, see the Reports and Utilities Guide.
New format online SMF disks. You must use current (online) SMF disks. They are volatile because a SMF disk can become active and reused for recording at any time unless the system was IPLed in NOAUTO mode.

Primary CA ACF2 for VM Databases

These are the CA ACF2 for VM databases normally in use. The first @DDSN macro in the ACFFDR specifies the primary databases. These databases usually have the @DDSN name of PRIMARY (@DDSN PRIMARY).

Alternate CA ACF2 for VM Databases

The @DDSN macros in the ACFFDR define alternate databases. Use them:

To bring up the system with a minimum amount of delay if the primary databases are unavailable. If you do not merge SMF data with the alternate database before you bring up the system, you can lose changes to the databases.
To speed up the recovery process if the primary databases are unavailable. By building the alternate databases from backup files each time you take a backup, you eliminate this step when an emergency situation occurs. Performance issues should determine whether you should build alternate databases after backups or only when recovery is necessary. Having alternates built after each backup gives you more options if a disaster occurs.