Blogs and Podcasts

I’d like to first thank Rick Vanover, Madalina Cristil, Nikola Pejková, and everyone at Veeam for their efforts and support leading into my second Veeam 100 Summit. It’s a HUGE undertaking that requires many levels of coordination. This was my second time attending the event in person. It was an hon

Hi, Wanted to try and bring some of the magic of the Veeam 100 Summit to the Community Hub, as so much of Veeam’s success comes from the community! I’ll be blogging here each day bringing some highlights from the summit. Hope you enjoy it!  

Hi everyone, I bring this book, I hope you Enjoy ItThis book provides tips that help administrators maximize the performance of VMware vSphere 8.0 Update 2. Sections cover hardware selection, ESXi and virtual machines, guest operating systems, and virtual infrastructure managementDownload Here 

Hello,  I try to install Veeam Agent for Linux on my debian 11but i have two errors that involve failure of Veeam Agent for linux installation 20/09/2023 09:41:17 Failed [172.16.0.18] Failed to install veeam_6.0.0.1060_amd64.deb and blksnap_6.0.0.1060_all.deb packages: E: Impossible de trouver le paquet linux-headers-5.10.0-18-amd64 E: Impossible de trouver de paquet correspondant à l'expression rationnelle « linux-headers-5.10.0-18-amd64 » E: Impossible de trouver de paquet correspondant à l'expression rationnelle « linux-headers-5.10.0-18-amd64 » Failed to invoke rpc command  0:00:14 20/09/2023 09:41:32 Failed [172.16.0.18] Failed to install Veeam Agent for Linux: E: Impossible de trouver le paquet linux-headers-5.10.0-18-amd64 E: Impossible de trouver de paquet correspondant à l'expression rationnelle « linux-headers-5.10.0-18-amd64 » E: Impossible de trouver de paquet correspondant à l'expression rationnelle « linux-headers-5.10.0-18-amd6

Hello Team, Can anyone help, am trying to upgrade VeeamOne env from 12.0.0.2498 to VeeamONE_12.0.1.2591_20230314, am unable to upgrade as it shows license is invalid. Could you please help path to download trial license for VeeamONE_12.0.1.2591_20230314.  

As announced in VeeamON 2023, the release 12a (or 12.1) of the Veeam Data Platform is coming soon. In addition to bringing new cybersecurity features, one of the focuses is improving the ability to protect data stored in Object Storage.It is a critical demand for organizations to store data related to modern applications or any unstructured data related to the business.It will be possible to take data from object storage and store it in backup repositories of any type: block, file, object storage, or even tape.There will be flexible recoveries in restoring the entire buckets, including permissions, attributes, and tags.

Hi all.reference Upgrading Veeam Service Provider Console - Veeam Service Provider Console Deployment GuideI share the procedure step by step for upgrading VSPC v6 to v7.Backup database before proceeding. Backup of the VM dedicated to the VSPC service before proceeding. Cold snapshot of the VM VSCP if there is database Download ISOCheck your versiontip:

 And the Veeam 100 Summit 2023 has now come to a close. I myself made it home yesterday, and I know others have stayed on a bit longer but the numbers are starting to dwindle as this becomes just a fond memory.For my final piece of Veeam 100 content here, I want to share with you the heart of what makes this event such a success. The people! And I welcome the other Veeam 100 attendees to share any green content photos and stories!For me, whether it’s been getting lost in the beautiful architecture of Prague, or having a cheeky pint after hours, the friends I’ve shared it with have made it unforgettable!Photobooth FunThe Vanny Pa

 Hey! Microsoft SQL Server backends some of the organizations' most critical applications. Any loss of data or even the inability to fully recover this environment can cause catastrophic damage to the business.Veeam offers several options to simultaneously protect the most business-critical applications and Microsoft SQL Server environments.Starting with version 12 of Veeam Backup & Replication, the Veeam Plug-in for Microsoft SQL Server was made available.This pl

We start the day with @kirststoner12, Roman Kuksov, and @jorge.delacruz   First up is Jorge talking us through the Veeam ONE Threat centre.Jorge talks us through the data platform scorecard, made up of the following four contributing components:Platform Security Compliance - This is driven by the VBR Security & Compliance Analyser (Formerly known as the best practice analyser) Data Recovery Health - This score looks at backups marked as suspicious/infected, you should hopefully see a 100% health when you first deploy this Data Protection Status - This score is based on the percentage of protected workloads vs unprotected Backup Immutability Status - This score is based on the number of workloads

Today kicks off with another all-star cast! @Julia F Morgado, Lyudmila, Vitaly, and Alec all on stage to talk the shared features of all Veeam Backup for Public Cloud, and individual product updates! Shared FeaturesFirst up, we’ll see Veeam enabling us to leverage more granular permissions for service accounts, with a built-in validation check to confirm the permissions are assigned.We’ll also see updates to the workers, with the ability to assign tags automatically to all worker nodes for their lifecycle.The biggest announcement from this however is that we’re going to see future Veeam Backup for Public Cloud updates only become available to Veeam Backup for Public Cloud instances integrated into Veeam Backup & Replication. This will make the Veeam Backup for Publ

Dear Support,    We have encountered a backup problem and cannot perform any backup operation at present. Please see the attachment for details. Could you please help us?

