Re: Using BRMS for SWA and save to save file?

[CRPence <CRPbottle@xxxxxxxxx>]

lgoodbar@xxxxxxxxxxxxxx wrote:
> We are looking to reduce our daily backup time.  <<SNIP>>
>
> Our daily backups (Tuesday-Saturday morning) only save critical 
> information, including security data, config, ERP / financial
> data, in-house files, QGPL, DLO and IFS. The save takes just over
> 2 hours, 3:00am-5:09am on 9/1. On Sunday we take a full system
> backup (BRMS equivalent of Save 21), which lasts for 3.5 hours
> (2:00am-5:32am 8/30). ERP and financial data is the bulk of our
> system.
>
> <<SNIP>>

  Since "security data" and "configuration" should be part of a 
well implemented "system change management", there should be no 
reason to save all of that data each time.  Saving a\the script 
which applies those system changes would be more efficient, and 
ensuring that the run of that script is made part of the recovery. 
Such a script should already be getting run after each install 
[potentially even after PTFs, though seldom any effect].

  I would look into why QGPL and /QDLS are being saved so often; 
i.e. investigate and work to eliminate those.  Or possibly [for 
missing system change management] that the QUSRSYS is not also 
included seems suspect.  For a system using SQL, saving the database 
[physical] files in QSYS2 might be important for the database, like 
QUSRSYS might be for the system.

Regards, Chuck