The following table shows for each function:
in the first and second column the location of the metadata (archive definitions and requests).
in the third column whether the requests can be restarted after the change of host.
in the last column the environment that can be specified for files and job variables.
Archive definition in the control file | Request in the request file | Restart after change of host? | Scope of the files/JV | |
Backup of SF pubsets | on the host | on the host | not possible | all SF pubsets |
Backup of an SM pubset | on the SM pubset | on the SM pubset | possible | this SM pubset |
| Version backup of an SF pubset | on the host | on the host | not possible | this SF pubset |
| Version backup of an SM pubset | on the SM pubset | on the SM pubset | possible | this SM pubset |
Migration of SF pubsets | on the host | on the host | not possible | all SF pubsets |
Migration of an SM pubset | on the SM pubset | on the SM pubset | possible | this SM pubset |
Long-term archival of the host | on the host | on the host | not possible | all pubsets |
Archival of SM pubsets | on the SM pubset | on the SM pubset | possible | this SM pubset |
Export/import | not relevant | always on the host | not possible | all pubsets |