Filter
Top Products
Configuring a Two Host System
17
o hdisk42
o hdisk40
o hdisk38
o hdisk37
o hdisk43
• The source and target volume of each FlashCopy pair reside in the same ESS
LSS.
Note: The root userid must be used to execute all ESS and AIX commands, and to
install DB2 and create the DB2 instance. The remainder of the DB2 commands are
executed from the ID db2ts1,which is the DB2 instance-owning ID.
1. Create the logical volumes in each LSS and assign them to the Primary Server
and the Backup Server via the Web interface of the StorWatch Enterprise
Storage Specialist.
2. From each AIX server run cfgmgr to define SCSI paths to the ESS.
3. Create a FlashCopy task for the SAP system via the ESS Copy Services Web
interface:
a) Create the task ts1sap to flash the disk on which the SAP software is
installed.
b) If you defined the task ts1sap with the ‘no copy’ option, you must also
define another task called ts1sapwd to withdraw the FlashCopy pair for the SAP
software. If you did not specify ‘no copy’ do not create ts1sapwd.
We will need a number of FlashCopy tasks for the database file systems to
support the different scenarios:
a. Create the tasks ts1db_10 to ts1db_17 to flash the logical volumes
containing the database data and log files in each LSS. If you create the
tasks with the no copy option, you must create appropriate tasks
ts1db_10_wd to ts1db_17_wd to withdraw the FlashCopy pairs.
b. Group the tasks as follows:
Group ts1db_10 to ts1db_17 into task, ts1db
Group ts1db_10_wd to ts1db_17_wd into task ts1dbwd.
With these tasks FlashCopy pairs for the data and log file systems of the
database can be established and withdrawn.
For the Standby Database Scenario we need a FlashCopy task that only
handles the database data filesystems without the log filesystem. We group
the tasks ts1db_10 to ts1db_16 into the group task ts1dbdata and the tasks
ts1db_10_wd to ts1db_16_wd into the group task ts1dbdatawd. We will also
need a FlashCopy task for flashing the log filesystem and for withdrawing the
FlashCopy pair.