I wish it were that simple.  :)   We actually do a full every night for
this set of databases. 

Some questions the vendor asked...

"You have 4 threads starting at the same time, one for each dbs which is
fine.  Could there be there another Tivoli process on the 8th day that
may be using 5 threads?  Tivoli can only handle 8 threads at a time,
causing the last worx thread to wait until the other processes complete.

 
What we see on the 12th is a delay of 2 seconds where Tivoli does
nothing, it is waiting on something.  
The 4 processes are forked at the same time each day -
Tivoli should begin the 4 backups immediately in sequence, but it does
not.
Tivoli completes the 1st backup, then waits 2 seconds and begins the
other 3 backups."

The bar_act.log for an example of a 'normal' backup...

2006-04-17 00:55:40 22260  23824 /digi/informix/bin/onbar_d -b
 2006-04-17 00:55:43 22260  23824 Begin level 0 backup rootdbs.
 2006-04-17 00:55:43 22260  23824 Successfully connected to Storage
Manager.
 2006-04-17 00:55:44 22260  23824 Completed level 0 backup rootdbs.
 2006-04-17 00:55:46 35386  22260 Process 35386  22260 successfully
forked.
 2006-04-17 00:55:46 35002  22260 Process 35002  22260 successfully
forked.
 2006-04-17 00:55:47 35386  22260 Begin level 0 backup phys_dbs.
 2006-04-17 00:55:47 33858  22260 Process 33858  22260 successfully
forked.
 2006-04-17 00:55:47 35386  22260 Successfully connected to Storage
Manager.
 2006-04-17 00:55:47 35386  22260 Completed level 0 backup phys_dbs.
 2006-04-17 00:55:47 19004  22260 Process 19004  22260 successfully
forked.
 2006-04-17 00:55:48 35002  22260 Begin level 0 backup logs_dbs.
 2006-04-17 00:55:48 35002  22260 Successfully connected to Storage
Manager.
 2006-04-17 00:55:48 35002  22260 Completed level 0 backup logs_dbs.
 2006-04-17 00:55:49 33858  22260 Begin level 0 backup prod_dbs.
 2006-04-17 00:55:49 33858  22260 Successfully connected to Storage
Manager.
 2006-04-17 00:55:50 19004  22260 Begin level 0 backup test_dbs.
 2006-04-17 00:55:50 19004  22260 Successfully connected to Storage
Manager.
 2006-04-17 00:55:50 35002  22260 Process 35002  22260 completed.
 2006-04-17 00:55:50 35386  22260 Process 35386  22260 completed.
 2006-04-17 01:16:14 19004  22260 Completed level 0 backup test_dbs.
 2006-04-17 01:16:15 19004  22260 Process 19004  22260 completed.
 2006-04-17 01:50:00 24852  35424 /digi/informix/bin/onbar_d -l
 2006-04-17 01:50:01 24852  35424 Begin backup logical log 10953.
 2006-04-17 01:50:01 24852  35424 Successfully connected to Storage
Manager.
 2006-04-17 01:50:07 24852  35424 Completed backup logical log 10953.
 2006-04-17 01:50:07 24852  35424 /digi/informix/bin/onbar_d: process
exit 0 (0x
00)
 2006-04-17 01:52:14 33858  22260 Completed level 0 backup prod_dbs.
 2006-04-17 01:52:15 33858  22260 Process 33858  22260 completed.
 2006-04-17 01:52:15 22260  23824 Begin backup logical log 10954.
 2006-04-17 01:52:16 22260  23824 Successfully connected to Storage
Manager.
 2006-04-17 01:52:16 35446  19126 /digi/informix/bin/onbar_d -l
 2006-04-17 01:52:16 22260  23824 Completed backup logical log 10954.
 2006-04-17 01:52:16 22260  23824 /digi/informix/bin/onbar_d: process
exit 0 (0x
00)
 2006-04-17 01:52:16 35446  19126 /digi/informix/bin/onbar_d: process
exit 0 (0x
00)

For an abnormal backup...

2006-04-12 00:56:03 19658  34038 /digi/informix/bin/onbar_d -b
 2006-04-12 00:56:06 19658  34038 Begin level 0 backup rootdbs.
 2006-04-12 00:56:07 19658  34038 Successfully connected to Storage
Manager.
 2006-04-12 00:56:09 19658  34038 Completed level 0 backup rootdbs.
 2006-04-12 00:56:14 18354  19658 Process 18354  19658 successfully
forked.
 2006-04-12 00:56:14 21288  19658 Process 21288  19658 successfully
forked.
 2006-04-12 00:56:14 34224  19658 Process 34224  19658 successfully
forked.
 2006-04-12 00:56:14 35060  19658 Process 35060  19658 successfully
forked.
 2006-04-12 00:56:15 18354  19658 Begin level 0 backup logs_dbs.
 2006-04-12 00:56:15 18354  19658 Successfully connected to Storage
