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

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>]

Diana,

If your Option 21 saves are taking the same time as they did prior to
your upgrade, then you can probably eliminate hardware problems, damaged
objects, and probably command default changes from your list of
possibilities.

Here are some thoughts:

- You may, as a result of the upgrade (or just coincidentally) have some
jobs active which were not previously present.  This could be system
stuff or user jobs.  This would lead to object locks which could take the
extra time to resolve.  You could research this by tracking down the
program (QEZBACKUP?) and changing its logging characteristics so that you
have a detailed log.  This would also allow you to determine which class
of objects is taking longer.  Alternatively, you could display the object
descriptions of the various libraries and folders and see if you have
objects which were not saved (check the last saved date) as a result of
locks.

- It's also possible that the system characteristics have changed so that
you have less memory available when your backup occurs.  This doesn't
seem likely given the drastic increase in execution time.

Regards,
Andy Nolen-Parkhouse

> bounces@xxxxxxxxxxxx] On Behalf Of Diana Hicks
> 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