First,
archive and
backup are two different things and each have their own copygroup to control the destination.
Backups and archives are both performed from the client.
- backups use the destination in the backup copygroup of the management class used to determine in which primary storage pool they are stored
- archives use the destination in the archive copygroup of the management class used to determine in which primary storage pool they are stored
The destination of both those copygroups can be the same or different.
Once it's in that storage pool, it's all controlled on the server side. You can migrate the data from any primary storage pool (disk, file, tape, directory) to any primary storage pool (disk, file, tape, directory), but you can't control what node is migrated, it's an all or nothing and you can just control the percentage you migrate. HELP MIGRATE STGPOOL for more info. You can move data from one node from any primary storage pool to any primary storage pool. HELP MOVE NODEDATA for more info.
If you want your backup and/or archive to go directly to tape, make sure to use a management class that the corresponding copy groups have a destination of a tape pool:
https://ibm.biz/Bdr9M2
