News, guidelines and various community projects
Hello, I need to create a SQL DB backup for VeeamBackup DB (VBR 10). I’m using MS SQL Server Management Studio with Windows Authentication however the DB is not accessible with this user, do I need to use SQL Server Authentication with th “sa” user? if yes, I don’t have the password, is there a default password? if no, can I try to reset this password without problems? Thanks for your help, Omar De Souza.
Hello,Everything is in the title, it’s the first time i’m using Veeam.So, i have a VM on ESXi A, i want to setup an incremental backup of this VM to ESXI B that has a LUN assigned to it (the datastore is created).But i have no idea how to do it. When i create a backup job, when i get to “storage”, i can only chose the default backup repository, which is on the local hard drive where Veeam is installed...I don’t know how to create a new repository that will point to my “backup-LUN” datastore on ESXI B …Can you help me ?Thank you in advance,Regards
Great news! The pre-registration for VeeamON 2022 is open!https://www.veeamon.comThis year VeeamON will be a hybrid event, which means you can either attend virtually (for free!) or in-person. If you go for the later you’ll have to hurry as the seats are limited (1500). Also there’s a bonus option to add VMCE/VMCA training for a very good price. If you need to justify the costs for attending the in-persion event and the training, there’s even a template you can download and fill in our details. This will sure make it easier to get the budget for the trip to Vegas So regardless if your planing for the virtual or in-person event, go to www.veeamon.com and register yourself!Also don’t overlook @MicoolPaul’s post with more details below
Since I was tired to click roles together in vCenter server, I wrote a simple script on creating a vCenter role for Veeam with PowerCLI.This PowerShell / PowerCLI script lets you create a new vCenter server role with all the cumulative privileges and permissions to use them with Veeam Backup & Replication V10.The privileges used are based on the recommendations out of the Veeam Help Center which you can find here: Cumulative Permission for VMware vSphere – Veeam Help CenterSimply execute the script and follow the steps to fill in the relevant data like your vCenter server name, the username and your password. The script will then ask you to choose a name for your new role and automatically creates it. The script in actionThe script was successfully tested against:VMware vCenter 6.5 VMware vCenter 6.7 VMware vCenter 7.0You can read about this on my blog:https://www.virtualhome.blog/2020/04/22/creating-a-vcenter-role-for-veeam-with-powercli/The script is online at github: https://git
@PValsecchi already showed how to use vSphere tags for VM selection in VBR. New in v11 is the possibility to combine vSphere tags. I want to show how this work. For that, I created two tag categories. One for Location and one for Backup. I defined datacenter A and B locations; and Gold, Silver and Bronze backup priority. These tags are assigned to my 4 test VMs:So: VM01 and VM03 (odd numbers) are located in DC A. VM02 and VM04 (even numbers) are in DC B. VM01 and VM02 are defined for Gold-Backup, VM03 for Silver, VM04 for Bronze. First, I select one Tag for VM selection: DC A. This can be done either with single tag selection or with new combination of tags but just select one.As expected, when backup runs, VM01 and VM03 are selected:Next, I want to backup all Gold-Backup VMs in DC B and select these tags: Objects shown in Job definition:Just VM02 has all tags assigned: Fine, works as expected! And now, backup all VMs in DC A and B:Eventually here is a pitfall. Because now nothing will
The first of February was "Change your password" day. Because there are a lot of InfoSec people in the community I would like to ask: Is it still a good idea to change the password regularly? Respectively does this make sense any more?I am not convinced to change the password regularly. For sure it makes perfect sense, when:Account was hacked Check with tools like https://haveibeenpwned.com/ Using the same password for more than one service/account Using a bad password (for example: Password1)I am convinced of the following measures to protect accounts and passwords:Using long and/or complex passwords Using MFA wherever possible Using a password managerWhat do you think about this?
Another week, another script Today I’m sharing a Powershell script to configure the audited items (user) and set the audit notification settings. More details about the enhanced audit item functionality can be found here:https://www.veeam.com/blog/next-gen-office-365-backup-security-auditing-and-reporting.htmlThe read me and the code can be found on github:https://github.com/yetanothermightytool/powershell/tree/master/vbo/vbo-auditcfg
Veeam Agent for Microsoft Windows is unable to open backup files created by Veeam Backup & Replication
Hello, I am getting this error message:Veeam Agent for Microsoft Windows is unable to open backup files created by Veeam Backup & Replication.I want to restore a physical machine. Backup and USB boot stick were created under Veeam Communtty edition 10.
Based on my original script from 2020 where I created a vCenter role for Veeam Backup & Replication with PowerCLI, I decided to do the same for Veeam ONE. You can find the other script for VBR here:As a result the blog post here with the new script was born !This PowerShell / PowerCLI script lets you create a new vCenter server role with all the cumulative privileges and permissions to use them with Veeam ONE V11.The privileges used are based on the recommendations out of the Veeam Help Center which you can find here: Connection to Virtualization ServersSimply execute the script and follow the steps to fill in the relevant data. Most importantly your vCenter server name, the username and your password. The script will then ask you to choose a name for your new role and automatically creates it. The script in action :DAfter you have created the role you need to assign a user to it. As a result, continue within Veeam ONE where you add your vCenter Server. Veeam ONE vCenter “add”The p
Error message is about a missing restore point for a certain VM. Because of this catalog replication job fails. Cause and solutionOne possible cause is the deactivation of VMs guest indexing in backup job during a period of time when Enterprise Manager did not have access to the VBR server. In a specific case the password of the user that was used by Enterprise Manager to communicate with VBR server was changed.Fortunately, the solution here is also quite simple. At least I found a quite simple way to solve the problem. You need enable guest indexing and run the backup job. After this run make sure catalog replication runs without an issue. Now you can disable indexing again. From now on catalog should be replicated without problems.
Hey everyone, ACG are offering some free training courses again this month, some of them are looking really good!Disclaimer, haven’t watched all of the courses yet, but wanted to share early enough in the month that everyone gets a chance to review! AWS: AWS EssentialsIntroduction to AWSIntroduction to the AWS MarketplaceHow to Properly Secure an S3 BucketEKS Basics (Amazon Elastic Kubernetes Service) Azure: Azure ConceptsIntroduction to Azure SecurityIntroduction to Networking on Azure GCP: Google Cloud ConceptsGoogle Cloud Security EssentialsIntro to GCP for AWS AdminsGKE Basics (Google Kubernetes Engine) Kubernetes: Hands-on Kubernetes Troubleshooting Linux: Linux Operating System Fundamentals Want to see the whole list available? Click here!
VMware vSphere 7.0 U3c is released today, this version can resolve some critical issues. Please check the followings.For Log4j issue on vCenter 7.0, vCenter 7.0 U3c can resolve this issue.https://www.vmware.com/security/advisories/VMSA-2021-0028.html vSphere 7.0 Update 3 Critical Known Issueshttps://kb.vmware.com/s/article/86287
Hey Veeam Community, Question goes to people who work with companies that use Salesforce. 1) What is the is the most typical setup you see, in terms of Salesforce administration: Internal Salesforce team Internal IT team External service provider2) What is the size of that company and Salesforce deployment? (relative estimate or actual user count)For example, at Veeam it is managed and owned by the dedicated internal Salesforce team.Thanks!
we currently use azure as object storage and would like to achieve immutability on the backups.veeam does not support “out of the box” immutability to azure. i would like to know if any of these would work or if anyone has better ideas.Immutable blob storage on folder level Enable soft delete for blobs (or container) Enable versioning for blobs (or container) Enable point-in-time restore for containers setup Object replication in azure for the storage account thanks
Hello Veeam Community,El Rickatron and I cover this week's activity - but we need your opinion: Did we break the rule and should there be a new section on the community site for VMCE content? Check it out now and let us know what you think! ICYMI: Make sure to take a look at the Veeam Community Guide.
I’m using Veeam 11 (11a? not sure how to tell) Community Edition on my home network. Mostly everything is working fine; however, two of five win10 computer agents (184.108.40.20684) in the inventory are showing : Microsoft Windows version installed on this machine is not officially supported by Veeam yet. which is AFAIK is incorrect - both are standard Windows 10 Pro installs (I have never used any dev or pre-release builds). For example, the machine that gave the above is 10.0.19044 N/A Build 1466 which according to this page https://docs.microsoft.com/en-us/windows/release-health/release-information is a production release, not a Technical Preview. Where is the issue? How do I convince Veeam that it a production OS? PS, in case you are wondering; the backup still works. The issue is my reporting mechanism… since Veeam reports a Warning due to “Technical Preview”, I keep getting alerts about the issue.
Hello,We want to perform VEEAM backups on a server that has MAXDB. Is there an agent allowing MAXDB backups including logs as it is the case for SQL Server? Moreover, it seems to believe the forums that restoring a VM with a MAXDB database leads to an inconsistent database if you don't freeze it first. Is it always the case? cordially
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 the headline suggests, Veeam recently released a “version 3a“ of Veeam Backup for Microsoft Azure.Whilst there are your usual mixture of security fixes and bugs resolved, it actually brings a new (and welcome) change to the licensing structure around protecting Azure SQL workloads (not to be confused with Azure virtual machines running SQL Server). Licensing Per Server, not Per Database It’s not unusual to see Veeam adapt their pricing models over time to provide better value for customers. We’ve seen this historically when, for example, Veeam adjusted their NAS licensing to increase the amount of storage protected per instance license. However I was certainly surprised when Veeam released the latest version of Veeam Backup for Microsoft Azure and included a change to the way they process Azure SQL Workloads.First of all, this isn’t to be confused with the “traditional” approach to running SQL Server workloads in Azure, aka, running a virtual machine with SQL Server installed. That
I see a interesting thread on Veeam Forumhttps://forums.veeam.com/vmware-vsphere-f24/case-05192176-problem-restoring-backups-from-multiple-rdx-tapes-t78398.htmlwhere they’re trying to restore .vkb from RDX and got this error: From your experience, what do you guys think it can be?In my opinion, the RDX device was broken BEFORE the backup job, or it is a known bug due to the missing update KB4025334 and ReFS enabled on Windows Server 2016.And above all, RDX in nearly 2022? What do you think?Let’s flow this thread with our experience in cases like this one, and just leave real solutions on R&D Forums.
Login to the community
Log in with your Veeam account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.