|
An enhancement has been made to the incremental save support of Domino databases on iSeries to do the following:
- detect when a new database has been added to the server since the last *FULL save of the Domino server
- detect if the DBIID of a database has changed since the last FULL save of that database
- detect if a non-logged Domino database has changed since the last FULL save of that database
If any of the above conditions are found for a Domino database, then an online FULL save of just that database will be done. Here are some details about the implementation:
Whenever a *FULL save request of the Domino server is requested, and archival style logging is enabled on the server, additional information will be saved about each of the Domino databases. If a *FULL save request of the Domino server is requested, and archival style logging is NOT enabled on the server, then no additional information will be collected. Archival style logging must be enabled on the server to be able to perform the incremental save request. All of the following discussions relating to *INCR save requests assume that archival style logging is enabled for the server.
On an *INCR save request of the Domino server, the DBIID information saved on the *FULL save request is compared against the current DBIID data. If the DBIID has changed, or we don't currently have any information saved about this database (which means it is a new database), an online FULL save is performed on just this database. The extra information saved about this database is updated at this time. If for any reason information about the current database could not be retrieved, or the saved information about the database could not be retrieved, the worst is assumed and a FULL save of that database will be performed. This particular situation is not expected to occur (where the data can not be retrieved), but if such a thing were to happen, it was important to make the attempt to save the customer's data. A message will be issued to the joblog when a Full save of a database is needed during the *INCR save request and the reason for the Full save of that database.
On an *INCR save request of a Domino server, if a database is not currently transaction logged, because either it was explicitly removed from the logging, or the database is an older release database and not valid for logging, and the data or non-data Timestamp of the database indicates the database has changed since the last *FULL save of the server, this database will also be saved with an online Full save of just this database. This is expected to be a rare occurrence, but it does catch database changes to non-logged databases, and perform the save as soon as a change can be detected. An example may be helpful here to explain this more fully. If a *FULL save of the Domino server is done every Saturday night, with nightly *INCR backups, and a non-logged database was changed Wednesday morning, a Full save of just that database will occur on the Wednesday evening *INCR save request. If the non-logged database changes weren't saved as soon as possible, the user would have to wait until next Saturday's *FULL save of the server to get the changes saved to non-logged databases. This should reduce the exposure of changes made to non-logged databases and something serious happening to the database before the next scheduled *FULL save of the Domino server.
Once Domino 6.0.3 (or 6.50) and the corresponding BRMS changes are loaded onto the system (SI10612 (V5R1 PTF)/SI10615(V5R2) PTF) , a *FULL save of the Domino server should be done. If an *INCR is the first save done, instead of a *FULL of the Domino server, all of the databases will look like new databases to this support and will force a *FULL save of the Domino server. Domino 6.0.3/6.50, with this enhancement, can be installed without the BRMS changes installed and no need to schedule a *FULL save of the Domino server at that time. It isn't until the BRMS changes are installed, that have additional changes supporting this incremental enhancement, that a *FULL save of the Domino server should be done, OR if not scheduling a *Full save of the Domino server, that enough time is allowed for a *FULL save of the Domino server to occur during the next scheduled *INCR save request. Without the BRMS changes installed, none of the *INCR save processing described in the preceding paragraphs will occur. It takes a combination of Domino 6.0.3/6.50 and the corresponding BRMS changes to fully implement this enhancement.
| 
