Blogs and Podcasts

I hope, this post safes you the time I spent to figure this out.Normally I do not install Veeam Enterprise Manager (EM) unless there is a use case - like indexed file search. With it, EM can search a index - created at backup time. So no mount of restore-points is necessary to find files in backups. For more information see here:https://helpcenter.veeam.com/docs/backup/em/understanding_search.html?ver=110According to my knowledge, index search is able to lists all file-versions in selected time range. For this you have to filter your search:ProblemIn multiple VBR v11 + EM environments I had the situation that index search results shows just latest file version in result. I spent some time to troubleshoot, ask colleagues, recherche. Finally I get an answer in R&D forum:https://forums.veeam.com/veeam-backup-replication-f2/search-not-behaving-like-i-would-expect-t72642.htmlShort answerIndexed search should show all file versions. This feature is broken in v11 and will be fixed. 

As promised part 2 of a 2-part topic regarding rotating USB disks 😉.But after writing this topic I had to devide it 2 separate parts because of the limitation of 50.000 characters 🤣😏 You can read the first part in OFFLINE backup copy using rotating USB disks – part 1 | Veeam Community Resource Hub As already mentioned in part 1, using rotated USB disks is a possible and affordable way to have an offline or airgapped backup copy. If you keep them offsite, the two times 1 of the golden 3-2-1-1-0 has been completed!In this part I will go a bit deeper in this topic.I will split it into 4 sections : LimitationsWhen using a repository with the rotating drive option, you have some limitations you have to keep in mind. Those are :On one managed server, you must create only one repository with rotated drives It is NOT possible to store archive full backups (GFS) with backup or backup copy jobs It is NOT possible to use per-VM backup files It is NOT possible to rescan the backup repository NF

Today I received a great surprise in my email from Madalina Cristil (@MadiCristil), the manager of the Veeam Community Legends program, and Rick Vanover (@rickvanover) that I was renewed into the 2022 second intake.You can find out about the Veeam Legends program on the Community Hub here - Veeam Community Hub.It has been a great first year in the Legends program, and I was happy to contribute to helping the community. I look forward to another year and meeting many of the Legends in person at the #Veeam100 event in October.There are some great benefits to being a Legend -As a part of Veeam Legends, you’ll be eligible for unique content, NFR licenses, private betas, prelaunch briefings, Veeam R&D insights and, of course, awesome Veeam Legends swag!But one of the most significant benefits is being part of a community to share knowledge, experience, tips, tricks, etc.  I know this from already being in the Veeam Vanguard program for the past five years.So if you are interested, check

One of the things that we have in all our projects and backup environments are Backups Jobs.After deploying all components and servers on our Veeam infrastructure, the first thing that we do is the creation of our backup jobs.Thinking of that, I write this post telling you what is the main nomenclatures that I’ve been used on my Veeam Backup & Replication. B2D - Backup to DiskBackup jobs that we use to send data to any disk repository. B2T - Backup to TapeBackup jobs that we use to send data to tape libraries. B2C - Backup to CloudBackup jobs that we use to send data to cloud. On V11 we need a SOBR to send data to public cloud like AWS, Azure and GCP. However, if we have a Veeam Cloud Connect repository, we can send data to this kind of 'cloud' and use B2C name on backup job. BC - Backup CopyBackup copy jobs we often use to make one or more copies of data between repositories or sites. LTR - Longe Term RetentionBackup copy jobs we can have to attend a long-term retention on data ar

As a system consultant I often implement solutions for customers in the SMB market.Working for the SMB market is often more challenging than working for the enterprise market because of the limited financial budget/investment. I always try to deliver a solution that is as good and secure as for customers of the enterprise market but of course with other and cheaper solutions 😉. Of course VEEAM is always being used as the software defined backup solution 😊. For me personally the golden 3-2-1-1-0 rule is one of the most important things to keep in mind when creating a good backup solution for the customer.More info about that you can read in one of my first posts : 3-2-1-1-0 Golden Backup Rule | Veeam Community Resource Hub In this post (part 1 of 2 parts) I explain a bit more about implementing the second 1 in the rule – offline backup.One of the solutions is using rotating USB disks.This is specifically for backups of VMs and/or backups using agents of physical/cloud objects.In part

