You must have SMS active on your system to perform aggregate backup.
Prior planning is suggested if you want to back up SMS-managed
data sets and have them recovered later in an environment compatible
to that which existed at the backup site. It is recommended that the
SMS classes retain the same attributes both at the backup and at the
recovery sites. The ACS routines should also be compatible.
If you do not have identical SMS environments at both sites, SMS-managed
data sets can still be successfully recovered, but not necessarily
in the environment in which they existed at the backup site. The SMS-managed
data sets are recovered in one of the ways described in
Considering storage management subsystem requirements.
Note: - You might want to specify the required SMS class names and attributes
in the instruction data set when you perform aggregate backup. See Creating an instruction data set.
- All SMS class names that are encountered during aggregate backup
processing—along with their associated attributes—are
listed in the ABACKUP activity log. This information can be retrieved
during ARECOVER PREPARE processing and used to define the SMS environment
at your recovery site. You should also consider backing up the source
control data sets (SCDSs) as a separate aggregate group so that you
can recover them as an aggregate before recovering application data.