Community

I wanted to share this just incase it helps someone else. I was getting the following errors in Veeam B&R Community Edition 12.0.0.1420 when trying to add/rescan one of my eight Hyper-V hosts. These started occuring when moving towards a full block on NTLM in our environment.Disks and volumes discovery failed Error: A security package specific error occurred. RPC function call failed. Function name: [GetSvcVersion]. Target machine: Network path not found or invalid credentials supplied.I verified DNS was good, disabled firewalls, enabled NetBIOS over TCP/IP, among other things. None of these helped.What ended up fixing this, was enabling the “This account supports Kerberos 128/256 bit encryption” on our Active Directory user that services Veeam. I’m not sure why they other hosts were fine, but this fixed the final one and should have been done anyways.

Hello,With Veeam Agent for Microsoft Windows FREE edition, I wonder if there’s a way to test the encryption key? I tried removing job but when restoring it still didn’t ask for password.And, can I re-add job after removing it or add the current jobs to another PC?Thanks

As you may know, with vSphere 7 Update 1 VMware introduced the vSphere Clustering Service.The plan is to get more independent of vCenter Server for certain cluster features like for example DRS.Where you certainly notice the difference, compared to older releases, are the vCLS agent VMs shown in vCenter.https://blogs.vmware.com/vsphere/2020/09/vsphere-7-update-1-vsphere-clustering-service-vcls.htmlThere's no need to backup them and if you have a current Veeam version (v10a Patch 20201202 or higher), they're are automatically excluded from your jobs.The agent VMs are manged by vCenter and normally you should not need to look after them.Normally…yesterday we've had the case were some of the vCLS VMs were shown as disconnected; like in this screenshot:Checking the datastore we have noticed that those agents VM had been deployed to the Veeam vPower NFS datastore.As this datastore is managed by the Veeam server and can connect/disconnect at any time, it's a very bad location for the vCLS VM

To back up data from M365 one can pre-create an app within AzureAD and connect via a certificate from VBM. Then no additional login to M365 is necessary:Step 5. Register or Select Azure AD Application - Veeam Backup for Microsoft 365 GuideKeep in mind that you do not need to select this check box if you have granted the required permissions to the specified Azure AD application beforehand and already registered its certificate in Azure Active Directory. If the Grant this application required permissions and register its certificate in Azure AD check box is not selected, Veeam Backup for Microsoft 365 skips the Log in to Microsoft 365 step and proceeds to Finish Working With Wizard.But once you want to restore back to M365 things change: From within Exchange Explorer, you are prompted to do the device flow login with e.g. an Exchange admin to restore mail objects.Though while deploying the AzureAD-App an impersonation user was already specified. Is there a way to pre-define rights to th

Hard disk 20 (3.5 TB) 1.9 TB read at 41 MB/s [CBT] - Can anyone tell me how long it should take this disk to complete backups? The backup ran for 13:21 hrs and failed to complete due to backup window setting. The backup window for the job is set for 15 hours 5pm - 8am. In addition how can i confirm if  a FULL or Incremental backup is running for a VM that failed backup.Backup type is VMware Image Backup. 

