Community

 In my last post I covered the requirements and necessary steps to configure immutability for HPE StoreOnce with Veeam V12. In this post I want to focus on how immutability behaves in different scenarios.Enable immutability for existing Catalyst storesIf you have existing Catalyst stores, the good news is that it’s possible to enable immutability for them. Let’s take a look at the Veeam helpcenter:Note that if you enable immutability and Veeam Backup & Replication does not start a new backup chain and still continues the chain, the whole backup chain is marked as immutable.https://helpcenter.veeam.com/docs/backup/vsphere/storeonce_supported_features.html?ver=120#immutabilitySo, after you configure immutability, the current or new backup chain will be made immutable. All other existing backup chains won’t be touched and therefore stay mutable.This is also exactly what I could reproduce in my lab environment. After enabling immutability, the current chain is made immutable, while all

Hi, Possibly a question for @Federica or @haslund. As the VMCE & VMCA are yet to have their new exam & certification released, willl there be an extension to the expiry of the current VMCE & VMCAs?For example:I sat my VMCE 2021 in June 2021, my VMCE states it expires the 9th June 2023. Likewise I sat my VMCA in September 2021, and my VMCA states it expires the 1st September 2023. I’m conscious that this looks like it’s just an automation, but as we’re a VASP, and our ProPartner portal is showing this imminent expiry, that it could reflect badly on my organisation if my certifications have ‘expired’ even if there isn’t a replacement certification available. A second question on this, after the 2023 grade exams are available, how long will we have to upgrade before the certifications are counted as ‘expired’ within ProPartner? Thanks!

Hi allI already read and know different articles and posts of different people like @MicoolPaul, @olivier.rossi, @Chris.Arceneaux and others regarding object storage and the used block size.In this article a bit more about that in combination with Veeam Cloud Connect. Goal : My goal is to setup a new Veeam Cloud Connect infrastructure for multiple hundreds of customers. Setup : The setup of the Veeam Cloud Connect is a infrastructure that consists of several SOBR’s that consists of multiple extents (performant block-storage physical servers with REFS - 64K) in a performance tier in 1 datacenter and a capacity tier with object storage (performant physical object storage devices) in another datacenter with using the copy-mode and immutability.Of course there is a performant interconnection between the 2 datacenters. Advantages of this setup : There are a lot of advantages in my opinion in using that setup : we use 2 datacenters and all data is being copied from 1 datacenter to another da

Hello Forum,Since I’m reconstructing everything I would like to seek some advices for WAN accelerators.We have Primary Site (Austria, Vienna) and Secondary Site (Serbia, Novi Sad).Backup to Primary:Backup Jobs going to Synology LUN that is connected via iSCSI to Windows Server (ReFS 64KB block size) + FastClone From Monday to Friday - Incrementals On Friday - Full Synthetic Backup 21:00 - 22:00 starting of the Backup Jobs Backup to Secondary:I would like to try and implement WAN Accelerators for this so that potentially we have better performance. 2 Source WAN Accelerators. 1 for large VMs and 2 for small VMs 1 Target WAN Accelerator.Question regarding Backup Copy Job:As I’ve read some documentation about WAN Accelerators I checked that Source WAN Acc should have better CPU performance so it doesnt need to be some high I/O performance device and for Target WAN Acc is opposite, is thsi true? Plan is then to use physical Windows Machine with SSD on Target WAN Accelerator How would I appr