Just two weeks after the release of Veeam 365 version 6a, Veeam has released the first cumulative patch P20220825 (build 6.1.0.254). This patch fixes two issues which have been discovered in the 6a GA release. While, according to Veeam, those issues only affect less then 1% of the v6a users, it’s still recommended to install the patch. A backup of Security groups, Distribution groups, M365 groups, and specific users may complete with the warning: Nothing to process When this occurs no restore point is created for such objects.Note: Depending on the job configuration, the job may complete with a Success status, and the problem may occur unseen Under certain conditions, a backup job that includes SharePoint, OneDrive, or Microsoft Teams objects may run longer than expected, and the processing of lists may complete with the warning: Failed to analyze list changes. Value does not fall within the expected range. For more information and to download the patch, visit the following KB: https:

I case you haven’t seen. There are currently two ongoing surveys from Veeam; one about the Help Center and the documentations, the other one about the livestreams (Industry Insights, TechBytes). So in case you want to share some feedback on those topics, here’s your chance:Veeam Help Center: https://www.surveymonkey.com/r/JFBXD2HVeeam Livestreams: https://www.surveymonkey.com/r/VeeamStream22A Sources:https://forums.veeam.com/post461204.html#p461204  

50 Episodes of GTwGT celebrating with a great interview with David Friend, CTO of Wasabi... he is a very engaging and smart individual... really knows what he wants Wasabi to achieve. Learnt a lot about what makes them tick.

Some of you may have noticed a certificate validation error when using the Automatic Update function in the Veeam Backup for Microsoft 365 console. The error is due to a certificate expiring (which is needed to validate server updates). There is no cause for concern; the certificate was not compromised, and the option to manually patch the server was not interrupted. This certificate has since been updated, but a manual patch is needed to get the new certificate for validation. For those who want the quick fix, head over to KB4341. The rest of this article will cover some good-to-know information about certificates and some lessons learned.What is PKIWe commonly hear the term “certificates” with applications or websites and understand this is generally associated with security but may not understand what role certificates play. To start, let's talk about what a certificate is. A digital certificate is used to initiate an information exchange in two major parts; first, by saying, “ you

So part one of the Veeam Backup for Microsoft 365 discusses the shared responsibility model and outlines both Microsoft and Customer responsibilities. I also took at why you need to backup briefly but will dive more into this for part two. You can find resource links and part one here - Part 1 When it comes to backing up your Microsoft 365 data, there are seven reasons why you NEED to back it up -Accidental deletion: This is actually the most common cause of data loss in Microsoft  65. If you delete a user, whether you meant to or not, that deletion will then be replicated across the netw rk. A backup could restore that user, either to on-premises Exchange or Microsoft 365. Retention policy gaps and confusion: Retention policies in Microsoft 365 are designed to help organizations comply with regulations, laws and internal policies that require that they retain or delete content; they are not back ps. But even if you do rely on your retention policy in place of a backup, these retention

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's the corresponding R&D forums post: https://forums.veeam.com/veeam-backup-for-microsoft-365-f47/warning-on-my-sharepoint-site-t81314.htmlUpdate 2:It looks like the issue itself is gone since Saturday; perhaps Microsoft did change something on their side. I did

Veeam have today released the long-awaited update to Veeam Backup for Microsoft 365 (VB365), v6a.This release has been overshadowed by Microsoft’s controversial changes being made to the Teams backup process, forcing vendors such as Veeam to cease using EWS as a mechanism to backup Teams data, instead insisting on the use of the Teams Graph API. Why is this controversial? Because the Teams Graph API is billable per query. You can read more about this in my full blog post here.There are two key notes I’d like to highlight on this v6a release: Permissions Changelog Veeam are now including a permissions changelog for the Azure AD Application, vs the v6 release. This contains any newly required permissions, changed permissions or removed permissions, as well as describing the usage of these permissions. This is available within the v6a release notes, available here. Alt Text: Image displaying the permissions tables within the release notes Microsoft Teams API will NOT be enabled by default

 For this blog series, I will look at M365, which many people use daily, and why it is necessary to have backups using the Veeam Backup for Microsoft 365.  Now my approach will be coming not from a typical user perspective but from an MSP (Managed Service Provider) perspective.  I will start part one of this series by going through the shared responsibility model for Microsoft 365 and how Veeam plays a key role there.  As we progress through the series, I will talk more about the installation of Veeam for Microsoft 365 and other best practices. Shared Responsibility ModelThe shared responsibility model regarding your data relates to what Microsoft is responsible for and what you as the end-user are responsible for in protecting your data.  Many thought that Microsoft did backups for your data, and that assumption could not be farther from the truth.  When your data resides in Microsoft 365 as the end-user, you are responsible for backing up your data.What is explicitly each party respo

