Comprehensive data protection for all workloads
Locked
Gostev
Chief Product Officer
Posts: 32217
Liked: 7583 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

[V12.2] Top Issues Tracker + Useful Tips

Post by Gostev »

Last updated:
Nov 5th @ 165K unique downloads (multiple downloads from the same account within one week are deduplicated)

Top Issues Tracker for V12.1
Top Issues Tracker for V12
Gostev
Chief Product Officer
Posts: 32217
Liked: 7583 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Tips & Tricks

Post by Gostev » 1 person likes this post

Script for automatic backup server hardening
Are you overwhelmed with the number of security hardening recommendations the new 12.2 Security & Compliance Analyzer has flagged? Implement them all quickly using the officially supported script! Please refer to the KB4525 for more information and to download the latest version of the script.

Exclude extensions from malware detection
If you get alarms about existing files with known malware extensions, however upon examination they appear to belong to legitimate line of business apps, simply exclude these extensions from suspicious file system activity monitoring. This will tune our malware engine to the unique workloads of your business and have it guard your environment from over a thousand of OTHER ransomware strains without producing false positives alerts. Note: while the attacks by malware strains using the excluded extensions will no longer be detected on the basis of file system activity, ransomware encryption activity will still be detected on excluded files by the inline entropy analysis.

Backup encryption hardening
Consider implications of recent encryption algorithm hardening on your recovery processes. Encrypted backups created by V12.1 or later builds be decrypted by V12.0 builds or any earlier product versions. For more information on the encryption hardening, please refer to the page 7 of What's New in 12.1
Gostev
Chief Product Officer
Posts: 32217
Liked: 7583 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Known Issues

Post by Gostev » 1 person likes this post

The following is the list of common V12.2 issues that have resulted in a significant number of repeating support cases.

#1: [Nutanix AHV] Backup proxy appliance is not available
Scope: Backup servers with multiple network interfaces, some of which are not reachable by the proxy appliance (including APIPA addresses)
Symptoms: After upgrading backup server to V12.2 and updating AHV backup proxy appliance, it is shown as unavailable in backup console.
Cause: Allowed maximum timeout to start the Proxy service is exceeded while connection attempts are timing out on unreachable interfaces.
Status: Hotfix is available > KB4654

#2: [Nutanix AHV] AHV Cluster rescan failures
Scope: Nutanix AHV Clusters that have storage containers with IDs higher than Int32 value (2147483647).
Symptoms: After upgrading backup server to V12.2, AHV cluster rescan fails with with the "JSON integer <integer> is too large or small for an Int32" error.
Cause: Unknown. Such high values for storage container ID were not expected because Nutanix assigns them incrementally starting from 1.
Status: Hotfix is available > KB4654

#3: [Cloud Connect] Jobs to cloud repositories start failing [FORUM TOPIC]
Scope: Veeam Cloud Connect service providers using version 12.2 + tenants using version 12.2
Symptoms: Jobs to cloud repositories may start failing with with the "There is no FIB [summary.xml] error with Veeam Cloud Connect v12.2" error.
Cause: Network connection drops between the Veeam Cloud Connect server and the cloud gateway within in the service provider’s infrastructure.
Status: Service provider should refer to the KB4655.

#4: [Cloud Connect] Upgrade of a Veeam Cloud Connect server to 12.2 is not possible
Scope: Cloud Connect servers with at least one Cloud Connect Replication failover session performed from the Veeam Service Provider console.
Symptoms: Cloud Connect server upgrade to 12.2 fails on the Configuration Check step.
Cause: The configuration check logic is not prepared for backup.model.cloudsessions table to contain NULL values
Status: Service provider should contact Customer Support for the workaround.

#5: [Proxmox] dm-integrity may detect inconsistency in restored backups
Scope: Hot Add mode backups of VM under high I/O load
Symptoms: dm-integrity tool may determine inconsistencies in the restored virtual disk.
Cause: Unexpected QEMU snapshot and CBT handling peculiarity.
Status: Hotfix is available > KB4686 and is included in the 12.2 ISO starting from version 20241031
Locked

Who is online

Users browsing this forum: No registered users and 324 guests