Community

With Microsoft releasing Windows Server 2022, Veeam have delivered support for this in Veeam B&R and Veeam ONE v11a. This includes support not just for protecting Hyper-V VMs on the OS, or guest OS support, but also running all the relevant Veeam Components and services on Windows Server 2022. This is truly a great milestone that Veeam have achieved so promptly after the release of this operating system.There’s more to this story however, Veeam currently ships with SQL Server 2016 Express edition as its default database if you don’t choose to install your own first. This will leave you in an unsupported state with Microsoft as only SQL Server editions still within mainstream support are supported for Windows Server 2022,

One of the biggest mysteries of Veeam’s list of features in my opinion is the Backup Copy Job. On the surface, they’re easy to understand – you create a Copy Job, use some supported backup source, and copy this source VM data to a designated target to implement part of the 3-2-1(-1-0) Rule – have multiple copies of your data and/or at least 1 offsite copy of your data. Easy, right? Well, when you look under the hood of the technology behind the retention, scheduling, interval, etc. things start to get murky pretty quick, at least for me. The most difficult to understand about Copy Jobs in my opinion is how the retention algorithm works when using the GFS (grandfather-father-son) archive option. And with the changes brought to Copy Jobs with the release of Veeam v11, I believe things got worse instead of better. As such, I thought it would be beneficial to the Veeam Community for me to go through the Backup Copy process from a deep-dive perspective, and see if I can make a bit more c

Hi Team,can someone please help to resolve below issue.i started a backup copy job.the backup copy job replicates data from HPE storeonce Azure cloudbank repository to Azure based storeonce VSA, this is first time we configured this.actual data backup traffic path is given below,physical storeonce catalyst -> storeonce cloudbank in Azure -> VSA catalyst store.on-prem proxy servers and storeonce connected via FC cable and Veeam servers is also running as a VM in Azure.we observed this error during copy job of storeonce cloudbank in Azure -> VSA catalyst store.please help to know possible reasons for this error and how we can mitigate this.we also see below errors on this same copy job,[Error] Creating new metadata file Error: Failed to call RPC function 'PluginsHost.StoreOnceFastMoveFile': TryPopById Pipe message queue was canceled.[Error] Error: Failed to

Happy New Year Community!Has anyone who’s upgraded VBR to v12.1… have there been any notable issues reported? I know with the upgrade, which supports upgrade of vSphere to 8U2, there is a CBT bug within vSphere when upgrading VM disks. That isn’t a Veeam issue though...rather a VMware issue. Simple fix for that is simply don’t upgrade vSphere to 8U2. 🙂 Other than that, has there been anything discussed ‘in the wild’ as it were on upgrade issues I have not yet heard about? I’d like to upgrade, but want to make sure there’s no egregious bugs before doing so. Cheers all.

"We're researching and doing some prototyping around Proxmox to see what's possible there as far as backup goes," Anton Gostev, Veeam's senior veep for product management posted on January 11.Another Veeam product manager, Fabian Kessler, last week confirmed that effort, writing "Proxmox is something we are doing some early research on." As found on Reddit/The Register

Hi Guys,  I am new to Veeam and i really want this to work cuase i really like Graphical interface and method of doing this. But i have made several attempts and recreated a new repository and backup jon and every time i backup to my nas through SMB  I get a failed backup job! The logs tell me this Processing ADMINDC1 Error: An unexpected network error occurred. Asynchronous request operation has failed. [requestsize = 524288] [offset = 528384] Failed to open storage for read/write access. Storage: [\\ADMINNAS\Veeambackup\VMbackupjob2\ADMINDC1.a00c5b97-a1c2-4fb5-8717-7576427fd30fD2024-04-21T134040_E6E7.vbk].Error: An unexpected network error occurred. Asynchronous request operation has failed. [requestsize = 524288] [offset = 528384] Failed to open storage for read/write access. Storage: [\\ADMINNAS\Veeambackup\VMbackupjob2\ADMINDC1.a00c5b97-a1c2-4fb5-8717-7576427fd30fD2024-04-21T134040_E6E7.vbk].Proce

