Community

Way back in December (really, it was only 4 weeks ago ?!?), I posted on my personal blog about the Broadcom acquisition of VMware, and how they were ending all of the current perpetual licensing and moving everything to subscription licensing. However, there were many, many questions, and FUD about the changes and what this would mean for licensing VMware products going forward. After many conversations with VMware, reviews of presentations VMware provided to partners and distributors and reading of FAQ's, I finally have an understanding of just what direction exactly VMware is going with their licensing and how it applies to the end user clients. Please note that this is more oriented towards the newly announced vSphere Foundation subscription and it's smaller siblings, vSphere Standard and vSphere Essentials Plus Kit subscriptions which

More and more companies are depending totally of their ICT infrastructure (on-premises, private cloud, hybrid cloud, public cloud) …Ransomware and hackers are more popular than ever…Therefore one of the most important things is that the company has a solid backup strategy, so we can fall back at those in case of disaster or being impacted by ransomware or hackers.You can find very often the 3-2-1 rule. I suggest every customer or company to even go a step further : apply the 3-2-1-1-0 rule !3 : Maintain at least 3 copies of your data By three copies, I mean that in addition to your primary data, you should also have at least two more backups.Why?The chance that something is going wrong with 3 devices at the same time is a lot smaller than with 2 devices, especially when the primary backup is often situated

Veeam Backup and Replication is comprehensive data protection and disaster recovery solution which is capable of creating image-level backups of virtual, physical servers, cloud machines, and restoration as well. You may encounter the following errors when installing the Veeam backup and replication tool “VEEAM service is unable to start, error 1064: An exception occurred in the service when handling the control request”. Therefore, I will be showing you the steps on how to resolve this issue very quickly. Here is a detailed link to this post.If you are here reading this troubleshooting guide "new Veeam Backup server but then Veeam won’t start", this means you must have recently instal

Hi All, I trust everyone is doing well. Please assist one of our Backup Copy is not running due to the below error. File does not exist: [********.vib].Failed to open storage for read access[******.vib]. Failed to restore file from local backups. Agent failed to process method (DataTransfer.RestoreText). Thanks in advance. :)

I’ve seen this multiple times now with VMware. You cancel a task via vCenter or the ESXi UI and it just stays there hanging and nothing further happens. Normally this situation resolves itself after some time, but just last week I had a case where the task never stopped. While the Webclients weren’t really helpful in that case, we were able to cancel this task with the ESXi commandline.Warning: Interupting certain tasks, for example snapshot consolidations or Storage vMotions, can lead to issues or corrupted VMs. So only do this if you don’t have any alternatives and need the task to be canceled. And better have a backup at your hand.SolutionStart the SSH service on the ESXi host where your VM is registered Connect via SSH Query the VM ID: vim-cmd vmsvc/getallvms

For some reason and to come to speed with all the Veeam components, I decided to revive my Veeam Lab and during the process, I encountered the following error “Error 1064 - An exception occurred in the service when handling the control request : No connection can be made because the active machine rejected it “. Before I proceed to fix this issue, I would love to discuss the capabilities of Veeam for anyone that may stumble on this article. Veeam Backup & Replication is comprehensive data protection and disaster recovery solution that provides a centralized console for administering backup, restore, replication operations in all supported platforms (virtual, physical, cloud). Regardless of what your needs are ranging from flexible hybrid cloud capabilities from AWS, Azure, and Google Cloud, or the most robust ransomware protection and recovery options. Veeam brings hardened immutable storage options, dependable cloud-native backup options

Hi everyone, I have problem with one of my servers who have MSQL and when the backup is finished i have this warning message “ Unable to truncate Microsoft SQL Server transaction logs. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate SQL server transaction logs for instances: . See guest helper log.” I have search in official support and only find that the veeam account for backup must be MSQL administrator on that database, and to be local admin on that machine. I have make him database admin, but still i have this warning, and the hdd on that machine will be full soon. We have V11 Enterprise with support and so on, but because we are Public Enterprise we have bought this product from one Company in our Town. Can somebody give me some solution instruction step by step ?

