Today we released release 2.1 for the MaxBack VSS Writer.
The following issues have been fixed:
- possible corruption of the backup history after restore
After the restore, the backup history cannot be read because the files dbm.knl or dbm.mdf are not readable as described in SAP Note 524132.
The suspected cause is a delay between the response of the backup commands and the actual writing of the files. This causes the snapshot to be created too early.
As of this patch, the snapshot is delayed until the files in the backup history are complete.
- unnecessary conversion of the log volume name when connecting
When the database is connected, the log volume name entered is converted to uppercase. This mistakenly causes volume names with lowercase letters not to be accepted.
- new option ignoreComponentModeBackupResult
This option has been introduced as workaround for a issue with Backup on HyperV Windows Server 2016. This option should only be used if our support advises this.