RE: Nightly backup takes longer after upgrade from V4R5 to V5R1

After comparing history logs from before and after the upgrade as well as 
generating a joblog, I found that QMPGDATA, QRCL, QUSRDIRDB and SYSIBM were 
added to the V5R1 all user libraries from go backup (runbckup).  The backup 
increase was caused mostly from the QMPGDATA library.  Many allocation errors 
were occuring from the PM/400 collection job while the backup was trying to 
save QMPGDATA.  To eliminate this, I have to change go backup option to select 
libraries from a list which doesn't include QMPGDATA or follow the instructions 
on 
http://www-1.ibm.com/servers/eserver/iseries/pm/existing_customers/datacoll.htm 
.

Thanks for all the suggestions that were submitted.

>  -----Original Message-----
> From:         Diana Hicks  
> Sent: Tuesday, March 04, 2003 9:54 AM
> To:   'Midrange-L submission'
> Subject:      Nightly backup takes longer after upgrade from V4R5 to V5R1
> 
> We upgraded our 170 from V4R5 to V5R1 a couple weekends ago.  Since then, our 
> daily backup is taking 2 hours when it used to take only 1 hour.  We have a 
> 13GB 1/4" 6385 tape drive and use the backup scheduler (RUNBCKUP from GO 
> BACKUP) to save all user libraries, all folders, all user directories, 
> security data and configuration.  At least once a month, we perform an option 
> 21 to save entire system.  The save entire system backup time (2 hours) did 
> not increase.  We applied all the cumulative, database (on the group CDs) and 
> hiper PTFs.  Our current total disk usage is 15 GB which is about the same as 
> it was before the upgrade and cleanup.  Any ideas on what has happened and 
> how we can fix it.  Thank you for any help you can provide.
>  
> Diana Hicks
> Town of Jupiter
> IBM Certified Specialist-AS/400 RPG IV Programmer
> IBM Certified Specialist-AS/400 System Administrator
> 


Please visit the Town of Jupiter online at http://www.jupiter.fl.us