|
OS/400 does provide Save_While_Active functionality. However, I
highly recommend from a usability point of view, that you quiesce the
system for a few minutes in order to obtain a synchronization point.
On my system this results in the application being unavailable to my
users for about 15 minutes whenever I run a backup. If you are unable
to take the system away from users for even this brief amount of
time, you will probably need to consider mirroring your system using one of
the high availability vendors like Mimix or Data Mirror.
If you are able to take a few minutes to quiesce the system, then the
Save_While_Active (SWA) feature of OS/400 could be just what you are looking
for.
Some reasons to consider...
1. SWA is a wonderful tool. It is a bit complicated to configure but well
worth the trouble.
2. You could configure your backup process to eliminate ALL downtime, but in my opinion. It isn't worth the effort.
3. Quiesce your system for a short time instead, in order to obtain a
synchronization point.
4. In the event of a recovery, you will be able to recover data to the time
of this synchronization point.
5. You can NOT use SWA for SAVSYS. To execute a SAVSYS command still
requires that the system be in a restrictive state.
6. As with any backup, run it during a time of light system use.
7. Because of the extra processing required for SWA processing your backup
will run longer, but users can use the system while it is running.
6. Full implementation details can be found in the OS/400 Backup and
Recovery Manual, SC41-5304. ==================================
MORE INFORMATION ON THIS TOPIC
==================================
Ask the Experts yourself: Our Backup & Recovery gurus are waiting to answer your questions.
Search400's targeted search engine: Get relevant information on backup & recovery.
Check out this search400 Featured Topic on backup & Recovery.
|
