|
>Ted Barry >It seems, some libraries picked up chgobj's along >the way, but some didn't. I kind of doubt it. You could probably prove it by comparing history, or backup job logs, or the actual backup content to the object change dates for dropped objects. I'd also want to check the logs for your restore processing. The only problems I've ever seen with SAVLIB and SAVCHGOBJ differential or incremental backups has been with multi-member files. In my situation it involved having members restored that were supposed to have been deleted. I have known folks who have completely screwed their differential backups by performing intermediate SAVLIB commands. This is one reason to secure the command. A friend discovered that his company's backups were swiss cheese because developers had a regular practice of performing SAVLIBs to refresh production data to test, for example. Performing SAVLIBs is easy. Designing a good backup strategy is hard work. -Jim James P. Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@xxxxxxxxxxxxxxxxx>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