I have put together a blog post going through what we have hacked during the Veeam Community Hackathon. I wrote about why we have done the project, how we developed the main functions and how we published the modules. Here is a link for the blog,https://adammazouz.com/post/2023/10/powershell-sdk-module-for-veeam-backup-replication-rest-api/happy reading :) 

Alt Text: Title image with the topic title as it’s textHi, a quick workaround story today from the field.I configured a NAS Backup job that was to protect an SMB share with a bunch of sub-folders & files. When the job ran, no files and only a few folders had been processed. When I browsed the backup, the folders I was critically aiming to protect were all missing.Upon further investigation of the share, the folders weren’t “actual” folders, but were instead unsupported symlinks. I discovered this because I attempted to change the scope of the backup job to a particular subfolder to confirm access. When I tried this, I received the following error message:Unable to backup root folder <Folder Name>: folder is unavailable. Invalid root item type: a file or a symlink is detected when a fold

Hallo everyoneI am trying to figure out what the best way to transfer Running backup jobs with tons of restore points pr. job, to a new Veeam server, without loosing any backup data/historyThe “old” Veeam server has to be decommissioned - and so will the current repository, over time.The new Veeam server should have all jobs and backup data (restore points) from “old” Veeam server and run on new repository/storage as wellWhat will be the best way on migrating all, from old to new server - and from old repo to new repo, with out loosing vital backup data and historyAnyone ?

Azure AD is a cloud-based multi-tenant directory and identity service that provides identity and access management capabilities in the cloud.Since choosing the correct authentication method is the first concern for organisations wanting to move their apps to the cloud. The following section helps you decide which authentication method is right for you by using a decision tree. It helps you determine whether to deploy cloud or federated authentication for your Azure AD hybrid identity solution.Scr: MicrosoftTo choose an authentication method, you need to consider the time, existing infrastructure, complexity, and cost of implementing your choice. These factors are different are different from Organisation to organisation. Because of this, I will be highlighting on the different authentication me

Hey guys! Recently I write a blog post about restoring backups to AWS. I normally write in brazilian portuguese but I thought will be a good content to translate and send here too. Like a say, I will detail all the pre-requisites and scenarios to restore backups to AWS using Veeam.This can be useful in three scenarios:Restore your on-premises environment directly to EC2 machines on Amazon. Migrate your on-premises environment to AWS.

This error happened to one of our clients. The backup chains’ status is good without any issues.VBR v12 guest file restore---happen error message is as below:Secondary GPT header LBA 209715199 exceeds the size of the disk (86401630720)Agent failed to process method {Mount.GenericMount)  I tried to change the mount server of the repository, but I still had no luck.This VM has only one virtual disk (C:) with 9

If the backup jobs fail and show an error message is “Unable to allocate processing resources. Error: Unable to find Hyper-V hosts where VM 'xxxx-xxxx-xxxx-xxxx-xxxx' is registered: Failed to connect to Hyper-V Integration Service on host, port 6163”. I tried to review the settings, and all of them look fine, but the backup jobs failed always. I have run into these issues sometimes, it’s easy to solve, you just need to reboot the Veeam management server or restart the Veeam services of the Veeam management server.

Hi Everyone,I thought I would first of explain what inspired me to write this on a nice September morning. It was a dumb decision. I have made many dumb decisions in my life and sometimes, just for fun I repeat them. In this case it was agreeing to a dentist appointment at 7 am on a Friday morning. This all came about around the time of VeeamON. Some of you noticed there were times at VeeamON in Miami when I was walking around with a not so jolly expression on my face. The reason for this was because I was stuck in between benefits providers (read dental insurance) and precisely at that time one of my remaining wisdom teeth decided to cause Armageddon. I held out as best I could. I tried keeping Listerine in my mouth for long periods at a time, then going to the beach and holding salt water in my mouth as I read it has healing powers (although this caused some fellow beach dwellers to give me strange looks). Finally a few weeks after getting back home I was able to go

I wanted to share a couple Veeam errors I experienced on my Replication (DR-side) server after I replaced server hardware. Not sure if anyone has experienced either of these errors, but they were quite frustrating to work through. Let me know if you had a similar experience/occurrence and what you did to resolve it. Maybe what I share here will help someone.As I was replacing hardware in my DR side vSphere Clusters, on my VBR server, I would perform a vCenter rescan to make sure VBR would see the new Hosts and my Replication jobs would run successfully. Because all the tasks involved with replacing h/w is time-consuming, I was only doing 3-4 Hosts a day (took 3 days for 10 Hosts), so I had to do this rescan several times. I think I only verified 1 or 2 jobs out of around 12 I have, but they run good. On the 2nd day, I noticed 1 of my jobs failed. The error shown was below:

I was doing a production backup chains upgrade, and we saw an alert for Microsoft Defender Cloud.It was because the blobs were being rescanned and upgraded by Veeam during the backup chains upgrade.   All was fine.  It's just a triggered alert that could be documented internally as nothing to worry about.  

That was not happening only at VM with the secure boot in the Hyper-V environment. It also impacts VMware.After installing this update on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up. Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below.We may ask customers to put them on hold to install the October patch for Windows Server 2022. 

Container runtimes are fundamental components of Kubernetes. It is responsible for managing the execution and lifecycle of containers, and it is necessary to choose and install a container runtime into each worker node in the Kubernetes cluster to run PODs. Container runtimes can be categorized into:• High-level container runtimes: CRI-O, containerd and Docker.• Low-level container runtimes: runc and crun.