Blogs and Podcasts

With v12 it will be supported to use group Managed Service Account (gMSA) for user credentials.For my understanding of gMSA it will be necessary to have VBR server in a domain. Because it will still not be recommended to join this server the production domain, a special resource or management domain could be needed. For more details we will have to wait for general availability to get the user guide.If you have more ideas about gMSA implementation, let us know 😀

You might or might not know this, but Wasabi does have a minimum storage duration policy in place.What's that?Depending on your pricing model, each uploaded object will be billed for a minimum amount of time.Pay-as-you-go customers have 90 days, reserved capacity customers (pre-paid) will have 30 days.If you delete an object before this minimum duration is over, the remaining time will still be charged.You can find more information on this website:https://wasabi-support.zendesk.com/hc/en-us/articles/360058734492-How-does-Wasabi-s-minimum-storage-duration-policy-work-ExampleYou upload 1TB of objects to Wasabi and have the 90 days minimum storage duration policy in place. After a week you decide to delete the whole 1TB.This means you pay for:7 days timed active storage 83 days timed deleted storage

I had a discussion recently about backing up ‘standalone’ ESXi servers, without the vCenter Server application. The discussion started around we were sharing my homelab but the use case became attractive for retail, edge and other ROBO scenarios. Why no vCenter Server Application?I do not run the vCenter Server Server Appliance (vCSA) at home simply because I don’t need it. At home I recently simplified my home lab. In March and April, I had to work from home for a while and it made me think about the home lab since I wasn’t travelling. I upgraded to a new host (still on vSphere) but really don’t need the vCSA. I do *not* use the free ESXi hypervisor, as I use the vExpert license on the host to unlock the full APIs that I need for backup. In our work lab environment, we definitely use the VCSA

Over the last several years Microsoft has been moving into Microsoft 365 with their services. With this migration they have introduced many new features into the eco system to make day to day communication and processes smoother. In this same transition Microsoft has also moved to depreciate legacy technologies for newer features that are purpose built for the ecosystem and modern data communication. We are in the process of what is now the second depreciation cycle of legacy technologies in Microsoft 365. The first being when on-prem services did not make it to the cloud and now with the deprecation of legacy APIs on January 31, 2023. Its important to note that depreciated does not mean these services are nasally going to be shut off but further support by Microsoft and third-party access to these services will also be limited if at all. In this case, services in Microsoft 365 that did not make the cut, by Microsoft, to be coded into the Microsoft Graph API with modern APIs will no

Just a quick reminder to everyone that all good things must end at some point. The following products will no longer be supported by Veeam from the 1st January 2022.Veeam Backup & Replication 9.x Veeam ONE 9.x Veeam Disaster Recovery Orchestrator 2.0 (Formerly known as Veeam Availability Orchestrator) Veeam Agent for Microsoft Windows v3 Veeam Agent for Linux v3Also in the near future is the end of support for the following products:Veeam Service Provider Console v3 (March 2022) Veeam Backup for Microsoft Office 365 v3 (April 2022) Veeam Backup for Microsoft Office 365 v4 (November 2022)You may be thinking “I haven’t seen an update for a long time for these products, I thought it was end of life anyway”. That’s because Veeam have a two-stage sunset policy for support. Stage One: End of FixWhen a Veeam product reaches end of fix,

See here how it works in a step by step guide.To start in Instant SQL Recovery wizard, select your server and choose Restore application items.Here you choose if you want to restore to the latest available restore point, or select a listed one. At the end of wizard press Browse. Veeam Explorer for Microsoft SQL Server starts.Choose the database you want instantly recovered and select to do so. You have these options to choose from: Latest restore point. Point-in-time state. Recover to another server. This you can used to recover DB using a different name while original DB is still in place. In this dem

Hi,In this topic I want to highlight the possibilities to archive a backup for a VM before you want to delete or decommision.Every company that uses VMs has to deal with deleting existing VMs, replacing them with new VMs because of migrating the application running on the VM, migrating because of using a new OS on the VM, …A lot of reasons why existing VMs will soon or later will be deleted or replaced by new ones. What do you want to do as a proper engineer before deleting the old VM? → Of course, you first want to take a backup before deleting the VM.I often had the situation where the customer needs something being restored/recovered of the deleted VM 😊Personally the best way for a VM that will be deleted, is having an independent full backup. Is that possible with

The new official capacity calculator for O365 is now live at https://calculator.veeam.com/vbo/You can either connect it to your real account and retrieve needed data or manually input data:If you love the full details you can click the “Show details” button:This will definitely make it a lot easier to estimate capacity use, but also size VBO servers and proxies, just click on the little “i” icon next to infrastructure sizing for even more information like CPU/memory:

