Title: Lotus Notes Attempt to recover a db that was not created with a backup utility Error
NV Version: 7.4.x
OS Version: Any
Application version: Lotus Notes 6.5
Plugin version: 3.1.x
Description: Explanation and resolution for "Attempt to recover a db that was not created with a backup utility" Error during Netvault Backup Lotus Notes Restore.
When restoring a Lotus Notes database, when the "Last Backup Set" option is selected and the database attempts to roll forward the database, the following error messages are seen in the binary log:
Job Message 2007/03/26 09:08:21 42 Data Plugin ln02 Wait for recover process to complete. Database(s) are being recovered.
Warning 2007/03/26 09:08:21 42 Data Plugin ln02 Attempt to recover a db that was not created with a backup utility. Database 'C:\Lotus\Domino\Data\kj1.nsf'
Warning 2007/03/26 09:08:21 42 Data Plugin ln02 Failed to Recover [C:\Lotus\Domino\Data\kj1.nsf] for database C:\Lotus\Domino\Data\kj1.nsf. Recovery Manager: Recovery only supported for Backup Files.
Job Message 2007/03/26 09:08:21 42 Data Plugin ln02 Bring online database 'C:\Lotus\Domino\Data\kj1.nsf'.
Warning 2007/03/26 09:08:21 42 Data Plugin ln02 Failed to RollForward databases.
Earlier binary logs show that the .nsf file has been successfully backed up using Netvault.
This error occurs where a .nsf file is being restored to a live location in situ. What has happened in these cases is that the DBIID of the original live database has been changed (for example by a compact command) and the restore APM does not recognise the database that is being restored.
In order to get around this problem, use the rename function in the restore to give the database being restored a new .nsf filename (the "data/" prefix and the ".nsf" extension are not required as these are added automatically), this step is required for each of the sub restores.
On the last restore, when selecting "Last Backup Set", also select "Give New DBIID to database" and (if this is a replicated database) "Assign New Replica ID". This will ensure that the restored database is rolled forward using the associated transaction logs, then allocated a new DBIID, which will result in a new copy of the live database with a different filename (but the same database title). Documents can then be copied from this database to the desired target.