While attending the VeeamON conference in Las Vegas back in May, Veeam announced they will be releasing Veeam Backup & Replication (VBR) v12 later in the year, and gave several sessions presenting what some of those features will be in the new release. I thought I’d do a write-up of what v12 features I’m looking forward to most, as well as provide a few extra lines of other notable features coming.Security-Veeam is upping its security game by implementing Multi-Factor Authentication (MFA) and Group Managed Service Accounts (gMSA). MFA is self-explanatory. From the VBR Menu > Users and Roles option, a Security window opens for you to select MFA for your Veeam user accounts (see figure below). But what about the gMSA? gMSA is a fantastic concept as it allows Veeam to use Active Directory service accounts while not storing the password locally on the Veeam server (i.e. when using for AAIP). Instead, VBR retrieves gMSA passwords on-demand

These days I saw a strange error that makes every backup failed. I thought this would be interesting to share. SituationThere were a few jobs running each day. From a point in time all jobs failed. Error that was shown in console was: [Error Unhandled exception was thrown during licensing process] I checked licensing of course. All hosts were licensed using perpetual licensing. No instances were licensed separately.SolutionIt turned out to be no license problem at all. What happened was, password of the user that was used for connecting to VMware vCenter was changed. After updating the new password in Veeam Manage Credentials too, everything works fine again.

Hi everyone,recenly i’m doing some test on the veeam backup&replication community edition on my Dell R710 which is running server 2019 standard. And at the first time, i can add a hyper-v server which is running server2019 (standalone) to the backup job, but once i deleted the job, i cannot add any hyper-v again.It always shows :Failed to connect to host 10.178.3.41Access denied or timeout expired. (sometimes is invalid namespace)Check if you have local administrator privileges on computer '10.178.3.41'.Possible reasons:1. Invalid credentials.2. Specified host is not a Hyper-V server.================what i did for this issue:https://www.veeam.com/kb1914

Hey Guys, Sorry for the weekend help, I am just too excited to leave VEEAM aloneI have googled and read other forum discussions to this topic but they all point towards a service not being started and in my case, everything is running, and I have rebooted everything also coming here for some helpI am in no rush this weekend, this can wait until MondayError message: Error: Managed session has failed: No connection could be made because the target machine actively refused it x.x.x.x:10005   Thanks in advance guys,

I spent some time in testing a new great feature in v11: Hardened Repository. Read here about:What is immutability is about Requirements Setup How it works What is immutability is aboutImmutability in this context means, a backup file cannot be changed or deleted without having root access within hosing Linux OS. So, even the backup administrator is not able to delete backups on such a repository.Why is this important? Think about ransomware. This software is that smart these days, it is able to recognize backup systems. It can trigger tasks like deletion of backup files. But when they are immutable, this cannot be done! RequirementsWhat is needed to get immutable backups? First of all: Veeam Backup&Replication v11. This is the first version supporting hardened repositories. Secondly a Linux server hosting repository volumes.What about the fi

Hi there,Veeam B&R 12 is installed on a Windows 2022 Server, which is installed on VMWare ESXi 6.5 U3. From there I backup our produtvie Server, which is a VMWare ESXi 6.7 with a Windows Server 2016 and a Windows Server 2012 R2 (Exchange Server) installed on it. Everything works fine, exept the backup of the Windows 2012 R2 Server. It does backup, but I receive the Warning “Failed to index guest file system. VSS Control: Index failed". Is there any way to fix this, except disabling the file indexing?

Support for Proxmox from Veeam has been one of the top requests in the last months. Therefore the announcement in May to extend the Hypervisor support to Proxmox Virtual Environment (VE) has been long awaited! This will be the 7th virtualization platform supported by Veeam, in addition to the 3 cloud hyperscalers and the Veeam agents.The Proxmox integration is currently planned for Q3 of 2024 and v1 will already include some nice features/benefits:flexible storage options immutable backups granular recovery cross-platform recovery (for example Proxmox <> VMware) Veeam ‘standard’ performance with CBT, hot add backup and BitlookerIn part 1 of this blog series I want to give a quick overview of the architecture of Veeam Backup for Proxmox and it’s initial setup. Disclaimer: All information and screenshots in this blog post are based on an e