|
There are commands in TAA Tool to facilitate this. The SAVALLCHG command is a slightly better implementation of SAVCHGOBJ. However the system provides no way to restore changes. However the is a RSTALLCHG tool that will do this for you. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com oliver.wenzel@cibavision.no vartis.com To: midrange-l@midrange.com Sent by: cc: midrange-l-admin@midrange.c Subject: AW: APYJRNCHG om 08/22/01 03:03 AM Please respond to midrange-l Hello, we are also looking at journalling to reduce downtime. We do a complete backup (w/o savsys and not in restricted state) each night, but when the crash happens during the day, we'd loose that daily data. We had to do a complete system reload two weeks ago, and only restoring the data (100GB) took 12 hours. I'd guess that a reload from savchgobj would take a lot longer? Anyhow, you'll need a good recovery plan if you go with savchgobj. Regards, Oliver > -----Ursprüngliche Nachricht----- > Von: Jim.Nelson@RCIS-NET.COM [SMTP:Jim.Nelson@RCIS-NET.COM] > Gesendet am: Dienstag, 21. August 2001 23:31 > An: midrange-l@midrange.com > Betreff: APYJRNCHG > > > We are looking at shortening our backup downtime by going with SAVCHGOBJ. > Only problem is that we journal most of our files, which means we would > need > to restore from the SAVEALL, then run APYJRNCHG for the daily saves. The > documentation says to expect a longer recovery time, but no estimates. > > During our 'busy time', we create about 300,000 journal entries per day - > tables ranging from 150 bytes to over 800. > > 1. Anybody have estimates (or an algorithm) on what the recovery time > would > be? Looking more for those occasional 'restore to a temporary library to > check data' rather than a complete recovery. If we ever need a reload, a > few hours here or there will be the least of my worries! > > 2. Any 'tricks' or items to watch for using SAVCHGOBJ and APYJRNCHG? > Horror stories? > > Thanks for your help. > > JN > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com
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.