You can perform at the source server the operations shown in this section and the data is stored in a storage pool at the target server. In these examples, the following is assumed:
You can back up the database of a source server to a target server. For example, to perform an incremental backup of the source server and send the volumes to the server TARGET1, issue the following command:
backup db type=incremental devclass=targetclass
| Expiration Processing of Database Backup Volumes with the DRM Feature: | If your server is licensed for the DRM feature, expiration processing can
delete volumes containing expired database backups. One or more
database backup volumes may be deleted from the volume history during
expiration processing if the following conditions are true:
|
You can also do an automatic database backup to a target server. For example, if you have issued the following command, a database backup occurs automatically when more than 60 percent of recovery log space is used:
define dbbackuptrigger devclass=targetclass logfullpct=60
You can back up a storage pool of a source server to a target server. For example, a primary storage pool named TAPEPOOL is on the source server. You can define a copy storage pool named TARGETCOPYPOOL, also on the source server. TARGETCOPYPOOL must have an associated device class whose device type is SERVER. When you back up TAPEPOOL to TARGETCOPYPOOL, the backup is sent to the target server. To do so, issue the following commands:
define stgpool targetcopypool targetclass pooltype=copy maxscratch=20
backup stgpool tapepool targetcopypool
You can configure your ADSM system so that when client nodes registered at the source server back up, archive, and migrate their data, it is sent to the target server. When clients restore, retrieve, or recall their data, the source server gets the data from the target server. Clients perform these operations just as they normally would.
To configure your system, ensure that the management policy for those nodes specifies a storage pool that has a device class whose device type is SERVER. For example, the following command defines the storage pool named TARGETPOOL.
define stgpool targetpool targetclass maxscratch=20 reclaim=100
| Note: | Reclamation of a storage pool automatically begins when the percentage of reclaimable space, which is specified by the RECLAIM parameter, is reached. Reclamation of a target storage pool can involve the movement of a great deal of data from the target server to the source server and back to the target. If this operation occurs automatically during peak operating periods, it could slow network performance significantly. If you set the value to 100, reclamation will not occur automatically. For details about storage pool reclamation and how to begin it manually, see "Reclaiming Space in Sequential Access Storage Pools". |
You can set up your storage pool hierarchy so that client data is migrated from a storage pool on the source server to the target server. For example, storage pool TAPEPOOL is on the source server. The TAPEPOOL definition specifies NEXTSTGPOOL=TARGETPOOL. TARGETPOOL has been defined on the source server as a storage pool of device type SERVER. When data is migrated from TAPEPOOL, it is sent to the target server.
define stgpool tapepool tapeclass nextstgpool=targetpool maxscratch=20
You can use any of the ADSM EXPORT commands to export data from an ADSM source server to sequential media on a target ADSM server. You must specify a device class with a device type specified as SERVER. For example, to copy server information directly to a target server defined as TARGET1, issue the following command:
export server devclass=targetclass
If data has been exported from a source server to a target server, you can import that data from the target server to a third server. The server that will import the data uses the node ID and password of the source server to open a session with the target server. That session is in read-only mode because the third server does not have the proper verification code.
For example, to import server information from a target server defined as TARGET1, issue the following command:
import server devclass=targetclass