Lotus Domino Incremental restore fails - Will NOT Recover Database 'xxx.nsf'. File does not exist (4033966)

Lotus Domino Incremental restore fails - Will NOT Recover Database 'xxx.nsf'. File does not exist

Following a successful Lotus Domino Full backup, a new database is created.
Several successful incremental backups of the Domino server are taken after that.

A restore is needed, therefore the Full backup is restored first without recovery options, followed by a restore of all incrementals with the last one performing the recovery.
While performing the recovery, the following error messages are returned in the NetVault logs regarding the newly created database:

--------------------
Failed to apply change info. Will NOT Recover Database 'd:\BkBtmp\Lotus\Domino\data\mail\fldr\cob3.nsf'. File does not exist
Wait for recover process to complete. Database(s) are being recovered.
Recover process error. Database 'd:\BkBtmp\Lotus\Domino\data\mail\fldr\cob3.nsf'
Failed to Recover [d:\BkBtmp\Lotus\Domino\data\mail\fldr\cob3.nsf] for database d:\BkBtmp\Lotus\Domino\data\mail\fldr\cob3.nsf.
Failed to bring online the database 'd:\BkBtmp\Lotus\Domino\data\mail\fldr\cob3.nsf'. File does not exist
Failed to RollForward databases.
Move File From: 'd:\BkBtmp\Lotus\Domino\data\mail\fldr\cob3.nsf' To 'd:\Lotus\Restore\cob3.nsf'.
Cannot access the specified relocate location: 'd:\Lotus\Restore\cob3.nsf'
--------------------

The described behaviour is expected and it is important to understand what each backup method does.
- A FULL backup will backup the database files *.nsf and the logs needed to recover them at the point in time of the backup
- INCREMENTAL backups will ONLY backup archived transaction logs (and no database files).
Because the only backup run after the creation of "cob3.nsf" was an INCREMENTAL, the actual database file was never backed up.
So it is good practice to often run FULLs, especially immediately after creating new databases.

To protect and save copies of your database files, run regular FULL backups.
The FULL backup method should be used anytime a new database is created or when the DBIID for a database has changed.
To keep changes that occurred to the database files, run regular INCREMENTAL backups between the FULL backups.