Restrictions
  1. Some Lotus® server databases are not valid for transaction logging. This can happen if the database is defined as an older database structure or the database has been explicitly removed from the list of databases being logged. If a database is not being logged, then an incremental backup will not be able to save the changes for this database and a point-in-time recovery will not be valid. To determine if you have any databases which are not transaction logged, do the following:
    Note:
    When changes do occur to these non-logged databases, and an incremental backup is requested, a full online backup will be performed on the changed, non-logged databases.
  2. The value of the Incremental type prompt on the attributes of backup control groups used for incremental online backup support is ignored. A value of *CUML or *INCR produces the same results.
  3. If a backup control group is set up to run an incremental online backup and BRMS detects that no prior full backup exists, BRMS will perform an full online backup instead of an incremental online backup.
  4. You must use the same type of media for the incremental online backup that you use for the full online backup. If the full online backup goes to tape media, the incremental online backup cannot go to save files or to a Tivoli® Storage Manager (TSM) server. BRMS recommends you use the same media policy for the Media policy for full backups and Media Policy for incremental backups attributes of the backup control groups used for incremental online backups to assure the same media types and retentions.
  5. You are limited to 97 incremental online backups of a Lotus server. Before you perform an incremental backup, you must perform a full online backup. BRMS recommends that you perform a full online backup of your Lotus servers at least once a week.


[ Top of Page | Previous Page | Next Page | Contents | Index ]