Alt Text: Graphic with blog post titleDon’t you just hate it when something is working and then it breaks?I was working with a customer recently that had their Azure Storage configured as a backup repository within Veeam (Direct to Object Storage) and all was working great. However, after a few months Veeam was attempting to perform lifecycle operations such as creating synthetic full backups and purging old restore chains, and then suddenly a backup job started to fail.After diving into the logs I could see the following error was happening with every backup attempt:Details: HTTP code: 403, Content Length: 246, Code: AuthorizationFailure,<DATE TIME> :: Error: This request is not authorized to perform this operation.Failed to copy azure blob. Source path: [{ContainerName}//Veeam/Backup/{Folder Name}/Clients/{GUID}/{GUID}/Metadata/Checkpoint/1. Version: [{File Version Date}].], Target path: [{ContainerName}//Veeam/Backup/{Folder Name}/Clients/{GUID}/{GUID}/Metadata/Metadata/Checkp

Protecting your Veeam Data Platform Audit Logs is another way keep your security sensitive logs safe. Using NetApp ONTAP SnapLock Write One Read Many (WORM) technology can protect you from bad actors attempting to delete your audit logs. Please make sure the NetApp ONTAP controller has a SnapLock license. The first thing you have to do is create a NetApp FlexVol (volume). I logged into NetApp ONTAP System Manager and from the main menu navigated to “Storage=>Volumes=>+Add” to get to the volume screen below (Figure 1). I filled in the fields and clicked on “More Options”(Figure 2) to display more volume options. If you enable the SnapLock option for the first time, you will be instructed to “Initialize the SnapLock compliance clock” which is required (Figure 3). Click on  “Enable SnapLock” select type “Compliance” and whatever retention period is needed for your companies compliance standards for audit logs. **** Caution if you select 14 years you will not be able to delete conten

Hi everyone!I had a case during this week, and I wanted to share my experience / workaround with y’all.I wanted to export a backup to an external drive, the VBR was a virtual machine, and no access to the Hypervisor to plug the USB and push it to the vm.Now you may think, mount it somewhere and share it over the network as a shared folder…I did, and was not working, some windows stuff that we were not allowed to share any unit, and was driving us crazy!We did some research, and remembered that there was a way to share / mount remote USB Devices over the Network! now, time to give it a shot!The idea is very straight forward, a Server machine, where the USB Devices is located at, and a client, to mount the remote resource as “local”.The tool name is VIRTUALHEREUSB SERVER(Local USB Drive)→NETWORK→USB CLIENT“Remotely mounted USB Drive”You simply download the Server and client, and execute them in the decided machines, couple of easy configs, and you are good to go, let me show you some scr

did anyone encountered this after upgrading to veeam 12.0 it hapend on every tape job:04/06/2023 17:11:47 :: Failed to create backup metadata info: Veeam.Tape.Core.TapeMetaGenerationException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.   at Veeam.Tape.Core.TapeMetaStorage..ctor(CStorage storage, ITapeBackupObjectsCache cache)   at Veeam.Tape.Core.TapeBackupMetaGenerator.GenerateBackupMeta(CBackup tapeBackup, TapeBackup tapeBackupSpecific)   at Veeam.Tape.Core.TapeBackupMetaGenerator.Generate(CBackup tapeBackup, TapeBackup tapeBackupSpecific)   at Veeam.Tape.Core.CTapeVmTaskMetaGeneratorRoot.GetBackupMeta()   at Veeam.Tape.Core.CTapeVmTaskMetaGeneratorRoot.GetSessionMeta(BackupSet backupSet, ITapeDeviceLockManager lockManager, ITapeMediaSetLockManager mediaSetLockManager, TapeExpirationDate expirationDate, ISessionLogger taskLogger, CTapeBackupSetPoint backupSetPoint, ITapeMetaBackup&

Hello guys,One of my customer has encounter the following error message in a backup job.I never saw this message before. The Veeam version is 11 last patch.It’s a linux repository.I asked to my customer to open a support case, but in parallel maybe one of you has already meet this one ?!

Hello, we are monitoring the customer backups via PRTG.Till now, we had a SQL Skript, wich got the latest result and reported it to PRTG:SELECT latest_result FROM bjobs WHERE name = @prtg;That worked fine with MSSQL Express, but now with PostgreSQL we have to use a PostgreSQL Sensor in PRTG. Thats no problem, but it always failes with: “GSS/SSPI authentication but IntegratedSecurity not enabled” when I try to use the postgres user, or with: 28000: SSPI-Authentication for user Administrator failed”. For debugging I tried to change the access settings in the pg_hba.conf file but nothing seems to work.Is there a way I can still run queries to the config database? Or do I have to go via the PowerShell Snappin from Veeam?PS: We don’t use the Enterprise Manager, because you need the Enterprise Plus license for that and our customers don’t have that license. Thanks alot.

Ok, I had a test server which I used to test out Windows Agent backups.I’ve now built a more robust server to handle veeam (community edition as we only have a few servers), when I try to backup the same server, I get:I’ve removed the backup jobs, and uninstalled the agent both using the old server and manually going into Add/Remove programs, yet the same problem exists. I’ve also added the registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication AgentDiscoveryIgnoreOwnership DWORD=1Still no joy.  When I go into the registry editor on the machine in question, I can see why Veeam is having a problem.  The values in BackupServerIPAddress, JobSettings, and VBRServerName are all pointing to the wrong server. I’m loathed to start deleting this key.  What do I do to ensure this server I wish to backup now has the correct agent installed?RegardsIan

A bunch of new vulnerabilities was discovered on Veeam One against the SQL Server connection: You can see all of these on the new Veeam KB4508. Don't hesitate and update your Veeam One environment right now.

Happy monday everyone!Are you considering integrating the feature direct-to-Object Storage into your backup plan, which allows you to add Object Storage as a primary backup repository?Perhaps you'd like to test it locally on-premise first, on a Windows Server environment, without having to purchase, or testing purposes, paid cloud solutions? Or maybe you're specifically seeking a reliable On-Premise Object Storage solution that can also run on a Windows Server?Well, this guide is just for you.In this example I used:VMware ESXi 8.0 U2 Windows Server 2022 VM with 2 disks MinIO 2023-11-15Prepare your Object Storage Windows serverLet's set up and update a Windows Server 2022 VM. Keep it in a Workgroup. Then partition two disks: a smaller one for the OS and a larger one for data. In my example, I allocated 50GB to the OS and 500GB to the data.Visit https://min.io/download#/windows and download the executable.Place that in C:\ and create a PowerShell script with the following code:setx MINIO

Hi there,I would like to share with you that applications for the following 2024 program are open. Existing vExperts and those aspiring to be part of this esteemed community are encouraged to submit their applications for consideration. Similarly, the Cisco Champion program welcomes both current members to reapply and prospective participants to submit their applications for review.For more information on the vExpert program, please take a look at this piece from @victorwu   

A long time ago, my colleague @StefanZi  had provided a Powershell script to create the necessary Azure/Entra appplicaton to be used in Veeam Backup for Microsoft 365. In the meantime, new permission requirements have been added to this application and the Powershell cmdlet AzureAD will also be retired next year (see here), and one of my Powershell scripts also requires the automated creation of an application in Azure/Entra.These were enough reasons for me to update the script. So what's new?- Use of the Microsoft Graph Powershell Module- Revise and add permissions- Adaptations to the text (e.g. adapted product name)- Optimize outputAnd the good news are. Script is ready to use. More details in my GitHub repository here.Enjoy!Steve

HI Community, I am currently using Veaam v12 B&R community edition.I have tried to add a service provider for ekco.I have followed steps from https://www.ek.co/publications/using-veeam-cloud-connect/Once I add veeam.cloudhelix.io and the username and password I get the below error.Is the issue down to the fact I am on community edition V12 or is it an issue from ekco’s side?(I have already logged a ticket with ekco support to see what their response will be) 

1 week ago I had to work during the whole weekend 😉Yes, occasionally some work for customers needs to be done during a maintenance window, often during the weekend, not possible during weekdays.If it doesn’t happen every week and it is possible to schedule it when it suits for yourselves, no problem 😁.Well, last weekend I had to work with a colleague of mine for a customer in a datacenter.Because of the very bad implementation before of the infrastructure (not done by us 🤗), we needed to verify and document the whole setup and every network-connection.Why?We had to turn off the whole Hyper-V cluster, storage, servers, virtual machines, …Afterwards we needed to remove all cabling, reorganize all devices, change the configuration, recabling everything and turn on the infrastructure again.You wouldn’t believe how bad the setup was!!!All went spotless 🤣, it was not our first time we did some project like that : my colleague, a network and firewall specialist and myself a backup, hyperv

Alt Text: Banner graphic displaying the post titleHi,Another quick hint from the field. I’ve seen on multiple occasions that Veeam can get stuck when moving metadata between cache repositories. I needed to move a batch of NAS Cache metadata to a new location, due to a change in Veeam Backup & Replication v12, whereby now it is recommended that you provision no less than 1GB of cache space per 1 million file versions, per backup job. A bit different to some of the previous ‘best practice’ guidelines of ~4GB total!As a quick side note, the Veeam Best Practice documentation now suggests 5% of the source data size as your cache size when using object, but I’m sticking to the Veeam Helpcenter documentation’s 1GB per 1 million file versions guidance, as it’s a good minimum for sizing. The Veeam Best Practice documentation doesn’t always scale well once you’ve got TBs of data. For example: At 50TB of data across 25 million files, your sizing with the best practice starts at 2.5TB of cache

I know I’m late, but spending an extra 4 days in Prague was a blast and the jetlag kicked in hard after being awake over 26 hours coming home! First off, Thanks to @Rick Vanover @Madi.Cristil @safiya @NikolaPejkova  Nikki Adkins, and everyone else for their hard work. As this was my first summit (and first time out of NA) I had no clue what to expect and a bit nervous about the trip. Everything exceeded my expectations from the hotel, the sessions, events, the venues and swag 😄! I already want to go back to EU and explore more.  The flight there was a bit rough. Having someone take their shoes and socks off and bump you with their foot for a few hours is not my idea of a good time, but I was able to keep my cool and power through. I met @Chris.Childerhose and @Matt Crape at the airport which made my trip to the hotel stress free. We were all a bit more tired than expected so the Uber instead of transit was the right call. I was pretty happy with the weather in Prague when I checked my

My question is, if we are excluding SQL data volumes from the original backup job, can we still do full SQL backups and transaction logs using application-aware processing?For some background, in our current state my team is backing up our Windows SQL VMs using a Backup job, then use a Backup Copy job to get those offsite. Since the team has historically ran SQL Agent jobs to do daily full and hourly log backups for each DB they decided to exclude any volumes storing SQL data from the Veeam Backup job. I see the reasoning and I suppose this works, but I’d like to shift to including Veeam on SQL backups so we can easily get those offsite using the existing backup copy jobs.Finally, a sort of related question, if we can use Veeam and the SQL agent jobs in tandem, which one should truncate those? In my testing I’ve had to set the SQL Agent job to copy only mode for things to work, but I feel like setting Veeam to copy only mode should work as well, but I must be missing something since I

Hello to all,As I configure a testing Job with Multiple VMs with the same OS, I can see that there is no difference in the deduplication rate in Report when I run the VM itself alone or in the Group.One more point to ask:The VMs in the Backup Copy Job are all started at the same time when the job starts.Is this how it should be or they need to be run one at a time?

I'm here to show you a little working proof of concept I put together during the Veeam 100 Summit in Prague last week. It's very much a work in progress, but I'm excited to share it with you.(video and callout at the bottom for feedback) Let's dive into the tech stuff and some notes on what we're using.So, we're making use of the Veeam VBR Rest API, as you will know I am a fan of any API especially when it comes to Veeam. The prototype is put together using Node.js. It's like the middleman between the frontend and my VBR server and OpenAI. (we're rocking the gpt-3.5-turbo-0613 model). Although I'm thinking about going with a locally hosted model in the future, especially for sensitive backup server data. But for now, in this prototype and my lab setup, I'm good with this setup, nothing for me to worry about with the few machines I am protecting.For this prototype, I've focused on Backup Jobs and Backup Sessions, and it chats with four VBR Rest API endpoints to make it happen./api/v1/jo

We have configured our backup copy jobs to execute in a continuous mode and hadn’t any issues until the other day.  Ten (out of 100) of our backup copy jobs failed, with the error of “Unable to copy the backup: some backup files are located on an unavailable scale-out repository extent”.  Checking the restore points on the source and target repositories, we noticed the restore points (for the most recent backup) for the target repositories were in an incomplete state.  We performed the following manual steps to resolve; Disable backup copy job After reviewing the target repository from the backup copy job, the identified servers with the error, have the most recent restore point showing incomplete. Rescan the target repository Then process the incomplete restore points by selecting forget Rescan the target repository Enable backup copy job and executeWe did open a support case and the engineer discovered the issue we experienced stemmed from the backup copy job interfering with the bac