Backup, archive, restore, and retrieve operations
This domain tests the operational difference between backup and archive and between restore and retrieve. Backup creates versions managed by backup copy groups. Archive creates a separately retained copy managed by archive copy groups and is usually retrieved by archive description.
Core rules
A backup can be incremental and produces active and inactive versions. A restore can recover the latest version or a point-in-time version, depending on available versions and retention. An archive is independent of the normal backup version cycle and is retrieved with dsmc retrieve. Administrators can also run BACKUP NODE and RESTORE NODE for server-initiated operations. Filespace information matters: a restore targets the correct node and filespace.
Worked example
A user needs /home/user/report.txt as it existed on 1 June 2024. Use dsmc restore /home/user/report.txt -pitdate=06/01/2024. If the file was archived instead, use dsmc retrieve and select the archive by description or date. The reasoning is that backup restore follows version history, while archive retrieve follows archive retention and description; choosing the wrong operation can return the latest backup instead of the required archive.
Traps
Do not treat archive as a long-term backup version. Do not assume a point-in-time restore is possible after all relevant versions expire. Do not retrieve without the correct archive description or node. Do not confuse client-side dsmc commands with administrative BACKUP NODE or RESTORE NODE.