Community

Hello,This is a good way to kick the tires with Veeam Backup for Nutanix v4 and AHV. The prior version of CE was below AOS 6.x. You could not demo Instant VM Recovery because this feature was available with VBN AHV v3.x and required AOS AHV 6.x. It can be installed on an ESXi server. Please follow the links below. It does require that you register with a Nutanix account😀. Caution: It is not recommended to register CE clusters with Prism Central, which is being used for commercial licensed clusters.Caution: No upgrade path to CE 2.0 will be provided from the older CE or Prism Central for CE.Nutanix CE Download Page

whilst adding a Hyper-V standalone server, fails with this error:Veeam Backup Transport -- Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action VmaCheckIsAccountAdmin, entry: _VmaIsUserAdmin@4, library: C:\Windows\Installer\MSI4E95.tmp

 🚨 The Challenge: Limited Support Access During Critical POCsAs a VMCE-certified engineer and active partner, I’ve had the opportunity to deploy Veeam solutions across various environments, often in time-sensitive Proof of Concept (POC) scenarios. These are crucial moments—not just for testing features, but for building trust and confidence with potential customers.However, one recurring challenge we face is limited support access during these POCs. Without a production license, even VMCE partners are often restricted from opening support cases unless routed through a customer with a valid production support contract.This becomes a bottleneck—especially when dealing with complex configurations, replication issues, or backup repository anomalies that need quick resolution. ✅ The Proposal: Grant Production-Level Case Privileges to VMCE Partners (During POCs)

We have been using Veeam for almost 2 years now.  We recently had to redo our Hardened repository due to a poor setup the first time around.  We got the repository reformatted and setup correct but now we cant do a 1:1 copy from the primary data store.  I would think that when you do the backup job and select copy the whole primary data store it would indeed do that, but Veeam support told me it will only copy day forward. We are just looking to have the Hardened Repo be a 1:1 of the primary datastore.  Support told me the only way to do that is to do a file copy of each job to said repository.  This of course would duplicate anything that was already on this repo.  Is there another way to accomplish this?  Or does anyone know if there’s anything on the horizon for Veeam to make it copy 1:1 like one would think a “copy” of the main datastore would be?

I currently have a Quantum Scalar i3 tape library with 4 drives. I need to add 2 more drives to the library in Veeam. We bought a new SAS card, and have not yet installed it into the tape server. When I do, and connect the 2 new drives to it, I am unclear as to what I will need to do in Veeam to get it to recognize that there are now 2 more drives in the library, so I can add them to the correct media pool. Will it automatically see them?

Hi all,I wanted to share with you my latest article discussing the security features built into Veeam.https://www.backupart.cloud/veeam-security-features-recap/It is a hopefully comprehensive summary of everything, with a few tips for suggestions and advanced configurations.Let me know if anything is missing.Thanks! 💚

Hi everyone, I started the update, and it has been sitting at step 1 for over an hour. Is this normal or should I be concerned? Thanks in advance! 

Currently i have 9 TB azure file share and want to make backup copy for my VBR and configure this file share as backup copy repository.But in the backup infrastructure there are external repository and VBR can connect to the azure blob storage.So i want to know what pro and cons using azure blob vs azure file share? Which one is more recommended?

I am back with another PowerShell tip and again one more for the VB365 product.This one shows you how to move data between repositories using the Move-VBOEntityData cmdlet.  There is also a script that you can download to automate your move as well.You can check it out here - https://just-virtualization.tech/2025/04/10/powershell-tips-for-veeam-vb365-v8-move-data-between-repositories/Also once you complete the move and since with this command you cannot move data in a repostiory from a Proxy to a Proxy Pool, referencing my first blog will allow you to complete the move from Proxy to Pool once the data migrates.  You can check it out here - 