SureBackup is a really great feature to verify your backup data. Up to now the selection of VMs to verify within a single job was limited. For example it was not possible to mix physical with virtual machines. There seems to be something new in v12 beta! With beta it is possible to add agent backup machines to virtual machines into the same Application Group and as Linked Jobs too.

VMware has announced on August 3rd that vSphere ESXi 7.x is the last version supporting Apple Mac platform.https://kb.vmware.com/s/article/88698Reasom is that Apple is moving away from the x86 processor platform.With 7.0 the MacOS platform will be supported until EOL. Guest OS support for Mac is discontinued, too.  macOS guest operating system may only be operated in VMs on vSphere ESXi hosts installed on Apple Mac hardwarehttps://kb.vmware.com/s/article/2015161

VeeamON 2022 was live this year in Las Vegas and it was a great event.  I am a little late with my review of the conference due to catching COVID when I got back which took me out last week.  But I am back to feeling great again so here is my in-depth review and many of the new things coming in v12.Being able to walk the strip as well being my first time in Vegas was something of amazement with the sights and sounds as well as the lights.  You definitely get your steps in when you go to Vegas!First off the conference was great and to be able to attend live again was something else.  Being able to discuss and mingle with the vCommunity again was terrific as chatting with someone in person is something special.  The conference was packed into three days of exciting sessions, the welcome reception, expo hall, tech town, swag shop and even a visit from some friendly little dogs to lighten your day.The welcome reception on the first night was filled with music, live performers, some great f

Last week I had to troubleshoot a backup job that was using a brand new proxy and repository server. No other job was using these components. Nonetheless just 4 VMs were processed at the same time. All other VMs showed status “Pending”. As additional information, “Resource not ready: Active snapshots limit reached for datastore” was shown too in active job log.After a short investigation we found out, all VMs were located on just one VMFS datastore. Fortunately there is a rather simple solution for this limitation. You can create a registry key on VBR server to increase the limit of active snapshots per datastore:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\MaxSnapshotsPerDatastore For more details see this forum posts:https://forums.veeam.com/vmware-vsphere-f24/active-snapshots-limit-reached-for-datastore-t19711.htmlNice detail: The change enters into force immediately – even the job is currently running!Keep in mind, this is a global setting!  

Hello everybody!Today I’m coming to talk about archive backup with blob Azure.Archiving is good option to save money with your full (GFS) backups. It means that you can save your backups as archive instead of traditional hot/cool blob of Microsoft Azure.To do that you need configure a Scale Out Backup Repository with the Archive Tier enable.After that you can move your full backups older than X day to this kind of archive, as this example: But first you need to configure your blob repository as an archive option. To do this go go to Backup Repositories inside Backup Infrastructure menu. Right click on the pane and chose Add backup repository… On this screen chose Object Storage: On the next step choose Microsoft Azure Blob Storage option: After that click on Azure Blob Storage Archive Tier: Type Name and Description of your archive blob: Enter with your Credentials for this blob and chose what Gateway Server will be used for this function: On the next screen you just need to set what C

More and more customers are aware of the fact that 1 copy of their backups is not longer enough  . Yes!I always recommend to my customers and colleagues to implement the golden rule 3-2-1-1-0 (see my blog post  : 3-2-1-1-0 Golden Backup Rule | Veeam Community Resource Hub).The thing I want to highlight is having 1 copy offsite and being airgapped - immutable at the same time! Veeam delivers here 2 important possibilities : using a copy job to a service provider offering VCC using object storage with the copy mode in the SOBR capacity tierIn this post the move mode in the SOBR capacity is being ignored.Also using an object storage appliance on-premises is being ignored. The purpose of this post is knowing the similarities and differences between the two possibilities I already mentioned. Why? Because customers and colleagues often ask me why they should choose a copy job to our VCC instead of using object storage at a public cloud provider like Azure or Amazon.I have a list of 10 simil

