From: Jeff Miller To: All
OK, here is a backup strategy.
On Monday we do a SAVLIB on library X, which saves files A, B, C, D and E.
On Tuesday we do a SAVCHGOBJ on library X, saving files A, B and C because they were changed during the day.
On Wednesday we delete file C from the system. That night, we run another SAVCHGOBJ on library X, which saves files A and B.
Thursday morning we accidentally delete the entire library.
If I do a full restore from Monday's SAVLIB and then restore Tuesday's and Wednesday's SAVCHGOBJ, won't I end up with file C back in the library which shouldn't be there, because it was deleted? What would the proper restore strategy be?
From: James Coolbaugh To: Jeff Miller
Jeff, if you need to worry about this scenerio, you can do one of two things. First, perform a full save each day (Ouch!). Second, keep a log of all deleted objects. This second method could be a manual or automated procedure. Then as part of your disaster recovery procedures, you would check this log to see what objects were deleted and do them yourself.
From: T. Drews To: Jeff Miller
If you journal your files, the system will know of deleted files-they still need to be deleted manually, but it would eliminate the possibility of forgetting to write down the deleted file in a log. Also, you could write a little CL program to do a DSPOBJD to an outfile and check the final list of restored files against the outfile; you then delete any "extra" objects. This approach uses less system resources.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online