- SVP, Product Management
- Posts: 28236
- Liked: 5012 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
This topic contains top version 10 issues based on the number of support cases or their criticality.
Version 10a is now available that includes fixes for most of them> KB3228
#1: Empty UI
Symptoms: Veeam console may not show any content in a number of management tree nodes when you launch it after upgrading to v10.
Cause: Upon the first execution of any new SQL query, SQL Server creates so-called "execution plan" to ensure it's optimal execution going forward. Since following the upgrade, many new SQL queries will run for the first time, creating execution plans for all of them may take up to 10-20 minutes depending on SQL Server performance. Until that happens, certain UI nodes will remain empty.
Status: No action is required, as the issue will fix itself in a few minutes. You don't even have to restart the backup console, just press F5.
#2: Scheduled jobs are not running
Symptoms: Scheduled jobs are not running after upgrading to v10.
Cause: v10 stores time in the new format (UTC), so following the upgrade those in GMT-negative time zones "end up in the past" for a few hours, with their jobs waiting for the Next Run time.
Status: No action is required, the issue will fix itself after a few hours, once you "catch up" with the GMT time difference.
#3: Upgrade date/time conversion error
Symptoms: Upgrade to v10 fails with the "The conversion of a nvchar data type to a datetime data type resulted in a out-of-range value" error.
Cause: For unknown reasons, a number of customers have their job schedules contain 01/01/0001 00:00:00 values, which the upgrade script fails to convert to UTC.
Status: Contact our customer support for assistance with correcting the invalid configuration database values.
#4: Hyper-V with SCVMM
Symptoms: Backup jobs may fail in some environments with the "Object reference not set to an instance of an object" error.
Cause: This issue affects environments where at least one virtual machine is stored in the SCVMM Library.
#5: SureBackup with advanced multi-host virtual labs
Symptoms: SureBackup jobs using advanced multi-host virtual labs fail with the "Invalid configuration for device " error.
Cause: v10 regression with VMware DVS support.
#6: SureBackup log export
Symptoms: Exporting logs for a SureBackup job that includes an Application Group fails with the "Object was not found" error.
Cause: v10 regression.
#7: Capacity Tier copy policy uploads full backups periodically
Symptoms: Copy policy uploads full backups to object storage periodically, instead of copying changes only. Newly uploaded data overwrites the existing data, so there's no extra storage usage.
Cause: Copy policy bug with backup file chains without periodic fulls (forever-forward incremental and forever-reverse incremental).
#8: NAS backup from VSS snapshot
Symptoms: Backup from VSS snapshot fails with the "Failed to create a VSS snapshot" for file shares hosted on NAS devices (but not on Windows servers).
Cause: VeeamFilesysVssSvc service runs under LOCAL SYSTEM context, and lacks impersonation when interacting with NAS devices.
#9: NAS backup instance consumption
Symptoms: Instance consumption is doubled for the protected file share.
Cause: NAS backup copy job erroneously consumes instances.
#10: vCloud Director registration
Symptoms: Adding vCloud Director to managed servers fails with the "Failed to get certificate" error.
Cause: In v10, the backup server tries to retrieve certificates from each cell. If the backup server can connect only to a load balancer, but not to actual vCD cells, then registration is not possible.