


Example 1
| 1. | Four backup generations |
| 2. | One Save / Data per week |
| 3. | Regular or automatic backups of the log segments (Autosave Log, AUTO-ON) between the complete backups (Save / Data). Note that Autosave Log requires a tape device of its own. |
| 4. | Save / Pages in special application situations only |

The recommended backup scheme consists of one complete backup per week (on Saturdays) and one or more log segment backups per work day. Each week, the complete backup starts a new generation of backup tapes (next letter in the alphabet). The number of generations can be defined and determines the number of weeks in this scheme to be fallen back upon in case of restore.
In Section Backup / Schedule Manager, the recommended backup scheme is represented in form of a timetable.
Example 2
| 1. | Four backup generations |
| 2. | One Save / Data per week |
| 3. | Automatic backups of the log segments (Autosave Log, AUTO-ON) between the complete backups (Save / Data). Note that Autosave Log requires a tape device of its own. |
| 4. | Save / Pages daily - preferably at the end of a work day |

The recommended backup scheme consists of one complete backup per week (on Saturdays) and one save pages per work day. Each week, the complete backup starts a new generation of backup tapes (next letter in the alphabet). The automatic backup of log segments is entered once in this example in order to be complete. As the automatic backup only takes place once, it can be enabled interactively or entered once in the schedule (see Section Backup / Schedule Manager).
Save pages is recommended in addition to save log segment, because, in most cases, it ensures considerably faster recovery times than save log segment.