I have 2 jobs, each of which backs up a single Windows server with a retention policy of 7 days. 1 is working as expected. The other is continuously filling the backup volume with backups (going on 8 TB) stretching back to February. All the settings between the jobs are the same. Retention is set to 7 days. I assume that if I just delete files the entire chain becomes unusable. There does not seem to be a manual truncate the backup chain command or option. So just how does one convince Veeam that February 28 is more than 7 days ago? Thanks.

For those living in Canada and able to attend the VUG Canada event on May 2nd registration is now open. You can find the link in the VUG Canada group page here - Looking forward to seeing lots of attendance and having a great night with some beer tasting.

I want to revisit a discussion I’ve had before about the best DNS configuration for Veeam Cloud Connect.What is common is that there is a common DNS name given to the customers for which multiple A records are created. This provides the round robin load balancing for the cloud gateways.I’ve heard two ways of creating the DNS records for the gateways.A records for each gateway CNAME pointing back to the common DNS nameI know I had seen some documentation supporting the CNAME option before but I can’t seem to find it now.I’m asking this in context of pushing out VSPC Agents. I’m not sure I fully understand how the Agents communicates back to the VSPC and connects the Agent Backups or VBR to the service provider. I am seeing in some instances that it adds a service provider to the VBR but using one of the gateway DNS entries and not the common DNS entry.

Hi, I have a Protection Group with 8 clients all running Veeam Agent.  The Protection Group is part on a schedule that backs everything up once a week.  Is there a way to backup one of the machines in an adhoc manner?  Is that Quick Backup or something else?Thank you!

While creating Azure blob storage, what exactly is the configuration in Azure that we need to do in order to activate Immutuble in Veeam?

I’ve been part of technology communities for over a dozen years. If there’s one lesson I’ve learned, it’s that you never stop learning. When I started in tech, Cloud was the shiny new thing. At the time, I was recruiter who wanted to learn about the technologies I was recruiting for so, I started attending Columbus Cloud Computing User Group. Over time, I became more involved in the community, co-organized a cross-platform cloud computing conference, and worked in Community Management with cloud and DevOps engineers, architects, and admins. Through this ad hoc learning, I gained a theoretical understanding of the cloud but not much hands-on experience. As the newest member of Veeam’s Product Strategy team, I’m enhancing my knowledge and becoming more hands-on with Azure and Veeam’s Azure backup and recovery solutions. Today, I’m sharing how I’ve started learning plus my top tips for preparing to learn a new skill. This post is the first in a series called “Learning Through Co

Hello everyone,As you know, we cannot always take a backup by installing a remote Linux agent with Veeam B&R. Because it does not support some systems. We use Veeam Linux Agent as a nice solution here. I was using this for a few of my clients. But the biggest problem is that SMTP configuration cannot be made. Is there an additional solution for this? Or is there a possibility that such a solution will come to Linux Agent in the future?  

We have vbk files from Dec 23 and Jan 24. Do you we need those fie for restore? Our retention was 15 days and it was reduced to 4 days.

hi Veeam CommunityI would like to know your experiences with GFS.What should I pay attention to in order to have a backup copy strategy and what do you suggest?weekly?monthly?yearly?

Hello,Getting the following error while trying to run the backup copy job: “Processing “Server Name” Error: Cannot create or load meta-file "D:\VBRCatalog\Publications\Upload\66f61108-b62d-467c-845f-fc111d0b9223\PubCommands.txt". Open mode: EMtfLoadFile "D:\VBRCatalog\Publications\Upload\66f61108-b62d-467c-845f-fc111d0b9223\PubCommands.txt" does not exist.  ” I checked out the path. There’s nothing in the Upload folder. It’s empty. Please let me know what might cause this?  Thank you.

