On Tue, Apr 22, 2008 at 7:48 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:
> For example, our software uses journalling and commitment control.
> This requires some special considerations when backing up data.
What's wrong with "GO SAVE 21" or "SAVCHGOBJ *ALL *ALLUSR SAVACT(*LIB)"?

The Save 21 will of course work, but it will bring downtime. The
SAVACT(*LIB) might make your application data inconsistent, some
transactions might span multiple libraries - *SYNCLIB is required.

Add to that the journal switchover that Evan already mentioned and you
might see why not everything is as clear cut as it might seem on the
first look.

Our software also abstracts several restore procedures to make it
easier for end users to use them (we have many small businesses as
customers with no technical personnel). For this, extra metadata needs
to be saved on the tape.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.