Configuring IASP hosts
This section of the setup wizard focuses on setting the correct storage information for any database IASPs.
- Database IASP - An IASP that is designated for database and other system objects that will be replicated by Db2 Mirror. These IASPs require storage on both the setup source and setup copy nodes. During the setup process, the data that resides in the IASP on the source node will be copied into the identified storage on the copy node. Just like the SYSBAS requirement, the IASP storage must be the same capacity.
- IFS IASP - An IASP that will be used only for integrated file system (IFS) data. It will not be replicated by Db2 Mirror. There is only one copy of the data. The setup wizard does not allow an IFS IASP to be configured during the initial setup process. You can define an IFS IASP after the clone has completed. See Adding IFS IASPs to Db2 Mirror.
Each IASP found on the source node that could be a database IASP is listed. You must identify the usage of each IASP. For each IASP, select DB IASP Only or Ignore. Remember that IFS IASPS are configured after the clone has completed.
Primary and secondary IASPs are treated as a group. Only the primary IASP is registered to the Db2 Mirror environment.
In order to select DB IASP Only, the IASP on the setup source node must be varied on. If it is not varied on, select the row and click Vary On. This will run the vary on action for this IASP on the setup source node. The vary on may take a few minutes to complete. Once the IASP is varied on, select the DB IASP Only option from the select box.
For each database IASP, a copy host must be selected. Click Select to display the list of existing hosts and select the storage host for the setup copy node.

The setup wizard will automatically map disk units between the source and copy hosts based on size and data type. The mapping can be manually adjusted by dragging and dropping disks to rearrange the pairing and select disks that were not selected by the auto mapper.
Advanced button
- For IBM Storage Virtualize Flash Copy, the copy rate can be selected.
- For a warm clone, you have the option to automatically vary on database IASPs on the copy node after cloning.
- For a cold clone, you have two options.
- Automatically vary off database IASPs on the source node before cloning. Having an IASP varied off provides a cleaner copy during the clone process.
- Automatically vary on database IASPs on the source and copy nodes after cloning is complete.
Figure 2. Advanced Settings for database IASPs
Click Save and Continue to proceed to the next step.