Hello,I'm taking the opportunity right now to work on a like disaster recovery plan like, with Veeam.Once the replica job is up and running, my goal is to be able to trigger a failover if the server's ping is knocked out, so I wrote a little homemade powershell script to do that. If it is useful take it.^^ Clear-HostFunction FailoverCheck{    $server = "SERVER NAME"    if (Test-Connection $server -Count 1 -Quiet -ErrorAction SilentlyContinue){        Write-Output "$server connected successfully."    }else{        Write-Output "Connection to $server failed."        Write-Verbose "Pause for 10 minutes...then try again" -Verbose        Start-Sleep -Seconds 5 # set to 600        if (Test-Connection $server -Count 1 -Quiet -ErrorAction SilentlyContinue){            Write-Output "$server connected successfully after 2nd try."        }else{            Write-Verbose "Failed again. $server needs restart." -Verbose            # Insert Command to restart application here.            $RestorePoint

For the last few years, I have spent a lot of effort along with others at Veeam carefully watching the industry behavior when it comes to ransomware and its devastating impact it can have on an organization. I’ve also spent a lot of time putting together a lot of great works in the form of whitepapers, webinars and other assets to get the word out. Before I forget, check out these three key whitepapers:Edwin and I recap all Veeam ransomware capabilities: https://www.veeam.com/wp-protection-yourself-from-ransomware.html Hannes from Veeam Product Management goes deep and technical on the Veeam hardened repository: https://www.veeam.com/wp-guide-protect-ransomware-immutable-backups.html Kirsten and Melissa show how Veeam ONE can help to detect and respond to ransomware: https://www.veeam.com/wp-veeam-one-ransomware.html The important takeaway is that today, it is easier than ever to have backup copies ready to restore from ransomware with Veeam.What are the Immutability Options?I say ther

This Friday - I am presenting on SysAdmin Day 2022 with Sagi Brody - one of the Veeam Vanguards.But I need YOUR HELP - What is your best SysAdmin Story? I will feature it on the show and stream. Tell me a good one - I’ll share it! You can join the show to see if your session is featured also! This Friday at 11:00 AM New York time, Sagi and I will be LIVE on 4 Veeam social feeds (LinkedIn, Facebook, YouTube and Twitter) with a special stream. Join us on the LinkedIN feed here.I have a story that, for now, I will only refer to as “The Coworker” and Sagi will share his best SysAdmin Day story as well.But what is your best SysAdmin Day story? Do you have a save the day moment? What about those pesky dev is actually production situations? Believe it or not - the SysAdmins are still heroes. I would love to hear your stories and any appreciation story to go with it.Speaking of appreciation…. Veeam’s celebration of SysAdmin Day puts some prizes on the line. We are doing a lucky draw where you

Password Authentication & Certificate Authentications both have their pros and cons, but one undisputed stance is that certificates are more secure than passwords when used properly. To that end, I prefer to deploy certificate authentication when working with SSH, and when deploying Linux VMs, Azure prefers to as well.However, Veeam Backup for Microsoft Azure also signs you in with your Ubuntu user account, but doesn't support certificate authentication. Does this mean you're stuck with password authentication? Nope! Is it complex to configure? Also, nope! How does this work?Simply, we'll ensure that SSH is configured to only support certificate authentication, whilst configuring a password for authentication against the Veeam Backup for Microsoft Azure portal. For good measure, we'll also go through how to secure this platform further to reduce your attack risk. Getting set up with Certificate AuthenticationWhilst typically the more difficult part, Azure has done a great job of ma

Switching to Seal Mode - User Guide for VMware vSphere (veeam.com) Hello I wanted to bring to your attention a really interesting and useful feature.Create new Veeam  backup repository on new storage   Insert new exent on existing SOBRSet seal mode extent to be decommissioned After the extent is sealed, no further data is saved to the extent, and only read operations such as restore, merge and remove are allowed.Wait for the chains of all your jobs to reach the set restore points.Then verify that no Veeamzip \ export backups or oneshot backups without schedules are allocated on the old extent to be decommissioned.Such data will not be migrated needs a manual operation of moving veeamzip \export backup files etc.I love this feature allows me painless storage migrations for both standalone VBR environments and Veeam Cloud Connect platform .thanks for your attention

VMware vCenter Server is advanced server management software that provides a centralised platform for controlling your VMware vSphere environments, allowing you to automate and deliver a virtual infrastructure across the hybrid cloud with confidence.This privilege escalation vulnerability in VMware Center Server was reported to VMware by  Yaron Zinar and Sagi Sheinfeld of Crowdstrike for reporting.Present IssueThe vCenter Server contains a privilege escalation vulnerability in the IWA (Integrated Windows Authentication) authentication mechanism. VMware has evaluated the severity of this issue to be in the Important severity range with a maximum CVSSv3 base score of 7.1. Impacted ProductsThe following products are impacted. Workarounds are available to remediate this vulnerability in the affected VMware products.VMware vCenter Server (vCenter Server) VMware Cloud Foundation (Cloud Foundation).Known Attack VectorsA malicious actor with non-administrative access to vCenter Server may expl