Starting with MaxBack VSS Writer 3.x:
The steps descripted below are no longer necessary with MaxBack VSS Writer 3.0 or higher. The necessary reset of the log volumes is done automatically. Use the Session Logviewer to check the progress of the restore after the system is started and if it is ready for further log recoveries or start.
For previous Releases:
For backup solutions that restore entire Virtual Machines (for example with Veeam) or a bare-metal restore you should keep in mind that the log volumes of the MaxDb database will also be restored.
In this case you should make sure that the log volumes are cleared before a restore. If not, the database may not apply all transactions from the log media, resulting in an incomplete point-in-time recovery.
To clear the log volume open the database studio or a database command line after the restore. Then make sure that the database is correctly restored:
- The database should be allready in the status "admin".
- Make sure that there is a recovery log entry in the backup history
When restore was successful you can new execute the following database command:
util_execute clear log
The command will take some time. When the commend is completed you will see a "history lost" entry in backup history. You can now apply the log files from you log media backups.