Hi Folks, Next in my “Beware” series 😂.. Beware of podiums. Why? Because podiums are generally slanted. So if you have practiced your presentation over and over again at your desk, and your presentation involves CLI work (think Kubernetes Kubeclt or K if you using aliases) then you will be entering a world of fun since you fingers are used to typing on a keyboard that is flat and not slanted. I got used to it but I was nevertheless struck by shame. The typos were flowing and I could just hear the audience whispering, “wow this person can’t type, and he is too old too blame the cell phone thumb typing condition like all of the younger generation do”.  My poor High School Grade 10 typing teacher would be heart broken. She disliked me so much for goofing off in class that she would force me to stay after and finish the tasks which in turn massively improved my typing skills. However, when doing live presentations in front of people, no matter how badly you mess up (be it typing, or lousy

We have a file server that we are going to backup directly to an S3 compatible storage with immutability enabled.We want to put an incremental backup with full synthetic.Is full synthetic already compatible with S3 immutability with direct object storage?What do you recommend for the least resource consuming backup type? Thank you very much.

Hi Folks, I recently was lucky enough to be chosen as an Auth0 Ambassador. However, I am still very much on the initial learning curve when it comes to identity management so have signed up to a few udemy courses and pulled out the documentation. When starting a new path it is always nice to take your first steps in familiar territory so I decided to try out leveraging SAML2.0 for Veeam Enterprise Manager. First we need to create a free Okta developer account: Then we will create a new app integration: VEM (Veeam Enterprise Manager supports SAML 2.0 so that will be our choice here:We need to give it a name:Next we need to enter our SAML settings. I used a laptop where I have a test VBR setup:These two settings (Single Sign On URL and Audience URI can be found in VEM here after you have ticked the Enable SAML 2.0 radio box. Don’t worry about the other settings we will import them later. Save the SAML settings in Okta then open up the App page: Further down on the right hand side you wil

I have 2 Veeam V11 VBR servers. Which backup different servers. Servers are mostly VMWare, Windows/Linux and some Agent backups. No NFS/CIFS/ network share backups. At one point in time, these were 2 VBR servers in 2 separate data-centers but these data-centers got merged so now they’re located in the same data-center. They each use backup copy jobs to offload backups to Azure. For Azure, they’re using the same account, but upload to a different folder. Both servers have different proxies and different backup repositories. Backup repo’s are a combo of Windows and Linux (immutable). Each server uses a different SQL (server 2019)  back-end. Now, the idea is, to upgrade Veeam to V12 and merge these 2 V11 VBR servers into one V12 VBR server. Is this even possible? An upgrade to V12 can either done on the existing servers and then merge or I could build a new VBR server, install Veeam V12 and migrate both servers to the new one. The on-prem jobs cover about 15 days or so, so I could just se

Hey Everyone,A big evening in Toronto IT yesterday and Veeam was there. First @michaelcade and I went to Okta to take part in their Devday23 event (got some nice swag too!), then we had dinner with @Julia F Morgadoand headed to the Pre Kubehuddle meetup where I met some Kubernetes royalty! Of course everyone knew Julia and MIchael so I just used the occasion to shamelessly introduce myself :) . Joking aside I have to note Veeam/Kasten is making its presence felt! I saw no other backup vendors anywhere near these two events. Kubehuddle has  literally a Veeam invasion happening with Julia Morgado, Cassandra Farris, Michael Cade and of course humbly representing the Vanguard/Legend community me :). I believe these efforts are well worth it and are going to pay off. When people need backup in the Kubernetes community there first thought will be Veeam/Kasten! 

Hi everyone.If you missed it, Microsoft just released H1 2023 for Exchange Server 2019. Included in this release is the ability to use Modern Authentication in an Exchange Server only environment. In Case You Missed it, What is Modern Authentication? There are numerous resources describing the functionality of Modern Authentication in technical detail, but my goal here is to provide a conceptual overview of Basic Authentication vs Modern Authentication. Basic AuthenticationBasic Authentication, as the name might suggest, is a simplistic form of authentication. A client attempts to communicate to a resource that is protected, and the resource requests a username & password, you supply a valid username & password, and you’re granted access to the resource. Every time you want to access this resource, you need to provide the username & password. This was actually one of the main driving forces behind security considerations such as mandating HTTPS on websites, to avoid credent

 I’m returning to the VeeamON (virtual) stage this year, and I wanted to catalogue my journey within the Veeam Community so far and give thanks to the people that have helped me get to where I am today.I’d been working with Veeam products for about 7-8 years at the time, and I’d seen the Veeam Forums, now known as the Veeam R&D forums. I’d asked a few questions in there, but it never really felt like a community. The relationship within the forums was that of a customer and business. Someone would seek advice with a problem, or request a feature, and a member of staff from the Veeam forums would reply. Very transactional.Then, during the infamous lockdowns of 2020, Veeam launched their “Veeam Live” Event. During this event, Veeam revealed their new “Community Hub”. I remember frantically writing down the URL “community.veeam.com”. And I had no idea at the time how much my career was about to elevate.As the event concluded, I opened the URL to see if this was a long-standing platfor

Just want to run this by all the Service Provider Gurus here. It seems that for Multi-tenant O365 Veeam no longer wants you to place the console on the Cloud Connect server. Instead you install it separately and have it connected to the VSPC and expose a portal for restores. The old method of having the CC tenants go through the SP in the local VBR server is not seen as the optimal option. This diagram from the BP would suggest this:  Does that sound correct? I have been away from O365 for a bit now and the world is changing.

I found out there is a difference in the allowed number of active extents for an SOBR in VBR Enterprise Edition which could cause your backups to fail after upgrading from v11 to v12.This is the documentation for v11 (3 active extents max.):  And this is the documentation for v12 (2 active extents max.):  This is not mentioned in the release notes and it turns out you don’t get a warning during the upgrade.I raised Support Case 06063519 for this issue, this is the response from Veeam Support: I understand that the change in the policy is not desirable, but unfortunately, I'm not able to comment on the decision process behind this; and regrettably, I have tested in lab to upgrade a v11 Veeam environment that violated the new SOBR limitations, and I did not receive a warning during upgrade either.I am sorry to hear that this situation occurred, as historically Veeam has tried to be very transparent in all such matters, but I'm afraid that I cannot find where it was advertised.I have alre

Hi Folks, Off topic but I think worth mentioning. I had a discussion with a fellow presenter at KubeHuddle this weekend. This person has achieved a lot more than me in the Kubernetes and IT world and I have a genuine respect for them. What struck me during our conversation was an apparent lack of ego in my partner’s interactions. There was not even the slightest nuance of bragging or self aggrandisement. At one point I said “you must be very proud about having achieved so much”. To my great surprise the response was very placid. “only the insecure and fools make great importance of their achievements, a bucket that is empty is easily filled with any liquid until it overflows, but a pipe conducts the liquid through and the liquid does not spill, be the pipe not the bucket”I put down the response to the person coming from a very different cultural background than mine. After all I grew up in the Canadian/American “push push, go  harder harder, work more more, stand above the rest culture

More of a note about an effect I experienced using the new Microsoft Purview Compliance tool for Data Lifecycle Management and Retention Policies.We are new to M365, and are still migrating to it. As part of the setup before I started migrating, I did create a “Default Retention Policy” in Microsoft Purview for Exchange objects. I started migrating, setup Veeam M365 Backup to protect the migrated mailboxes, and all was good.As we expanded our use of M365, I reviewed the “Default Retention Policy” and learned a few more things about it. Long and short of the story, the default policy I had created was not applying to anything (for reasons undetermined). I deleted the retention policy and recreated it and all heck broke lose as the Purview retention policy applied.At this stage of our migration, roughly 1 TB of mail had been migrated, and our “every 30 minute” Veeam snapshots were keeping up easily.After the Default Retention Policy started applying to all of the migrated mail, the next

env:1、vbr11a、vspc6、backup server（win2022） with backup agent success。2、upgrade to vbr12、vspc7。3、backup server（2022） with bakcup agent failed。4、no Capacity/Archive tier，just back up to vbr local disk.5、Only two Servers（vbr + vspc）。

One thing I really miss from other backup products I have managed, more detail displayed about what an active job is doing.  For example, a running Backup for 365 is taking a really long time.  The whole job summary says how many objects it has processed, number of items processed and the data transferred.But it does not show the same details in the actions. It only shows the name of the item and how long it is taking.  It would be really handy to know how many items and how much data has been transferred at the object level. Would help me understand what is going on and would allow me to investigate what changed to prompt a difference in backup times. 

So we're 7 days out from the big day, and thought we could put a collaborative Spotify playlist together for the event. I've added a couple of obvious tracks, but feel free to add more relevant tracks. Let's get an amazing playlist to match an amazing event.https://open.spotify.com/playlist/2iVGkhPztcEQyW7BrNJYGd?si=6a29d22cae4349d2

A few weeks ago I started to build my agenda for VeeamON 2023 in Miami. As there’s lots of interesting content covering various topics, it wasn’t easy at all to decide which sessions to attend. With over 130 sessions, I had conflicting schedules and so had to leave out some of those. This was especially hard as all sessions offer valuable knowledge, so I hope that recordings of most of them will be available after VeeamON.With this post I want to highlight ‘just some’ of the sessions I’ve picked for my agenda. There are much more great sessions, more that I could list here, so be sure you check the complete agenda.In-Person10 Years Working with Veeam: How it Helped Shape Our Careers All Demo Session for Veeam Hardened Repository Architecting Veeam Backup for Microsoft 365 at Scale A-Z Automation Journey with Veeam’s Automation Desk QuizMania – Veeam 100 against the World Ransomware Recovery Unplugged Tape Your Data Now! Veeam Backup & Replication v12 Hidden Features Veeam Repositor

Any idea for this? It’s pure Hyper-V with Azure, not AWS. 1/31/2023 10:06:49 AM Warning Failed to connect to AWS plug-in: Failed to login to platform service: The HTTP resource that matches the request URI 'https://vbr11:9402/api/v1/account/login' is not supported.  

HiWe running an VBR11.0.1.1261 using SOBR with an QNAP as capacity tier. QNAP is supported S3 repository by Veeam and Veeam is partnering with QNAP. Also Immutable option should work as stated in https://www.veeam.com/sys469.After running while this setup we start getting strange errors.  Error deleting multiple items from SOBR invalid URI - which refers to cleanup operations on the S3 repository base on retention policy. VBR runs this operations in regular intervals.  In Veeam One - Data Protection View we get error type [v] (never seen before) and a Knowledge information that stats: S3 object storage added to VBR as repository may face overflow with small metadata file of 0 kb size. Cause: malfunction in object delete algorithm. Resolution - contact support to get a private fix. To get backups to SOBR working again we to delete objects from QNAP using qnap utilities. Now we try to synchronise SOBR with VBR DB but it takes forever. Has somebody came across this situation with AWS S3 o