Re: Backup sanity check

If yer backin' up stuff why go granular? If someone creates a new source file for example for includes only then oops, missed that.

Start with the security data for that system, small and important, also config. Then save the entire source libraries and object libraries too. Also working libraries for developers (they hit sh** in there!) and DON'T FORGET the IFS with todays systems and many web services running that's where much of that lives.

If you only have one tape library/drive then you won't impact a restore by having all this stuff on one tape.

Oh and PLEASE do get a SAVE 21 on that thing SOON and then at least every time you do PTFs or every 6 months whichever comes first!!


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 1/19/2016 8:37 AM, Richard Reeve wrote:

All,

I recently took on a new client that is not backing up the test LPAR
at all. Really, the data isn't important, but the programs and source
files are.

The production LPAR is backed up nightly using SAVLIB to tape. My
thought was to change ENDOPT to *LEAVE for he last production library that
is saved. Then just vary off the tape drive from the production LPAR,
vary the tape drive on in the TEST LPAR, then use SAVOBJ to save the
individual source files from test to the end of the production backup.

Does this sound like a good practice or does some one have a better
idea?

As always thanks for all of you knowledge and wisdom.

Rich