Re: Replicating Data Between IBM i Prod and Dev

without going to backup, for a simple set of data libraries, the Copy
Library (cpylib) command during an outage window does well.
For IFS directories, we keep a set of test directories, but the application
and website (live and test server instances) code and parameters determines
which to use. If we had been smarter, all the references to directories and
libraries could be in control files - then you could keep a test and prod
soft coded.
Jim

On Fri, Sep 27, 2024 at 4:58 PM eric bothes <iseriesstuff@xxxxxxxxx> wrote:

Rob, how to you handle IFS stuff?

On 9/27/2024 4:48 PM, Robert Rogerson wrote:

Hi Richard,

The approach taken at one customer I've worked at is that every Sunday
morning they restore all the data from the last production backup (which

is

still on site) to the development environment. This is only data libs.

Then they have programs that run that reduce/delete data that is not

really

needed in dev.
It works pretty good as often you can test/debug with data that is only a
week old in dev.

Rob

On Fri, Sep 27, 2024 at 4:35 PM Richard Schoen <

richard@xxxxxxxxxxxxxxxxx>

wrote:

HI All,

Customer wants to regularly refresh data between Production and Dev
systems. (Once every few weeks be able to refresh)

Please give me some ideas on best practices.

I can think of:
-Replication software. (Probably the MOST up to date)
-Save/restore libraries between systems with save files
-Use DDM files to move data.

Please share your strategies to keep test data relatively fresh on your
dev systems.

Thanks in advance.

Regards,
Richard Schoen
Web: http://www.richardschoen.net<http://www.richardschoen.net/>
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.