VeeamON 2025 San Diego, California
Bring your knowledge and expertise while creating blogs and podcasts
Recently active
With the release of Veeam Backup for Microsoft Azure v4, I thought now would be a good time to discuss how to handle account permission changes. This tends to be required when Veeam release updates to the Veeam Backup for Microsoft Azure product, typically required to support new functionality.I was greeted by the request for all of these permissions after updating from v3 to v4Once you sign into Veeam Backup for Microsoft Azure after an update, you’ll likely have a notification similar to the above, depicting the missing permissions.There are two ways to update the permissions, and I’m going to take you through them both now. Method 1: Let Veeam Update its Permissions Yep, Veeam can handle this for you, and it’s really easy.Step One: Enter the Configuration section of the Web UI. Navigate to Administration > Accounts. Find your Azure account, select ‘Edit’.Step Two: Within the Edit Azure Account screen, edit any name & description details if required, otherwise click next to en
I'm sure you all have heard about a lot of great features Veeam has added to its latest release like - ability to backup directly to Object Storage instead of the need to use SOBR tiers, choice to use PostgreSQL as your VBR configuration database, introduction of VeeaMover technology to move Backup files to new jobs or Repositories, increased security such as Multi-Factor Authentication, and many others. But there are quite a few features in Veeam v12 you may not know about. I'll be sharing what some of those are in this post PostgreSQL - AAIPAs mentioned above, Veeam now gives you the choice to use PostgreSQL for your VBR configuration database. This removes some limitations, such as the SQLExpress 10GB size limit as well as some performance limitations. But, did you know Veeam now includes PostgreSQL as an application-aware image processing (better known as AAIP) option? This includes transaction logs for point-in-time recoveries for PostgreSQL on Linux as well. PostgreSQL AAIP Synth
Today, I’d like to talk about creating and scoping realistic and enforceable RPOs and RTOs for your Business Continuity (BC) and Disaster Recovery (DR) policies and Service Level Agreements (SLAs) within your organization. As every organization will have different requirements the focus of this blog post is on general considerations for shaping your policy.Additionally this blog post is focused around policy design as opposed to backup technologies and should be vendor agnostic for the most part, though where I am aware of features from my backup solution of choice (Veeam of course!!!) I have referenced improvements that solutions such as Veeam can bring to the process.The assumption is made that you’re already aware of the applications, operating systems and data within the organisation/environment you’re designing these policies for. Step One: Define Recovery Priority Before we start to consider recovery point objectives, we should consider the recovery time objectives of our workloa
One rule of backup is to always have more than one copy of data. This has often been defined as following the 3-2-1 rule, which states, to ensure recoverability in the face of disaster, you need to have 3 copies of data, on 2 different medias, with 1 copy offsite. By following this strategy for backups, businesses gain three different copies of data that they can recover from. However, with the continued threat of ransomware in today’s IT landscape, we need to evolve this rule to meet the challenges that face businesses today. As data is the lifeline for every business, putting in the necessary steps to keep backups protected from malicious attacks is imperative. To do this, having a immutable storage option that prohibits backups from being altered or deleted should be an added element to a long standing rule for backups. With the addition of adding a copy of data that is offline and/or immutable, businesses can ensure that at least one copy is locked from being changed or deleted. H
Happy Friday Community!And an even better Friday for me after passing the VMware VCP-DCV this morning. Whew! What a challenge, but with some patient studying, practical experience, and hard work, it’s passable. ReviewAs I shared in my Study Guide post from a few weeks ago, the exam has 70 questions and is 135 minutes long, which is 5 minutes more allotted time than the prior version. Unlike previous exams, I really needed most of the time to finish the questions and review my answers. I still had about 45-50 minutes left after my review. But on the last 2 VCP exam versions I’ve taken, I was able to finish and review in a little over an hour.I think part of the reason for the extra time it took me to finish was the question format. They were normal questions but several sentences long (long for sure, but not book-length). As such, those took a little time to read, and verify whatever requirements were asked for. Thankfully there was also what I call ‘standard’ questions consisting of ju
FolksOnalytica just came out with their who is who in the cloud: I seem to see a familiar beard :) https://onalytica.com/blog/posts/whos-who-in-cloud-top-50-influencers-to-follow/
We know that Veeam Backup & Replication can back up virtual machines. This is one of the main functions of Veeam and it has the most features and options that we can configure. Normally, when we are starting in the backup area and taking the first steps in data protection, one of the features that ends up going unnoticed is Application Aware.So, application Aware is a function that we can configure in our backup jobs. It allows us to consistently create backup. Consistent Backup But after all, what is consistent backup?By default Veeam Backup & Replication does not perform your backups consistently. This occurs because a default configured backup job does not process a server's application logs. We must remember that Veeam backs up servers through snapshots taken in the virtualization environment. As a result, Veeam ends up not communicating directly with the operating system of each of these virtual machines. This causes Veeam to consider and perform these backups inconsistent
Hello everyone! @HangTen416 & I are delighted to introduce to you all the latest ‘thematic’ Veeam User Group: Cloud City. What is Cloud City? Cloud City is a Veeam User Group focused on Veeam’s Public Cloud and SaaS Product Offerings. We wanted to create a dedicated space in the community for people to share their knowledge and ask questions related to these products, or the relevant services that provide the platform these products interact with. Where can I find out more? Firstly, you can check out the group here: https://community.veeam.com/groups/cloud-city-107This page has more information on the purpose of the Veeam User Group, and you can join the group via this page. @HangTen416 and I are also going to be hosting an introduction meeting on the 9th May, be sure to register and check it out if you’re interested: During this session we’ll talk more about the purpose, some community guidance on what content we intend to focus on and encourage, and our plans for (virtual) meetin
An incremental update has been released for Veeam Backup for Nutanix AHV. Version 4a has a few new enhancements and some issues that were resolved. The download link is in the KB link below. Note: Veeam Backup for Nutanix AHV 4a only supports integration with Veeam Backup & Replication version 12. What's NewUpgraded OpenSSL to version 1.0.2zg Configuration restore now assigns a default start time to a restored job that used an active full schedule but did not have a start time configured Configuration restore now assigns proper value and proceeds if BackupUID is found to be an empty string during configuration restore Default settings for Active Full and Synthetic Full job settings in the web UI have been adjusted to be consistent with Veeam Backup & Replication.Resolved IssuesA backup job continues to retry when the session ends with a warning.Now, after the first session completes with only a warning, no further retries will occur. Notification emails sent to Enterprise Micr
Veeam Recovery Orchestrator (VRO) V6 can provide orchestration of recoveries to different locations (original location, a secondary site, or Azure) from backups or secondary backups. VRO The feature that I love the most about VRO (well, really one of the many features) is the ability to easily have VRO scan multiple backup restore points of a server (virtual or physical) for malware infections that may have been missed before a backup so bad backups don’t get put back in production! VRO will use a the update AV software installed on the mount server to perform iterative scans of multiple restores to find a “clean” restore point to recover from. This can be performed in a few easy steps. First, launch the orchestration plan for the server(s) you want to restore, right-click on it and select run. Step through the wizard until you reach the “Ransomware scan” page. If you want to limit the number of restore points scanned, you can set it here by checking the checkbox and entering a val
This is part four of the blogpost. If you want to read it from the beginning, head here: SOBR Archive Tier – Explained and Configured – Part 1 of 4 | Veeam Community Resource HubIn this last part, we will cover the free section of our feat and put things together in VBR.Setup within VBRNow it’s time to create the new object storage inside your VBR console. Add a backup repository of the type “Object storage”.Add new object repository to be used as archive tier. Choose the appropriate hyperscaler. For the archive tier currently only AWS and Azure are supported. We’ve used Azure in the example.Only Amazon S3 (AWS) and Azure can leverage the archive tier.Now the differentiation from capacity tier is made by selecting “Azure Blob Storage Archive Tier” instead of just “Azure Blob Storage”.Make sure to select the special option for the archive tier.Give the new repository a nice name and description within VBR.Very inventive name, isn’t it?And provide your storage account name and the shared