Veeam Configuration Backup is the process of creating a file that contains all the settings and data of Veeam Backup & Replication. This file can be used to restore your Veeam Backup & Replication installation in the event of an issue such as server failure or software error.Veeam Configuration Restore is the process of restoring your Veeam Backup & Replication installation using a previously created Veeam Configuration Backup file.Why Should You Use Veeam Configuration Backup?Disaster Recovery: In the event of an issue such as server failure or software error, you can quickly and easily restore your Veeam Backup & Replication installation. Time Saving: Instead of configuring a new Veeam Backup & Replication installation, you can restore a previously crea

Hello Veeam Community,I would like to share some insights regarding the use of Google Cloud Platform (GCP) storage as a backup target for Veeam Backup & Replication, particularly in scenarios involving GFS retention policies with yearly backups. As we all know, Veeam supports object storage integration with multiple cloud providers, and GCP is one of the key platforms many organizations are exploring due to its flexibility, pricing models, and deep integration with Veeam. Before diving into the impact of GFS retention, let’s quickly review the main types of GCP Cloud Storage that can be used for backup purposes:Standard Storage:     - Best for frequently accessed data.      - Ideal for short-term storage or backups with high change rates.Nearline Storage:     - Cost-effective for data accessed less than once a month.      - Suitable for monthly or quarterly backup

Backup to object storage requires a valid enterprise edition license Veeam job has been stopped with failures.Error: "Provider load failure."→ Backup Copy Job (Object Storage ) hello This is rich.kim who loves veeam. While using a Veeam permanent license, the error message below suddenly occurred in the object storage of the secondary backup (backup copy). This is a perpetual license that I am using without any problems. Why does a license-related message appear? I can't understand.~ 

Dear Community, After upgrading my VBR server, I faced challenges upgrading the associated GCP appliance due to tricky infrastructure and policy level restrictions.I worked with Veeam support for over two months, sharing multiple log bundles, conducting several remote sessions, and troubleshooting persistent upgrade failures.I would like to highlight the key issues, steps, and eventual resolution to help others facing a similar situation.Challenges Faced:The GCP appliance upgrade consistently failed due to missing permissions and internet access on newly created instances. Policies at the organization/project level restricted public internet access, which was mandatory during the upgrade process. The appliance couldn’t reach Veeam repositories and update servers. Sessions with Veeam support revealed dependencies on temporary VM creation and public IP accessibility.Here are

