Community

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

Hello all,As many of you may have noticed, the VeeamON AMA did not broadcast as scheduled. There were some technical difficulties, and we apologize for that. An update on the new date for the AMA will be shared here once available. Until then, continue checking out the pre-event sessions that are available now on the VeeamON Attendee Portal! https://www.veeam.com/veeamon 

🐱Hello all,  It's less than three weeks until VeeamON Miami 2023! The anticipation is building, and we can feel the excitement in the air!But, before that @Rick Vanover and Product Strategy team have prepared a LIVE Ask Me Anything (AMA) session! Join us on May 11th for a chance to ask any questions you might have about Veeam and VeeamON! Get a sneak peek at the exciting content that will be featured in both the in-person and virtual experiences. Don't miss out on this incredible opportunity to connect with the experts and get the answers you need!Use the link below to register today:  https://connect.veeam.com/flow/veeam/veeamon2023/attendeeportal/page/sessioncatalog/session/1678240245854001tCwA Best, Madi

Hi,We have published VBR plugin to a tenant in VMWare vCloud director for VBR v12. It was successfully published, roles and self service configured. However, when i log into customer tenant from vCloud director and goto veeam protection under more. it pops up Error "Unable to connect to the Veeam backup infrastructure. Please contact service provider". Thanks.Best Regards,Farhan Ali

I have a problem when I tried to use quick migration jobError shows2023/5/5 下午 05:21:18 :: Copying snapshot files Error: Failed to open VDDK disk [*********] DRAP/AP.vmdk] ( is read-only mode - [false] )Logon attempt with parameters [VC/ESX: [XX.XX.XXX.X];Port: 902;Login: [root];VMX Spec: [moref=71];Snapshot mor: [71-snapshot-1];Transports: [nbd];Read Only: [false]] failed because of the following errors:Failed to open disk for write.Failed to download disk 'vddkConnSpec>'.Agent failed to process method {DataTransfer.SyncDisk}.  2023/5/5 下午 05:22:57 :: Failed to process VM DRAP at Friday, May 05, 2023 17:22:57 Error: Failed to open VDDK disk [*********] DRAP/AP.vmdk] ( is read-only mode - [false] )Logon attempt with parameters [VC/ESX: [XX.XX.XXX.X];Port: 902;Login: [root];VMX Spec: [moref=71];Snapshot mor: [71-snapshot-1];Transports: [nbd];Read Only: [false]] failed because of the following errors:Failed to open disk for write.Failed to download disk 'vddkConnSpec>'.Agent failed

Guys, I don’t know if everyone is aware, but VMware has this course for free until 06/15/2023: https://learning.customerconnect.vmware.com/site/program.do?dispatch=showProgramSession&id=18657ec2-4eb2-11ed-b5a6-0cc47a352292You also win 1.500 points in VMware Reward and a chance to win a VCP Exam voucher.More information here: https://blogs.vmware.com/learning/2023/04/27/invest-in-your-cloud-skills-and-earn-1500-rewards-points/

VMware vSphere logoRecently VMware released Update 1 for both VMware vCenter and ESXi. I successfully upgraded my vCenter but had to wait on the ESXi hosts until the VMware USB NIC Fling was updated to be compatible with Update 1. It is now updated and can be downloaded from here – VMware USB NIC FlingI downloaded the fling and the Update1 ZIP file from the VMware site that I could run on the CLI of each host after enabling SSH. So I connected to my hosts via the Web UI, logged in and enabled SSH. I then used Mobaxterm to connect to each of my hosts.The steps at a high level to upgrade are as follows –Remove the current USB Fling driver from each host Reboot the host to complete the VIB removal Enable SSH again on each host Run the CLI command to process the Update1 ZIP file on each host Reboot each host to ensure Update 1 is applied Enable SSH again on each host Install the USB NIC Fling for Update 1 Reboot each host to ensure the drivers are loaded Check the Web UI to ensure the USB

"Mastering Veeam Backup & Replication 12 - Third Edition" is now in publication (since April 2023) and is ready to order either the book or e-book/kindle.Well, since writing my first book on v10 and my second one on v11, I debated to myself about writing the update of the book to v12.  It took me some time to process and think about if I wanted to do it, and after attending VeeamON 2022 in Las Vegas, where v12 was introduced, it got me excited, and I then took the plunge.  This time, the process was much smoother as I had already done the first & second books and understood the templates, formatting, etc.  The team at Packt worked with me again and my busy schedule to create something I think that everyone will enjoy reading.  Whether you are a newbie with Veeam or a seasoned expert, you can learn something from this book.Veeam 12 best practices: design and deploy a secure and resilient platformKey FeaturesGain in-depth knowledge of Core Architecture Changes, including PostgreS

Hello! In this topic I would like to cover the steps to change the default Veeam Backup for Azure worker disk size.There are some scenarios where you need to increase the volume size of the worker depending on the size of your protected VM. This change must be done via restAPI, so one of the options we have is using Swagger, which is the restAPI tool built-in the VB for Azure appliance.You can refer to this page on user guide to find detailed steps to authenticate Swagger. As soon as you are properly authenticated in Swagger you need to find and expand the Workers method: Locate the endpoint: api/v4/workers/profiles/{regionId} and click on Try it OutIn the request body, these are some of the parameters you can use:In this case we will not configure worker profiles per VM size, so we will use only the Simple type and Archive type since they are mandatory if not using different profiles.You can find more information about worker profiles here. Fill out the body request as follows:{ "min