Manager.
 2006-04-12 00:56:15 18354  19658 Completed level 0 backup logs_dbs.
 2006-04-12 00:56:17 35060  19658 Begin level 0 backup phys_dbs.
 2006-04-12 00:56:17 21288  19658 Begin level 0 backup prod_dbs.
 2006-04-12 00:56:17 34224  19658 Begin level 0 backup test_dbs.
 2006-04-12 00:56:17 21288  19658 Successfully connected to Storage
Manager.
 2006-04-12 00:56:17 35060  19658 Successfully connected to Storage
Manager.
 2006-04-12 00:56:17 34224  19658 Successfully connected to Storage
Manager.
 2006-04-12 00:56:17 18354  19658 Process 18354  19658 completed.
 2006-04-12 00:56:17 35060  19658 Completed level 0 backup phys_dbs.
 2006-04-12 00:56:17 35060  19658 Process 35060  19658 completed.
 2006-04-12 00:56:59 16888  18364 /digi/informix/bin/onbar_d -l
 2006-04-12 00:57:00 16888  18364 Begin backup logical log 10863.
 2006-04-12 00:57:00 16888  18364 Successfully connected to Storage
Manager.
 2006-04-12 00:57:10 16888  18364 Completed backup logical log 10863.
 2006-04-12 00:57:10 16888  18364 /digi/informix/bin/onbar_d: process
exit 0 (0x
00)
 2006-04-12 01:22:44 34224  19658 Completed level 0 backup test_dbs.
 2006-04-12 01:22:47 34224  19658 Process 34224  19658 completed.
 2006-04-12 02:19:50 34250  23246 /digi/informix/bin/onbar_d -l
 2006-04-12 02:19:50 34250  23246 Begin backup logical log 10864.
 2006-04-12 02:19:50 34250  23246 Successfully connected to Storage
Manager.
 2006-04-12 02:19:56 34250  23246 Completed backup logical log 10864.
 2006-04-12 02:19:56 34250  23246 /digi/informix/bin/onbar_d: process
exit 0 (0x
00)
 2006-04-12 04:11:26 21288  19658 Completed level 0 backup prod_dbs.
 2006-04-12 04:11:27 21288  19658 Process 21288  19658 completed.
 2006-04-12 04:11:27 19658  34038 Begin backup logical log 10865.
 2006-04-12 04:11:27 19658  34038 Successfully connected to Storage
Manager.
 2006-04-12 04:11:28 19194  11898 /digi/informix/bin/onbar_d -l
 2006-04-12 04:11:29 19194  11898 WARNING: A log backup is already
running. Can'
t start another.
 2006-04-12 04:11:32 19658  34038 Completed backup logical log 10865.
 2006-04-12 04:11:32 19658  34038 /digi/informix/bin/onbar_d: process
exit 0 (0x
00)
 2006-04-12 04:11:34 19194  11898 /digi/informix/bin/onbar_d: process
exit 152 (
0x98)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Alexander Verkooijen
Sent: Tuesday, April 18, 2006 4:34 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Slow Informix backups every 8 days?

I do not claim to have any knowledge of Informix
but the behaviour you describe suggests that
you use a backup schema of a full backup every
8 days and incrementals/differentials on the
other 7 days.

Just guessing...

Regards,

Alexander

------------------------------------------------------------
Alexander Verkooijen
Senior Systems Programmer
High Performance Computing
SARA Computing & Networking Services
 

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 
> On Behalf Of Bell, Charles (Chip)
> Sent: maandag 17 april 2006 16:45
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Slow Informix backups every 8 days?
> 
> Client OS AIX 4.3.3
> 
> Informix Dynamic Server Version 7.31.UD4
> 
> TDP for Informix v4.1.3 TSM v5.1.5
> 
>  
> 
> Why would the client back up in a way that is considered normal (45
> mins. to 1 hr), but every 8th day take well over 3 hrs? Has 
> anyone seen
> this happen every 'x'th day at their site?
> 
>  
> 
> God bless you!!! 
> 
> Chip Bell 
> Network Engineer I
> IBM Tivoli Certified Deployment Professional (ITSM 5.2)
> Baptist Health System 
> Birmingham, AL 
> Office (205) 715-5106 
> Pager (205) 817-0357 
> Home (256) 739-0947 
> 
>  
> 
> 
> 
> 
> -----------------------------------------
> Confidentiality Notice:
> The information contained in this email message is privileged and
> confidential information and intended only for the use of the
> individual or entity named in the address. If you are not the
> intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this information is strictly
> prohibited. If you received this information in error, please
> notify the sender and delete this information from your computer
> and retain no copies of any of this information.
> 
> 

-----------------------------------------
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly
prohibited. If you received this information in error, please
notify the sender and delete this information from your computer
and retain no copies of any of this information.