Irregular backup timings
Hi All, We have Informix 11.10FC2 on SUSE linux 10. The sum of all dbspace size is around 1.2TB. We are using ONTAPE to backup the instance. Level 0 backup is taken on daily basis through cron job. Backup file is written to the file system. The cron is triggered at 22:00 hours but the end time is not fixed. Sometimes it completes at 4:00 hours and someday at 7:15 hours. I would like to know what are the factors affecting the backup timings. Also what precautions are to be taken to have consistent timings. Regards, Sushant
If the filesystem containing the archive file is busy that will slow down the archive. If the SAN structure containing the filesystem is busy that will slow the archive. If the server itself is busy then there will be more physical log records to be written to the archive at the end of each dbspace and that will affect the runtime of the archive. These are the main things to look out for. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Fri, Mar 16, 2012 at 12:49 AM, SUSHANT KODE <ksushants@gmail.com> wrote: > Hi All, > > We have Informix 11.10FC2 on SUSE linux 10. The sum of all dbspace size is > around 1.2TB. We are using ONTAPE to backup the instance. Level 0 backup is > taken on daily basis through cron job. Backup file is written to the file > system. The cron is triggered at 22:00 hours but the end time is not fixed. > Sometimes it completes at 4:00 hours and someday at 7:15 hours. > > I would like to know what are the factors affecting the backup timings. > Also > what precautions are to be taken to have consistent timings. > > Regards, > Sushant > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --047d7b10cdbb35282e04bb555551
3.5 hours is quite an increase in runtime performace, something is getting in the way obviously. (file system backkup ?) Every problem resolution needs to start somewhere and a good place to start is to grep for 'Archive on ' in the msg log and look at the time stamp for the completion times. Then try to see if you can recognize a pattern where it only happens say every nth day or certain day of the week or it only started to happen from date xxxx forward and see if you can coorelate that to a certain job that runs or whatever. Outside that tech support can offer guidance/assistance in pinpointing root cause. Mark