My query is, we have one Veeam backup server and added one backup repository as DAS of d drive of server, but now we want to configure these backup data replicate to another server as Linux server. can we possible and how?Please guide.

Hi, Yesterday, we applied the available updates to our Veeam appliance through Veeam Updater UI. There were several updates available and they all were successfully installed and the appliance were rebooted all fine. After applying the updates, we started to see this warning in our Azure portal under this Veeam appliance vm:"Virtual Machines in your subscription are running on images that have been scheduled for deprecation. Once the image is deprecated, new VMs cannot be created from the deprecated image. Upgrade to newer version of the image to prevent disruption to your workloads."As a result, our Azure site recovery replication for this appliance was broken between our primary region UK South to the secondary region UK West. When tried removing and reenabling the replication, it throws the error below:"Site recovery extension does not support the Linux operating system kernel version running on the source machine. Ensure that the VM is running a supported Li

We’ve decided to repurpose one of our large Synology boxes (RS3617xs+) and put some big drives to get us adequate storage space. On the bottom layer, the Synology FS will be BTRFS. We will create an iSCSI LUN on said FS, XYZ TB in size, mounted to a Linux VM formatted XFS for both immutability and fast block cloning for synthetic fulls.My question here how do I make sure I’m getting THE BEST compression and deduplication ratios out there from the Veeam side. I assume also “per-vm” repos fit in here as well? If not doing “per-vm” repos, more blocks will be deduped in this scenario than in a “per-vm” repo. This is so we get the best “usage” from our storage and lasts us for some time.Then there’s this article: Data Compression and Deduplication - User Guide for VMware vSphere (veeam.com)Anothe

Hello, community! We just post a video explaining in a simple way some functionalities about the Malware Detection with VBR.  I hope you guys enjoy this video! Have a good rest of week. Regards, Breno

I apologize for my absence from the community over the past few days!Before the post, I would like to make up for it with the sound of some of the coolest Grandpas in the world 😎 One of the aspects that Veeam has been reinforcing is the need for customers to implement and maintain cybersecurity policies using established frameworks in the market, such as the NIST Cybersecurity Framework 2.0. As an example, we have this excellent post by Ray Heffer:https://www-veeam-com.cdn.ampproject.org/c/s/www.veeam.com/blog/nist-cybersecurity-framework-2-0.html?amp=1Implementing technology solutions in line with the NIST Cybersecurity Framewor

we have enterprise plus edition license and installed Pune location Veeam backup server and now we want to use same license file to Bangalore location?so can we use the same license file in bangalore location server ? we have 90 instance  license.Please suggest . 

Backup jobs to SMB are failing on Kernel version 5.15.0-102How can we fix this without downgrading?

Running Veeam agent for Windows free on an intel nuc, image level backup to external USB SSD.Over a week ago we were getting the following in the backup failure reports; One or more bad blocks were detected and skipped and skipped in the source diskError: Cannot process pending I/O request (offset: 28058845184, size: 65536): async reader terminated Corrupted block processing thread failed unexpectedly Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Cannot process pending I/O request (offset: 28058845184, size: 65536): async reader terminated Unable to retrieve next block transmission command. Number of already processed blocks: [9390]. Failed to download disk '50f5cc69-4da2-47ad-a384-fe605dfacfaf'Ran all sorts of tools, benchmarks, SMART checks, chkdsks, etc and found no issues with C: (OS) or D: (eSSD). Noticed Veeam was due for an update, installed the new version, rebooted

HelloWe have a physical Huawei server (5288 v5) with Windows 2019 and Veeam installed. Since the announcement that the Veeam plugin is no longer supported, we have uninstalled the plugin and removed the storage in the Veeam admin center. Now we want to update to version 12, but there is an error message in the configuration checks. This is “unsupported Huawei Storage system”. We're supposed to remove something first, but I don't know what it should be. We have already tried to virtualize the server to another one, but the error persists. Does anyone perhaps know the cause?Many thanks and kind regardsThomas