Informix Restore Problem
Posted in 2004
Topics: Backup & Restore, Performance & Tuning, Storage & Space Management, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration
Hi Gurus,
I have some questions concerning a restore problem I have with an Informix
database running version 7.31.TD1X2 on Windows 2000 Advanced Server with
SP4. This server runs SAP 46C. Storage manager is Arcserve V9 with informix
agent that talks to xbsa interface and onbar. The online backup takes only
5 hours to complete but the online restore (cold) is taking 50 hours to
complete. On Windows NT the times were about 5-6 hours for an online backup
and about 8-9 hours to restore.
What influences how long a restore will take to complete? Is there any
parameters that will influence the performance of the restore? How does
onbar work when restoring the database?
What tends to happen is that the drive where the xbsa.log file is kept is
constantly being highly utilized and the log file is constantly being
written to while the restore is only performing about 75MB/min. The
informix data is on a seperate controller and system bus compared to the
OS/informix exes and arcserve exes. Attached is the contents of the
onconfig file.
Any comments or suggestions highly welcomed.
Thanks and regards
Stefan
#**************************************************************************
#static char sccsid[] = "@(#)ONCONFIG.TPL 20.2.5.1 SAP
97/07/14";
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.SAP
# Description: INFORMIX-OnLine Configuration Parameters for SAP R/3
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace name
ROOTPATH G:\\informix\\NYP\\sapdata\\ROOTDBS.000 # Path for devicecontaining root dbspace
# Path for device containing root dbspace
# Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)#ROOTSIZE 499712 # Size of root dbspace (Kbytes) 7.30TC7
changed this 17/10/99
ROOTSIZE 500004 # Size of root dbspace (Kbytes)# Disk Mirroring Configuration Parameters
MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH # Path for device containing mirrored root
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)# Physical Log Configuration
PHYSDBS physdbs # Location (dbspace) of physical log
PHYSFILE 500004 # Physical log file size (Kbytes)# Logical Log Configuration
LOGFILES 199 # Number of logical log files
LOGSIZE 500 # initial (!) Logical log size (Kbytes)# Diagnostics
MSGPATH e:\\informix\\nyp/online.nylexnyp.nyp.log # System message log
file path
# System message log file path
# System message log file path
CONSOLE e:\\informix\\nyp/console.nylexnyp.nyp.log # System console
message path
# System console message path
# System console message path
ALARMPROGRAM e:\\informix\\nyp\\etc\\log_full.bat # Alarm program path
# System Archive Tape Device
TAPEDEV \\\\.\\TAPE0 # Tape device path#TAPEDEV NUL # NUL path temporary
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 45000000 # Maximum amount of data to put on tape
(Kbytes)# Log Archive Tape Device
#LTAPEDEV e:\\IFMXBKUP\\IFMXBKLG.BAK # Log tape device path
#LTAPEDEV NUL # Log tape device path
LTAPEDEV \\\\.\\TAPE0 # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 45000000 # Max amount of data to put on log tape
(Kbytes)
# OpticalSTAGEBLOB # INFORMIX-OnLine/Optical staging area
# System Configuration
SERVERNUM 0 # Unique id corresponding to a OnLineinstance
DBSERVERNAME nylexnypnyptcp # Name of default Dynamic Server
DBSERVERALIASES nylexnypnyptcp # List of alternate dbservernames
NETTYPE soctcp,1,100,NET # Override sqlhosts nettype parameters
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
env.
RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
MULTIPROCESSOR 1 # Tune for new CPUs SGabriel 15Feb04
NUMCPUVPS 2 # Tune for new CPUs SGabriel 15Feb04
SINGLE_CPU_VP 0 # Tune for new CPUs SGabriel 15Feb04MUTEX_WAIT_LISTS 0 # If non-zero, force use of mutex wait
lists
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors# Shared Memory Parameters
LOCKS 1500000 # Maximum number of locks - EarlyWatch
7/9/99
BUFFERS 175000 # Use more memory 21/02/2004 SGabriel
NUMAIOVPS 2 # EarlyWatch Recommendation 28/03/2004SGabriel
PHYSBUFF 1024 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 200 # Maximum number of logical log files
CLEANERS 8 # Number of buffer cleaner processes SAPEarlywatch Go-Live 46C SGabriel 27/7/03
SHMBASE 0x20000000 # Shared memory base address
SHMVIRTSIZE 398656 # initial virtual shared memory segmentsize
SHMADD 32768 # Size of new shared memory segments(Kbytes) SAP Earlywaqtch Go-Live 46C SGabriel 27/7/03
SHMTOTAL 0 # Total shared memory (Kbytes). 0
=>unlimited
CKPTINTVL 1800 # Check point interval (in sec)
LRUS 4 # Number of LRU queues SAP Earlywatch
G-Live 46C SGabriel 27/7/03
LRU_MAX_DIRTY 10 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 5 # LRU percent dirty end cleaning limit
# Caution:# The settings of LTXHWM to 70 and LTXEHWM to 80 will produce a warning in
the
# online log file, but the values are correct in an SAP R/3 environment
# From old system 25/04/99 SCS
# reduced by 10; 14.02.1999; Roland Wartenberg, SAP AG Walldorf
LTXHWM 60 # Long transaction high water markpercentage
LTXEHWM 70 # Long transaction high water mark
(exclusive)
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)# System Page Size
# BUFFSIZE - OnLine no longer supports this configuration parameter.
# To determine the page size used by OnLine on your platform
# see the last line of output from the command, 'onstat -b'.
# Recovery Variables
# OFF_RECVRY_THREADS:
# Number of parallel worker threads during fast recovery or an offline
restore.
# ON_RECVRY_THREADS:
# Number of parallel worker threads during an online restore.
OFF_RECVRY_THREADS 10 # Default number of offline workerthreads
ON_RECVRY_THREADS 1 # Default number of online worker threads# Data Replication Variables
# DRAUTO: 0 manua
Stefan.Gabriel@nylex.com.au wrote:
> Hi Gurus,
>
> I have some questions concerning a restore problem I have with an Informix
> database running version 7.31.TD1X2 on Windows 2000 Advanced Server with
> SP4. This server runs SAP 46C. Storage manager is Arcserve V9 with informix
> agent that talks to xbsa interface and onbar. The online backup takes only
> 5 hours to complete but the online restore (cold) is taking 50 hours to
> complete. On Windows NT the times were about 5-6 hours for an online backup
> and about 8-9 hours to restore.
>
> What influences how long a restore will take to complete? Is there any
> parameters that will influence the performance of the restore? How does
> onbar work when restoring the database?
>
> What tends to happen is that the drive where the xbsa.log file is kept is
> constantly being highly utilized and the log file is constantly being
> written to while the restore is only performing about 75MB/min. The
> informix data is on a seperate controller and system bus compared to the
> OS/informix exes and arcserve exes. Attached is the contents of the
> onconfig file.
>
> Any comments or suggestions highly welcomed.
>
<SNIP>
> DBSERVERNAME nylexnypnyptcp # Name of default Dynamic Server
> DBSERVERALIASES nylexnypnyptcp # List of alternate dbservernames
It is "odd" to have two identical names for DBSERVERNAME and
DBSERVERALIAS (perhaps even ... wrong)
> BUFFERS 175000 # Use more memory 21/02/2004 SGabriel
> NUMAIOVPS 2 # EarlyWatch Recommendation 28/03/2004 SGabriel
If this behaviour is "recent" then this looks like a recent change!
> PHYSBUFF 1024 # Physical log buffer size (Kbytes)
Whoa there Lesley ... really big PHYSBUFF - 32k perhaps
> CKPTINTVL 1800 # Check point interval (in sec)
Why checkpoint every 30 minutes, instead of 5 which is the default?
> LRUS 4 # Number of LRU queues SAP Earlywatch G-Live 46C SGabriel 27/7/03
Seems really low for 4 * 175000 BUFFERS (700Mb of buffers would probably
need about 60 to 120 LRUs
> BAR_ACT_LOG /tmp/bar_act.log #Path of log file for onbar.exe
> BAR_MAX_BACKUP 1 #Informix Backup Agent
> BAR_RETRY 1
> BAR_NB_XPORT_COUNT 10
> BAR_XFER_BUF_SIZE 31> # Read Ahead Variables
RA_PAGES 32
RA_THRESHOLD 30
Nah ... RA_PAGES 32 / RA_THRESHOLD 8
> BAR_BSALIB_PATH E:\\PROGRA~1\\CA\\BRIGHT~1\\libbsa.dll #Informix Backup Agent
> XBSA DLL
>
> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT)
> OPTICAL_LIB_PATH \\SAPDATA\\PSAPBTAB.046
> RESTARTABLE_RESTORE off #To support restartable restore..values
> on/off> ISM_DATA_POOL ISMData
> ISM_LOG_POOL ISMLogs
Apart from that ... what is being written to the xbsa.log files (i.e.
where you say all the activity is going on)?
Related threads
- onbar -c -F in Windows Informix instance
- Anyone... SQLCODE=-668, ISAM error=-1
- Not using the 100% logical log page size alloacted to informix