Help: Urbackup not truncating exchange transaction log files?

client
1

Sorry if it has been covered… tried searching through the forums…

But installed urbackup client unto a freshly installed SBS 2011 in VM for testing the software. I’m probably missing something but it does not seem to truncate the log files after backup?

in need of help. thanks.

2015-05-20 07:41:57: WARNING: Upgrading…
2015-05-20 07:41:57: ERROR: Error preparing Query [SELECT tvalue FROM misc WHERE tkey=‘db_version’]: no such table: misc
2015-05-20 07:41:57: ERROR: Error preparing Query [DROP INDEX filehashes_idx]: no such index: filehashes_idx
2015-05-20 08:00:14: WARNING: Snapshotting failed because of Writer. Retrying in 30s…
2015-05-20 08:01:07: WARNING: Snapshotting failed because of Writer. Retrying in 30s…
2015-05-20 08:02:35: WARNING: Writer Microsoft Exchange Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_RETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
2015-05-20 08:02:36: WARNING: Writer is in error state during snapshot creation. Writer data may not be consistent. This means the files open by this application (e.g. databases) will be backed up in a crash consistent state instead of a properly shutdown state. Properly written applications can recover from system crashes or power failures.
2015-05-20 08:19:36: WARNING: Writer Microsoft Exchange Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_RETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
2015-05-20 08:28:16: WARNING: Snapshotting failed because of Writer. Retrying in 30s…
2015-05-20 08:28:58: WARNING: Snapshotting failed because of Writer. Retrying in 30s…
2015-05-20 08:29:39: WARNING: Writer Microsoft Exchange Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_RETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
2015-05-20 08:29:39: WARNING: Writer is in error state during snapshot creation. Writer data may not be consistent. This means the files open by this application (e.g. databases) will be backed up in a crash consistent state instead of a properly shutdown state. Properly written applications can recover from system crashes or power failures.
2015-05-20 08:55:24: WARNING: Writer Microsoft Exchange Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_RETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
2015-05-22 02:15:49: WARNING: Snapshotting failed because of Writer. Retrying in 30s…
2015-05-22 02:16:32: WARNING: Snapshotting failed because of Writer. Retrying in 30s…
2015-05-22 02:17:12: WARNING: Writer Microsoft Exchange Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_RETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
2015-05-22 02:17:13: WARNING: Writer is in error state during snapshot creation. Writer data may not be consistent. This means the files open by this application (e.g. databases) will be backed up in a crash consistent state instead of a properly shutdown state. Properly written applications can recover from system crashes or power failures.
2015-05-22 02:43:20: WARNING: Writer Microsoft Exchange Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_RETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.

2

Did not come up yet. The Volume Shadow Copy API has two modes. The component selection mode, where you have to select which individual components you want to backup and the whole drive backup mode. UrBackup uses the last one, which causes Exchange versions to have errors (you can look into the system error log for that).
The backups are still good, if maybe only crash consistent (as the warning message says).

You should enable circular logging to not get the accumulation of log data in the first place.

If you put the logs on a different drive you should not use UrBackup to backup exchange, as it does shadow copy one drive at a time, so the logs won’t be consistent with the main dabatase file.