Dear Parther.

I haved the following problem.

I Trying Restore backup offline ( 320 GB) in the server test. This restored takes around 8 hours, very long time, for the activity that I try to execute.

This backup makes it in tape ( IBM 3580 Ultrium Tape Drive).

Configuration of server TARGET ( test) is:

OS AIX 5.3
RAM 23 GB
PROCESSOR 2 ( 2 GHZ ) POWER 5
TAPE IBM 3580 Ultrium Tape Drive

Database Manager Configuration

Node type = Enterprise Server Edition with local and remote clients

Database manager configuration release level = 0x0a00

CPU speed (millisec/instruction) (CPUSPEED) = 3.306409e-07
Communications bandwidth (MB/sec) (COMM_BANDWIDTH) = 1.000000e+02

Max number of concurrently active databases (NUMDB) = 8
Data Links support (DATALINKS) = NO
Federated Database System Support (FEDERATED) = NO
Transaction processor monitor name (TP_MON_NAME) =

Default charge-back account (DFT_ACCOUNT_STR) =

Java Development Kit installation path (JDK_PATH) = /usr/java14_64

Diagnostic error capture level (DIAGLEVEL) = 3
Notify Level (NOTIFYLEVEL) = 3
Diagnostic data directory path (DIAGPATH) = /db2/AEP/db2dump

Default database monitor switches
Buffer pool (DFT_MON_BUFPOOL) = ON
Lock (DFT_MON_LOCK) = ON
Sort (DFT_MON_SORT) = ON
Statement (DFT_MON_STMT) = ON
Table (DFT_MON_TABLE) = ON
Timestamp (DFT_MON_TIMESTAMP) = ON
Unit of work (DFT_MON_UOW) = ON
Monitor health of instance and databases (HEALTH_MON) = ON

SYSADM group name (SYSADM_GROUP) = DBAEPADM
SYSCTRL group name (SYSCTRL_GROUP) = DBAEPCTL
SYSMAINT group name (SYSMAINT_GROUP) = DBAEPMNT
SYSMON group name (SYSMON_GROUP) =

Client Userid-Password Plugin (CLNT_PW_PLUGIN) =
Client Kerberos Plugin (CLNT_KRB_PLUGIN) =
Group Plugin (GROUP_PLUGIN) =
GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =
Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED
Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =
Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =
Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED
Database manager authentication (AUTHENTICATION) =
SERVER_ENCRYPT
Cataloging allowed without authority (CATALOG_NOAUTH) = NO
Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
Bypass federated authentication (FED_NOAUTH) = NO
Default database path (DFTDBPATH) = /db2/AEP
Database monitor heap size (4KB) (MON_HEAP_SZ) = 128
Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC
Backup buffer default size (4KB) (BACKBUFSZ) = 4096
Restore buffer default size (4KB) (RESTBUFSZ) = 4096
Sort heap threshold (4KB) (SHEAPTHRES) = 20000
Directory cache support (DIR_CACHE) = NO
Application support layer heap size (4KB) (ASLHEAPSZ) = 16
Max requester I/O block size (bytes) (RQRIOBLK) = 65000
Query heap size (4KB) (QUERY_HEAP_SZ) = 2000
Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10
Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 1024
Agent pool size (NUM_POOLAGENTS) = 10
Initial number of agents in pool (NUM_INITAGENTS) = 5
Max number of coordinating agents (MAX_COORDAGENTS) = MAXAGENTS
Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS
Keep fenced process (KEEPFENCED) = YES
Number of pooled fenced processes (FENCED_POOL) = MAX_COORDAGENTS
Initial number of fenced processes (NUM_INITFENCED) = 0
Index re-creation time and redo index build (INDEXREC) = RESTART
Transaction manager database name (TM_DATABASE) = 1ST_CONN
Transaction resync interval (sec) (RESYNC_INTERVAL) = 180
SPM name (SPM_NAME) =
SPM log size (SPM_LOG_FILE_SZ) = 256
SPM resync agent limit (SPM_MAX_RESYNC) = 20
SPM log path (SPM_LOG_PATH) =
TCP/IP Service name (SVCENAME) = sapdb2AEP
Discovery mode (DISCOVER) = SEARCH
Discover server instance (DISCOVER_INST) = ENABLE
Maximum query degree of parallelism (MAX_QUERYDEGREE) = 1
Enable intra-partition parallelism (INTRA_PARALLEL) = NO
No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 4096
Number of FCM request blocks (FCM_NUM_RQB) = AUTOMATIC
Number of FCM connection entries (FCM_NUM_CONNECT) = AUTOMATIC
Number of FCM message anchors (FCM_NUM_ANCHORS) = AUTOMATIC
Node connection elapse time (sec) (CONN_ELAPSE) = 10
Max number of node connection retries (MAX_CONNRETRIES) = 5
Max time difference between nodes (min) (MAX_TIME_DIFF) = 60
db2start/db2stop timeout (min) (START_STOP_TIME) = 10

THEY COULD HELP ME WITH SOME RECOMMENDATION WHICH CAN IMPROVE THE TIME OF RESTORED ( MAX 3 OR 4 HOURS)

Thanks for you valuable colaboration

Alexander Tapiero Rodriguez

Hi,
don't know if this helps in your case. You didn't specify your DB2 version/fixpack (command: db2level) and edition (command: db2licm -l).

I assume tape drive is bottle neck... and I assume you use DB2 v8 at least fixpack 4 or later (DB2 v9 or DB2 v9.5 are also OK)... if so you can use compress backup image functionality.

How to use compression?

Idea: compressed backup database will reduce disk space on tape device for about 80%. This will reduce a lot of time if tape drive is bottle neck.

Compression/decompression is done in memory so reading I/Os from tape device could be reduced dramatically. Reducing I/O will result in reduced restore time.

How to restore from compressed database?

The command is the same as usual restore. Why? Because compression library is stored in backup image so restore just extracts compression library from backup image and then executes decompression.

You can read more in the following article: http://www.ibm.com/developerworks/db...501zikopoulos/
Just scroll down to "DB2 V8.1.4" chapter.

Just a note: compression will use more CPU power both on production to compress database and also on test to decompress. You can also use util_impact_prority parameter using backup to reduce CPU power impact at backup time (at above link also read "DB2 V8.1.2" chapter). I guess restore is not the problem, because it is on test computer.

And sample:
Hope this helps,
Grofaty