AVS Cloudadmin role not working with Veeam VBR inside AVS. The cloudadmin role was created using the cloudadmin@vsphere.local priviliges as the template. So any account you assign the cloudadmin role should also work if the cloudadmin@vsphere.local is working.  Our Veeam VBR in AVS works if we use the cloudadmin@vsphere.local account but if we assign a service account to the cloudadmin role, it does not. The error is shown below:Failed to open VDDK disk [[vsanDatastore] c5ca9666-0633-ee72-8079-08c0eb414cda/Logon attempt with parameters [VC/ESX: [vc.4bc149b438784b2e87ed53.westus2.avs.aFailed to open disk for read.Failed to upload disk 'vddkConnSpec>'Agent

 When using preferred networks you might find your backup jobs take longer to initalise, commonly when you’ve got distributed backup components such as a physical proxy/repository and your Veeam Backup & Replication server isn’t performing any backup processing. This is because your Veeam Backup & Replication Server is also required to use your preferred networks configuration, even if it doesn’t have any network connectivity that resides within your preferred networks.This causes the job initialisation to take a lot longer than usual, and this grows even slower the more distributed your network topology and the more preferred networks you have. This is because your Veeam Backup & Replication server has to work through every preferred network match, before moving onto the rest of your network interfaces.Now, a quick

HiI am a newcomer to Veeam. I am backing up to a remotely located NAS using iSCSI. The speed is sitting at < 1mb/s and has been for days. There are no checks in the limit read and write speed under the repository settings and there are no bandwidth restrictions under network traffic rules. Are there any other settings that could be causing this restriction? Many thanks  

We're installing a storeonce 3660 FC and noticed quite a poor performance during network-free backup.The setup is as following:Primay storage alletra 5000 16Gb FCBackup Gateway server 8Gb FCStoreonce 3660 16Gb FCVeeam 12.2.The storeonce has been configured as repository with FC activated and the gateway server can reach it correctly, SAN has been zoned.The JOB is configured with storage integration and it creates the Alletra snapshot mounting it to the gateway server.Given such configuration the backup job is running at about 200MB/s where the same job using a diskbased target via FC as well is running at 1GB/s, which make sens of the 8Gb gateway server's HBAThe SAN Fabric is made of 2 switches, one is an 8Gb Blade switch and the second is a SN3000 16Gb switch.Th Gateway server is connected to the Blade Switch while the Alletra and the Storeonce are connected to the external 16Gb switch

Hello community! Recently, I ran into an issue where AIX backup jobs were taking longer than expected to start. After digging around, I came across a very useful Veeam KB article (KB2014) that suggests testing disk I/O to identify potential bottlenecks, especially useful when backing up to tape or dealing with performance inconsistencies.I decided to try out one of popular tools for benchmarking and simulating disk workloads: DiskSpd (for Windows).Step 1 – Install Disk Benchmark ToolMake sure you have the following installed: diskspd– Microsoft’s free disk performance tool for Windows. Step 2 – Run DiskSpd on WindowsHere’s the command I used:diskspd.exe -c25G -b512K -w100 -Sh -d600 D:\testfile.datExplanation of parameters:  -c25G → Size of the test file (25 GB

We are a service provider and using VCC and VSPC. We have two repository like NAS and cloud repository. We had connected multiple company with VSPC through VCC and taking backup to VCC NAS repository. We need to make a secondary copy of NAS repository to redunent and highly available the customer data.How can we do the redundency of repository like NAS to Cloud in Veeam Service Provider?

Hello folks,I asked to the forum but maybe one of you have the answer. I configured a Veeam Azure Appliance, my policy is the following:DailySnapshots:Create 6 snapshots and keep 24 snapshotsBackups:Create 1 backup per day and keep for 30 daysWeeklyCreate restore point at:12:00 AMSnapshots:Keep 1 weekly snapshot (6 days excluded)Backups:Keep weekly backups for 1 month (6 days excluded)Monthly :Create restore point on:1st day of the month at 12:00 AMSnapshots:Keep 1 monthly snapshotBackups:Keep monthly backups for 12 monthsMy VAB is linked to a VBR. On my VBR when I browse the backup properties for each instance I see only Full Backup (vbk files), is that normal with VAB or I miss something ? 

Hey folks, I am not going to present a new Veeam tutorial this time!I had some free time ahead of me so I had fun creating the starter pack for our dear Alfred. I think it can be improved, but here's my first version! I hope you'll like it!Next step a video of our dear Alfred?

I have single veeam backup policy with contains of 10 VMs.How we can get backup status for each VM to knowing the VM is backup is successful or not using powershell? 

 IntroductionIn the first of 4 blog posts of this [Migrate Veeam Infrastructure Off Production Domain series], we described the fundamental security reasons behind moving the Veeam infrastructure components OFF Production domain.  Disclaimer: This is not intended to be a complete Security Best practice reference, nor does it address every possible scenario. A Veeam Solutions Architect can be engaged as needed

I am currently going through the network segmentation best practices (Segmentation | Veeam Backup & Replication Security Best Practice Guide) and I’m wondering where would be the best zone to place my VB365 server.  Part of me thinks Management since it’s a backup server, and part of me thinks Restricted since I am backing up to a local disk.Anyone care to share their thoughts?Thanks!

As some of the Veeam staff probably know, I am definitely NOT Veeam's biggest fan. One reason is because there always seems to be a need to sort of build an environment to suit Veeam. As a service provider, I've always looked for solutions that best fit existing environments with little to no modifications. I've also been very big on ease of installation, ongoing administration, and intuitive interfaces for managing everything, I wouldn't rate Veeam as the best at any of that.However I do continue to see a lot of people who say "Veeam is the best" and "Veeam is great" and "Veeam solved all of our problems", and also threads like this veeam-backup-replication-f2/broadcom-vm ... 91924.html where there's plenty of people discussing needing to find a way to build their entire infrastructure around "what works with Veeam