RE: Backup toooo slow.

What performance do you expect from your tape drive? How fast can you get other backups going to that drive? (Gb/hour). What is the optimum block size writing to that device? and set TAPEBLK to that block size. Is there a problem with the tape or tape drive - doing re-writes or re-reads? Regards Murray Wood Gursoy YERLI <gursoy@ata.net> schrieb in im Newsbeitrag: 7hi3qf$jcm$1@news.xmission.com... > > Sorry guys, I repeat my question with valid information. > > What are the reasons for slow data backup. Process usually locks-up the > whole system. I've checked everything I know. But still have slow backup > process. We have tried both on tape and disk devices. Also ontape and > onbar does not make any difference. > > Gursoy YERLI > > Informix 7.23 TC1 > Windows NT 4.0 SP4 > 4 CPU's > 256MB > > ONCONFIG > -------- > ROOTNAME phcsroot # Root dbspace name > ROOTPATH D:\\IFMXDATA\\ol_phca_oafb_ne\\phcsroot_dat.000 > ROOTOFFSET 0 # Offset of root dbspace into device > (Kbytes) > ROOTSIZE 512000 # Size of root dbspace (Kbytes)> MIRROR 0 # Mirroring flag (Yes = 1, No = 0) > MIRRORPATH # Path for device containing mirrored> root > MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> PHYSDBS physdb # Location (dbspace) of physical log > PHYSFILE 30000 # Physical log file size (Kbytes) > LOGFILES 21 # Number of logical log files > LOGSIZE 16000 # Logical log size (Kbytes)> MSGPATH C:\\Informix\\online.log # System message log file path > CONSOLE C:\\Informix\\console.log # System console message path > ALARMPROGRAM # Alarm program path > TAPEDEV \\\\.\\TAPE0 # Tape device path > TAPEBLK 16 # Tape block size (Kbytes) > TAPESIZE 9216000 # Maximum amount of data to put on tape > (Kbytes) > LTAPEDEV C:\\IFMXBKUP\\IFMXBKLG.BAK # Log tape device path > LTAPEBLK 16 # Log tape block size (Kbytes) > LTAPESIZE 9216000 # Max amount of data to put on log tape > (Kbytes)> STAGEBLOB ,1 # INFORMIX-OnLine/Optical staging area > SERVERNUM 0 # Unique id corresponding to a OnLine> instance > DBSERVERNAME ol_phca_oafb_ne # Name of default database server > DBSERVERALIASES # List of alternate dbservernames > NETTYPE soctcp,1,50,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 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 4 # Number of user (cpu) vps > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps> to one > NOAGE 0 # Process aging > AFF_SPROC 0 # Affinity start processor > AFF_NPROCS 0 # Affinity number of processors > LOCKS 10000 # Maximum number of locks > BUFFERS 20000 # Maximum number of shared buffers > NUMAIOVPS 1 # Number of IO vps > PHYSBUFF 32 # Physical log buffer size (Kbytes) > LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 30 # Maximum number of logical log files > CLEANERS 3 # Number of buffer cleaner processes > SHMBASE 0x2000000 # Shared memory base address > SHMVIRTSIZE 8192 # initial virtual shared memory segment> size > SHMADD 8192 # Size of new shared memory segments > (Kbytes) > SHMTOTAL 0 # Total shared memory (Kbytes). > 0=>unlimited > CKPTINTVL 300 # Check point interval (in sec) > LRUS 8 # Number of LRU queues > LRU_MAX_DIRTY 40 # LRU percent dirty begin cleaning limit > LRU_MIN_DIRTY 30 # LRU percent dirty end cleaning limit > LTXHWM 50 # Long transaction high water mark> percentage > LTXEHWM 60 # Long transaction high water mark > (exclusive) > TXTIMEOUT 0x12c # Transaction timeout (in sec) > STACKSIZE 32 # Stack size (Kbytes) > OFF_RECVRY_THREADS 10 # Default number of offline worker> threads > ON_RECVRY_THREADS 1 # Default number of online worker> threads > DRAUTO 0 # DR automatic switchover > DRINTERVAL 30 # DR max time between DR buffer flushes > (in sec) > DRTIMEOUT 30 # DR network timeout (in sec) > DRLOSTFOUND \\tmp # DR lost+found file path> CDR_LOGBUFFERS 2048 # size of log reading buffer pool > (Kbytes) > CDR_EVALTHREADS 1,2 # evaluator threads > (per-cpu-vp,additional) > CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds) > CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR > queue (Kbytes) > BAR_ACT_LOG C:\\Informix\\bar_act.log #Path of log file for onbar.exe > BAR_MAX_BACKUP 1 > BAR_RETRY 1 > BAR_NB_XPORT_COUNT 10 > BAR_XFER_BUF_SIZE 15 > RA_PAGES 32 # Number of pages to attempt to read> ahead > RA_THRESHOLD 28 # Number of pages left before next group > DBSPACETEMP tempdb # Default temp dbspaces > DUMPDIR \\tmp # Preserve diagnostics in this directory > DUMPSHMEM 1 # Dump a copy of shared memory > DUMPGCORE 0 # Dump a core image using 'gcore' > DUMPCORE 0 # Dump a core image (Warning:this aborts > OnLine) > DUMPCNT 1 # Number of shared memory or gcore dumps> for > FILLFACTOR 90 # Fill factor for building indexes > USEOSTIME 0 # 0: use internal time(fast), 1: get > time from OS(slow) > MAX_PDQPRIORITY 50 # Maximum allowed pdqpriority > DS_MAX_QUERIES 20 # Maximum number of decision support> queries > DS_TOTAL_MEMORY 12288 # Decision support memory (Kbytes) > DS_MAX_SCANS 1024 # Maximum number of decision support> scans > DATASKIP off # List of dbspaces to skip > OPTCOMPIND 1 # To hint the optimizer > ONDBSPACEDOWN 0 # Dbspace down option: 0 = CONTINUE, 1 = > ABORT, 2 = WAIT> LBU_PRESERVE 1 # Preserve last log for log backup > > > "Bernstein, Rick" wrote: > > > > If you supply a few more details, you might obtain meaningful assistance > > Such as: > > * Informix version > > * Server type (manufacturer and model) > > * Informix utility be used (ontape, onarchive, or onbar) > > * Storage manager, if any. > > * Type of tape device > > > > If you are using onbar, you may want to review the tips at: > > > > http://www.geocities.com/Heartland/Acres/49