Veeam Backup & Replication supports and understands vSphere tags allowing the creation of Backup and Replication Jobs by selecting VMs to backup based on Tags.Tags concept was introduced in vSphere 5.5 and basically it is a label you can assign to any object (VMs, storage and so on...) in the vSphere inventory. You can assign a tag to a specific category to better identify a VM type or simply the installed OS.The use of Tags during Jobs configuration is pretty easy to configure. In the configuration wizard click Add button to add objects to backup. Click the tag icon to display VMs and Tags, select the item you want to include in the job then click Add.Using Tags you no longer need to edit a specific Backup or Replication Jo

Hi CommunityToday I’ve spent my time in our lab and I realised I made a mistake by choosing a bucket without immutability in our backup job.So I dedicated some time looking into how I could move backups to another repository in Veeam B&R Console.Before I started, I wondered why I would want to use the 'Move backup' function in a production environment.I said to myself that it might be necessary to do this in such cases as: Wrong configuration in a backup job Backup repository is close to full capacity. I must replace my repository (because out of warranty). Backup job policies are changed (immutable backup request or different policy needed). “Move Backup” operation permit to continue to use the same Job, moving backup files to a new backup location, and keeping job history and backup chain. SCENARIOIn our lab we have this scenario:

​In the first part of this three part blogpost we’ve discussed why to use gMSAs to achieve application consistency before backing up our workloads with Veeam Backup and Replication (VBR).In this part I will show you, how easy it can be implemented with VBR and how the process differs from the official manual.  (1) Ensure your forest schema is updated to (at least) Windows 2012 (Version 56+)First,

IntroductionObject storage vendors all have configuration considerations that must be accounted for as part of the process of designing Veeam backup repositories. Some of these considerations can be limiting, while others simply help dictate architecture decisions. In this post, I discuss on-premises vendor considerations, and how Veeam job settings can make an impact.To accommodate for vendor specific on-premises Object Storage Device limitations, it is sometimes necessary to adjust Veeam’s storage optimization settings. Every on-premises Object Storage vendor may express these limitations differently, but it usually boils down to the ability to handle large amounts of object metadata (and therefore number of objects) per bucket and/or device.In our experience, using larger storage optimization settings (job block size) with on-premises Object Storage devices typically works b

Hi folks,My wanderings in the wonderful continue. I need to move an M365 repo from a REFS drive (as far as I know this is not good, NTFS is the best practice) to a new drive. I have read on the forums that the Move-VBOEntityData powershell is NOT the way to go. Instead this is the procedure: 1. Disable all backup jobs related to the repository you want to move.2. Stop all the Veeam Backup for Microsoft Office 365 services before moving any data.3. Copy the backup repository data to the backup repository location on the new repository location (using robocopy for example).4. Start the Veeam Backup for Microsoft Office 365 services.5. Add the new repository with the moved data.6. Open backup job settings and specify to use the new repository Any comments or advice from folks who have been through this. I would like to avoid any pain since I had a wisdom tooth pulled this week and have enough already :)  cheers

It’s the year of Linux!!! Well, at least for me it is. 😉 I’ve used a decent amount of Linux CLI over the years in managing vSphere environments, but not learned near as much as I wanted to. I always felt a void in my depth of knowledge & expertise about Linux. So I started this year going all in with LFCSA (Linux Foundation Certified Systems Administration) video courses on Pluralsight, learning about Linux Storage, Operations, Users & Groups, Service, and Network Management.Because I’m way more comfortable now using Linux, I’m planning on implementing Linux systems as Veeam Backup components in my environment to decrease the heightened security risk Windows systems tend to pose. As such, I’ve been reading up on Linux implementation in Veeam’s User Guides, starting with the Veeam Agent for Linux (VAL) User Guide. I thought I would share my Linux Agent journey from Preparation, to Install/Implementation, to “Hiccups” encountered, to Backup Success with the Communi

Hi  have currently this warning for 3 consecutive days. the backup jobs ara all success but I getthis warning message . can any one help me resolve thisWarning message:>>>>>>>>>>>>>>>>>>>>>>>8/31/2023 10:00:51 AM Warning Failed to connect to GCP plug-in: Failed to login to platform service: No connection could be made because the target machine actively refused it xx.xx.xx.10x:9xxThnanks in advance>>>>>>>>>>>>>>>»  

UPDATE: Please see Update 3, as the hotfix/workaround needs to be undone because of possible side-effects.Just a quick information.Currently there could be an issue with Veeam Backup for Microsoft 365 and Sharepoint. Some sites will be backed up with the following warning:Processing site XYZ finished with warning: Failed to backup list: XYZ. Unknown ErrorI have seen this with 2 different customers and Veeam support is aware of this issue and actively working with Microsoft on it. At the moment I don’t have any further information, but I’ll keep updating this post.Update 1:I just found out that there's already a hotfix available: https://www.veeam.com/kb4326I haven't tested it so far, but will report back next week. Also here

 Hi all, I share the lab I created to test the CDP feature.HW List:VmwareServer: 4 UCSC-C220-M5SX - VMware ESXi, 6.5.0, 15256549 VCSA 6.7.0 15129973 Storage: Dell Storage SC 5020 VBR+CDP-Proxy Source 1x4 vCPU – 16 Gb RAM CDP-Proxy Target 1x4 vCPU – 16 GB RAM System Requirements - User Guide for VMware vSphere (veeam.com) Requirements and Limitations - User Guide for VMware vSphere (veeam.com)

