batavus
ADSM.ORG Member
Ok - I'm at a loss here. When backing up DB2 databases, for some reason the data ends up going straight to tape instead of first going to the BACKUPPOOL (as the policy is set to). What causes this?
I have 200GB in disk storage pool BACKUPPOOL - all consisting of 2.5GB volumes.
The DB2 session ends up directly opening a sequential volume and writes to it instead of writing to the disk storage pool first - wtf?!
Sess Number: 21,266
Comm. Method: Tcp/Ip
Sess State: RecvW
Wait Time: 0 S
Bytes Sent: 6.3 K
Bytes Recvd: 2.2 G
Sess Type: Node
Platform: DB2/AIX64
Client Name: RFPRODDB
Media Access Status: Current output volume(s): TSM013,(258 Seconds)
User Name: navrpt
Date/Time First Data Sent: 04/19/05 21:29:56
Proxy By Storage Agent:
Why would it write to sequential (LTO2) first instead of writing to the disk storage pool (that has adequate storage space available)?
I have 200GB in disk storage pool BACKUPPOOL - all consisting of 2.5GB volumes.
The DB2 session ends up directly opening a sequential volume and writes to it instead of writing to the disk storage pool first - wtf?!
Sess Number: 21,266
Comm. Method: Tcp/Ip
Sess State: RecvW
Wait Time: 0 S
Bytes Sent: 6.3 K
Bytes Recvd: 2.2 G
Sess Type: Node
Platform: DB2/AIX64
Client Name: RFPRODDB
Media Access Status: Current output volume(s): TSM013,(258 Seconds)
User Name: navrpt
Date/Time First Data Sent: 04/19/05 21:29:56
Proxy By Storage Agent:
Why would it write to sequential (LTO2) first instead of writing to the disk storage pool (that has adequate storage space available)?