Blogs and Podcasts

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.You will perform granular recoveries on individual objects and restore specific object versions. Of course, the immutability, the ability to define object version, object archive, and Backup Copy will be supported.This is all based on the NAS backup technology of Veeam Backup & Replication. Let’s wait for this new version!  

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:Mount ISO and start WizardCheck VSPC website consoleCheck version post updateOption 1) Manually download Management Agent for tenant serversManually Install Management Agent on all yours manged server TenantsOtion 2) Update Managment Agent VCC server from consoleFrom the console verify that all agents are updated without errors.enjoy :D

 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 Passover CeremonyGreat Friends Great FoodGreat PartyThe Best People Here’s to the number one tech community in the world 🍻

 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 plug-in natively integrates with Microsoft SQL Server Management Studio, the Microsoft SQL Server management tool used by organizations' DBAs (database administrators).With this plug-in, DBAs have complete control over the database backup and recovery processes, with zero friction with daily activities and an integrated manner with the organization's data protection policy.Therefore, the same Veeam platform protects virtual servers, Kubernetes clusters, physical servers, notebooks, desktops, and public cloud services.Some di

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 that are not compliant with the immutability target.Within each of these widget sections are call to actions for a related report to provide drilldown information on the appropriate topicsEach of these widgets have options to include/exclude settings for example:Data Recovery Health can cho

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 Public Cloud instance appear as a ‘managed server’ within VBR. The standalone Veeam Backup for Public Cloud will still exist, and all existing functionality will remain. Veeam Backup for AWSWe’re going to see support for Dyna

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 :) cc:/ Team 2  @Markus.K1985 @Chris.Childerhose 

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 folder is required. Path: [Path [<Path>], RootId [ffffffffffffffff]]Well, that’s not good! Because these were soft symlinks, this was the reason why Veeam was unable to process the data. But

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 methods. They are as follow;Azure AD password hash synchronization: This is basically the simplest way to enable authentication for on-premises directory objects in Azure AD. Users can use the same

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. Create a test environment of your on-premises infrastructure on AWS to validate patching, for example. Pre-requisites As always it is important that we understand the prerequisites of the solution. And in this case we are still involving a solution external to Veeam, which is AWS. Supported backup types  First, we have the supported Veeam backup types for restoring to AWS. Are they: Backups of vSphere or vCoud Director VMs created by Veeam Backup & Replication. Hyper-V VM backups created by Veeam Backup & Replication. Backup VMs and physical machin

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 9GB of free space. I cannot restore files from any existing restore points. (actually, I cannot mount any restore point to the mount server).I tried to create a new test backup job to back up the VM and tried to restore the guest file from the first restore point (full backup chain) but got the same error. So, I expend the C drive to add 10GB more storage space to it, then rerun the backup job.Now, I can mount the incremental restore point, but I still cannot mount the full backup restore point.This issue is solved, but all the existing restore points cannot be mounted before expandi

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 to the dentist wi

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:So, it appeared to me like Veeam didn’t actually update all references to any of my old Hosts and their associated

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.• Sandboxed and virtual container runtimes: runsc (from gVisor) and kata-runtime/the-runtime (from Kata Containers). The Container Runtime Interface (CRI) is the specification in charge of the communication between the kubelet and the high-level runtimes. The CRI defines gRPC APIs that allow the kubelet to interact as a client with different runtimes. CRI performs an abstraction layer for high-level runtimes.  The high-level runtimes use a lower-level container runtime to run and manage the components required to deploy and operate containers. Open Container Initiative (OCI) specifica

 Home Lab upgrade!Hi Folks, recently I wanted to «upgrade» my home lab, and I was thinking the best way to have an affordable, low consumption usable home lab for a ESXi Cluster, nothing fancy, just to be able to deploy a couple of little VMS, play with HA, DRS, shared storage and so on.I started checking out the Intel NUCs, but then I realized that it comes «empty», so it becomes costly at the end.Then, what about HPE Gen 8-9 Servers, «the wife would kill me»They are noisy, expensive and consumes tons of electricity!So, looking over the hardware I have, I looked into my Workstation, a Lenovo P320 which it has 64GB of ram, more than sufficient to run a Nested lab, but I wanted something more realistic, with wires and lights, you know, Im a hardware and wires lover!I kept the Workstation as base Server, Planning tu run there the base or foundational vms I normally run like: vCenter, DNS, AD, a Storage Appliance and a Veeam Server.lets keep it «low profile», so, Nowadays normally we do h

Hey! The first version of Magic Quadrant for Container Management is around! If we compare the companies named leaders by Gartner with those that contributed most to the Kubernetes project last year, we will realize that they are practically the same. Coincidence? I don't think so.These solutions deliver many Cloud Native Computing Foundation (CNCF) projects alongside Kubernetes distributions, like service mesh, security, observability, etc. Container management is a foundation for cloud-native infrastructure and helps enterprises automate container image provisioning, operation, and life cycle management at scale.Remember to protect these platforms with Kasten! :-) 

If it happened Error 1327.Invalid Drive when you try to upgrade the Veeam server, don’t panic. This is likely caused by a stale registry entry for the Veeam server. In my case, the Veeam server had an F drive but removed it a long time ago. My error message is Error 1327.Invalid Drive F: and the upgrade failed.1.login to the Veeam management server.2.Run regedit.3.check the following registry path on the Veeam server. HKEY_LOCAL_MACHINE\Software\Veeam\Veeam Backup Catalog\ and HKEY_LOCAL_MACHINE\Software\Wor6432Node\Veeam, do either of these paths show the F drive? Likely it will be the VBR catalog folder in my case.4.Right-click CatalogPath, select Modify.5.Change the Value data from F:\VBRCatalog to C:\VBRCatalog, click OK.6.Re-run upgrade again. The error message should be gone.

Hello All,Sharing update on a case where Jobs stuck in VBR, however does not reflect any Veeam.exe process under VBR, proxy or agent Machine From the task logs could find the PID of the job as below however no process shows up under task Manager on VBR, proxy or agent machine in this case oracle plugin VM.  Process: [64 bit], PID: [19652], SessionId: [0], UID: [fc911f7e-ed08-4bb7-be1f-4a3461f23dda] for the SRV03248Process: [64 bit], PID: [61356], SessionId: [0], UID: [3b69526c-e334-4305-bd33-bcced8fc2944] for the SRV03576Process: [64 bit], PID: [19724], SessionId: [0], UID: [a941f009-e8b7-475a-8fd2-1388653256b6] for the SRV03709Process: [64 bit], PID: [61356], SessionId: [0], UID: [3b69526c-e334-4305-bd33-bcced8fc2944] for the SRV03821 I worked with support, could identify ghost entries in DB, which was removed by below query. DB and this SQL Query should remove the jobs from running:Update [dbo].[Backup.Model.JobSessions]Set [state] = -1where id = '<id of the job>'Here are the I

As announced in VeeamON 2023, Veeam is working to improve the ransomware detection capabilities in two ways:Comparing guest file system indexes and looking for typical traces of malware. AI/ML to perform an in-line entropy analysis of the data stream on backup proxies to detect previously unencrypted data becoming encrypted.Some Ransomware detection techniques exist, but many have a poor detection rate. They also suffer from having high false positive rates, where they flag benign programs as malicious, and false-negative rates, and thus fail to identify malicious programs.The same applies to files where obfuscation techniques has been used by ransomware in an attempt to avoid signature detection. One of the most common techniques used is a CRC, which involves analysis of the value and position of a data group.On the other hand, detection techniques like Behavioral and Dynamic analysis must collect significant amounts of information. At the same time, monitoring has the disadvantage th