I’ve created a migration guide for moving from Veeam Backup for Microsoft 365 version 7 to version 8.  As you know, version 8 introduces a lot of new changes in the technology and architecture - like postgres database, centralized cache, and proxy pools.  This document will walk through the process of upgrading from v7 to v8, and migrating standalone proxies into the new proxy pools.  Be sure to take care around a “next next next” install, as now with Postgres and NATS, that’s additional workload on the VB365 controller.  It’s recommended to separate out the DB server from the VB365 server outside of the smaller deployments.

 Hello everyone,I want to share the tests performed on Beta 12.1.0.1944. From the installation of the PostgreSQL Database to VBR12.1, with a focus on the new Security & Compliance features introduced in this release. This version is particularly interesting for the introduction of new features dedicated to the security of the backup infrastructure and the related data protection.Planning and Preparation - User Guide for VMware vSphere (veeam.com) Prepare the virtual machine with requirements according to the needs of your infrastructure.Vmware Side:NEVER use a vmdk disk as a backup repository in production.Add new Disk ( vmdk for only test) for dedicate d repository NVMe Controller.

Sizing for NAS/file share backup can appear difficult initially, but with the help of the unofficial NAS Calculator by Hal Yaman it definitely will be a bit easier.As you can see from the screenshot below you need to know roughly how much source data in TB your file share(s) contain, how many files and directories. In case you are wondering what is primary vs secondary repository? Primary is for your short term retention (newest version) and secondary is for long term retention (older versions than newest).The user guide has some good info on the secondary copy settings.

Hot off the presses! Today, we’re announcing the general availability of the newest entry to our long list of supported hypervisors, with the addition of Oracle Linux Virtualization Manager. As some of you may be aware, Veeam Backup & Replication has been supporting Red Hat Virtualization for several years now, which runs oVirt and KVM under the hood. Although Red Hat has stopped development on RHV in favor of OpenShift, Veeam Backup & Replication will continue supporting RHV as a source until December 2026.But let’s focus on what’s new: Oracle Linux Virtualization Manager support as a source. The process to get up and running is straightforward: just download the oVirt KVM plug-in and install it on your VBR server. Once completed, you can head back into the console and go to Inventory --> Add Server, and you’ll now see Oracle Linux KVM listed as an opt

Today I want to share a sneak peek at the next release of Veeam Backup for Microsoft 365, v6a. Like traditional minor/interim releases, this release will mainly include bug fixes. However, there’s an interesting feature being released that I’ll be sharing some details on. Goodbye Exchange, Hello Teams Export APITo understand what’s changing, we need to understand what is going, and why this change is necessary. Currently, Veeam are protecting Teams channel ‘chat’ data via Exchange Online. Notice I say Teams channel, currently Veeam doesn’t protect any ‘Direct Messages’, either 1:1 or group chats, so chat in this context refers to posts and comments within a Teams channel. How does Veeam currently process my Teams data?To achieve the protection of this Teams data, Veeam reads a hidden folder within Exchan

Veeam Backup for Microsoft Office 365 Calculator(Download: VBO-Calculator-Community-1Download)Welcome back after a longer break due to holidays, personal changes and some challenges over the last weeks.As one of the main responsible german Systems Engineer for Veeam Backup for Microsoft Office 365 (VBO) I received a lot of questions and requests regarding the right sizing for a VBO-environment as well as for the “new” Object Storage Repository feature, which is available since version 4.Wouldn’t it be great if we had a tool for this ? For sure ! But let us first build up some tension. Before we concentrate on object storage I will give you some important information for your general VBO-Sizing. The SizingWhat do you need for a proper sizing?To get some r

IntroductionIn a previous post, I covered the SOBR Capacity tier Calculations and Considerations. Today, I will be exploring the Archive tier and discuss how to estimate Archive storage requirements, expected API calls and Proxy Appliance uptime. Before we jump into more details, remember that the Archive tier only works with “Amazon S3 Glacier”, “Amazon S3 Glacier Deep Archive” and “Microsoft Azure Archive Storage” in Veeam v11. In the SOBR config

This is part two of the blogpost. Part one can be found here: SOBR Archive Tier – Explained and Configured – Part 1 of 4 | Veeam Community Resource HubIn this part will will discuss the reason behind having different tiers and how they appear within Microsoft Azure. Hot or Cool? – what’s it all aboutS3 storage or blob storage as it is also called is offered by the hyperscalers in various flavors that basically differ in speed of access and the cost charged for the in- or egress of data as well as its storage. We can generally decide between hot, cool and archive for Microsoft Azure. This translates to Standard and Standard-IA (=infrequently accessed) with Amazon AWS. The concept behind is the same. In the following I will stick to the terminology as of Azure.The capacity tier of t