Community

Hi,I need to find a way for backup verification test for agent backup systems. These are physical machines. (sql, exchange, oracle). VMs are working fine. I could do manually or script based instant recovery to vmware. But those tests would be in production an not seperated in a virtual lab. Any ideas? Is this feature on a roadmap?Any news for supporting NSX-T nics in VLAB? Thx and GreetingsHartmut 

Hello, I would like to know how do you manage your job and associated TAG when you build Veeam for customer ? I would like to use 1 job for 200 VM and within these 200 VM I have some with oracle, some with Exchange, some with SQL, …How would you do for it ? I think about different categoriies (rpo / application type / log processing)rpo : 24/48/…application type : exchange, sql, oracle,…log processing : copy , truncate, truncate 15m, truncate 30m,…And use tag combination on my job with all the possibilities :24 + exchange + truncate24 + sql + truncate 15m24 + oracle + truncate 30m24 + oracle + truncate 15m What do you think about it ?Is it better to have 1 job for SQL ? 1 for Oracle ? I would like to know how do you do for big customer :) I have some with 200/300/500VMs and I would like to avoid to manually specify each VM on AAIP and the process associated

I want to do an end-to-end workshop video and guide on how to configure and set up the Veeam Hardened repository. Not everyone has the comfort in Linux to do this on their own or at least without help. What kind of things would you want covered?Some scope:I’m going to start with a server on the table, go from racking and stacking to data recovery Will focus on a physical server with a hardware management interface Will cover mostly the Linux steps, the B&R part is easy!Let me know what you would covered in here!

Hello everyone! Just a silly question here. Look for this datastore on my lab environment: As I remember this datastore is used by Veeam during the Instant VM Recovery process acording with vPower NFS right? However, in this right moment I don’t have any IR job running.Is it correct having this datastore mounted on ESXi everytime? 

The VMCA2022 exam is officially available since August 2nd 2021. So time to refresh my good old VMCAv1 certification as of 2016 which I did today. In the following I will give you an overview of what to expect and how to prepare.I registered with PearsonVUE through the VMCE certification website. Make sure to read the VMCA 2022 Exam Specification Guide provided there. There were significant changes to the requirements for the VMCA exam. It is not just the new version of the VMCAv1 exam. You will be entitled to sit the exam if you either:attend the Veeam Backup & Replication v11: Architecture and Design training course through a Veeam Authorized Educational Center (VMAEC) attended the “old” Veeam Certified Architect v1 course without sitting the exam within the last 12 months hold the Veeam Certified Architect v1 certification alreadySo there’s no need to be VMCE certified any more which is a major change in comparison to VMCAv1. I’ll come back to that point in my preparation hints

Let's take a look at the new restore endpoints in the Veeam Backup and Replication API - For clarity, I am not talking about the Enterprise Manager API but the new  api attached directly to your VBR install - This is future of automating VBR and I could not be more excited about having this decouple from Enterprise Manager. So, what is a first class disk? Essentially its bunch of capabilities that VMware have opened up in the vSphere API allowing for vendors (or you..) to create block devices independently of a virtual machine. Veeam have hooked into this allowing for you to restore individual disks from a restore point, they create a new datastore over their vPower NFS magic and make this disk available for consumption. High level steps we need to take programatically to make this work Perform the FCD restore using the Veeam B&R API  Find the attached/restored file via the vSphere API (vStorageObjectManager) Reconfigure our target VM to attach the restored VMDK file sitting mounte

Another bug in vSphere 7 U3, I just read about. The backup function in the VCSA does not work in U3 any more when DB health check is enabled. Then each backup fails! Fortunately there is a simple solution for this: run /usr/bin/dbcc -fbss embedded in a shell-session in VCSA.More information:official VMware KB article: https://kb.vmware.com/s/article/86084 Blog post by Andrew Mauro: https://vinfrastructure.it/2021/10/file-level-backup-issue-with-vcenter-7-0-3/This is important because you normally do not see failed backup. So when you never checks them, you would not find out the broken functionality. 

Hi! Sometimes I receive Twitter Direct Messages asking how I can receive the latest Veeam News that fresh. It is actually very simple, on this quick tip we are going to learn how to keep up to date with everything that happens in the Veeam Knowledge Base, starting with new articles into the KB to updates or revisions of them, following those simple steps, we will be updated of any change or new support for X, or Y.In a perfect world, these steps we would have to make them for all the manufacturers that compose our Datacenter, as good practice, but for today I show you how to add the KB of Veeam How to add the Veeam Knowledge Base to FeedlyThe first thing I want to tell you is how to add it to your Feedly, which is probably your favorite RSS reader, at least mine, from the main Feedly website, we will click on the + icon on the left:We will introduce the URL of the RSS of Veeam Knowledge Base – https://www.veeam.com/services/open/kb/rss-feed and the following will appear:Once we subscr

I’ve used Veeam Backup & Replication V10 solutino; have File-level-backup jobs, Synthetic full backup, local repo, and use Optimal Data Compression.My issue is, High and Extreme Data Compression does not compress The Backup.my backups took massive sotrage, why is the compression not working?

I’ve used Veeam Backup & Replication V10 solutino; have File-level-backup jobs, Synthetic full backup, local repo, and use Optimal Data Compression.My issue is, High and Extreme Data Compression does not compress The Backup.my backups took massive sotrage, why is the compression not working?

It’s the special time of the year again...where you can win great prices from Veeam Just register on the following page till December 31th 2021 and you’re in.https://www.veeam.com/holiday-giveaway-2021.htmlAfter registering you can also create your own christmas postcard. Here’s my greeting to the community (click link below):→ https://www.veeam.com/holiday-giveaway-2021-postcard.html?card=3P14HE7OF02GMQX 

I have an odd backup setup that I am trying to navigate. We have a VM (VMware) that is being backed up that has a volume listed in the OS as G: drive. This is actually a USB drive attached to the host server and is being fed into VMware via the xHCI USB driver. Veeam is backing up this volume, but is not listing it in the list of backed up drives if I try and create an exclusion. Is there another area to look or another way to exclude just this G: drive from the backup?

I am currently trying to upgrade to version 11 . The first upgrade failed with an error as it could not start the services. I followed this fixhttps://community.veeam.com/blogs-and-podcasts-57/failed-to-connect-to-veeam-backup-and-replication-server-how-to-fix-remote-channel-sink-urinotpublished-remote-connection-refused-and-failed-to-start-the-service-1263 I am now having to repair the installation as the fixes did not work and the services would not start. I have just tried to run the repair and I am receiving a different error "veeam configuration database is in use by the backup server " I have no idea how to proceed.

This is it, we’re in the final month of the year.The month where the world is unsure whether to work, or eat, or drink, or be merry, or some combination of the above.The month where IT is asked the age old question, “since there’s nobody in over the Christmas period, can we not just overhaul the entire infrastructure then?” So, to prevent the arguments with the family that we’re being anti-social on a laptop, we invented the change freeze. Does your organisation have one? How long do you give yourselves of sweet, sweet, read-only bliss?We want to see plenty of this:  And none of this:  If you haven’t had a change freeze yet, it’s not too late to try, you’ve all been working hard this year, you deserve a bit of downtime.

Hey guys, I watched this video on WAN accelerator and the instructor has told to not specify C drive as the cache location, but in helpcenter documents they have not specified anything like that. Is not setting cache location on C drive a good recommendation? Please refer the video and for more details of what I described jump to 6:27 of the video  

Veeam Backup for Microsoft Azure is purpose-built for simplicity, scale, savings, and security for your Azure environment. Veeam Backup for Microsoft Azure is available as a virtual machine (VM) offer exclusively through the Azure Marketplace in both Free and BYOL editions.Here are some guides that may interest you: How to set up Veeam ONE 11 Server, What’s new in Veeam Backup and replication v11?, how to install and configure Veeam Backup and Replication 11 Community Edition with its default SQL Server Express Edition, how to migrate Veeam MsSQL Database to a new MsSQL Server, and how to install Veeam Backup and Replication 11 Community Edition with a dedicated SQL Server.Due to the Shared Responsibility Model by Cloud providers, it is evident that it is still your data and that you retain the responsibility to secure and protect it. You may want to take a look at Veeam Backup & Replication which can also enable you to centrally manage Azure backup with another cloud, virtual, phy

Hi - just testing with community edition. I ran a test backup to C:\backup but I did not have enough space. I’ve added a new repository which is a Synology NAS. I can see a vbm file is created for 2 of my linux hosts, but thats it. Immediately the backup fails. All I get is “finished with error”. Is there a log somewhere thats a tad more verbose than this?  

Played around with the new version 5 of Veeam's Disaster Recovery Orchestrator (VDRO). I had some troubles with licenses and wanted to share my outcomes.There are a few components that should be taken into account for licensing:Production VBR server VDRO server Embedded VBR server within VDRO serverSome facts here:Production VBR server Can be added to VDRO server. Which will be normally the case for production installations. For PoC, it is not necessary to do so. When adding to VDRO (an agent will be installed), consider the following: You are not allowed to mix trial and NFR keys! So, when your VDRO server runs a trial (or paid) license, a NFR licensed VBR server cannot be added.   https://helpcenter.veeam.com/docs/vdro/userguide/licensed_objects.html?ver=50#licensing-for-standalone-veeam-backup---replication-servers-with-orchestrator-agents VBR server must have Enterprise or Enterprise PLUS edition licensed. VDRO server There are a few licensing types here: https://helpcent

This topic is replaced by the V12 Upgrade Center:  Doing something new! Here in the Veeam Community Hub I thought this would be a good place for a new piece of content that gives some practical information for the upgrade process for Veeam Backup & Replication V11.  We wanted to put this together here to give each of you an additional way to start the upgrade process! Watch this quick video below for an overview: Now, let’s get into the specific bits that you need to upgrade to V11! We may add sections or clarify things based on feedback, so please leave a comment below and maybe come back to the news section here for updates!Pre-Installation SectionWe recommend you review these key pieces of documentation: The Release Notes should be the first thing you read (these are with the download). Then, I recommend a good read of the What’s New document. Help Center User Guide (VMware vSphere version). Help Center User Guide (Microsoft Hyper-V version). Veeam Backup & Replication V

With version 10 and 11 of the Veeam plugin for Oracle RMAN was a new backup metadata format introduced.But what is the benefit of the new metadata format?In the older versions all metadata was written to one file – the “Veaam backup chain metadata file” (Extension of this file is .vbm).This file gets rather big over time and it takes some time to read and write the metadata for a single backup session from or to this file. Because of this the amount of time needed for a plugin backup session gets longer and longer.The new metadata format writes the metadata of a backup session in an own file (Extension of these files is .vasm). Now you have many small metadata files. If a backup file expires, the metadata has not to be searched in the big file and deleted from it. Now the metadata file can simply be deleted with the backup file. This is much faster than the former procedure. Additionally a new small file is written for the backup chain with some general metadata information (Extension

Veeam has released a new patch with some good fixes for SOBR and F5 refresh. Check it here - https://www.veeam.com/kb4245 

What happens if I loose VBR Server?How can I perform the Failover?What option do I have for DR of the VBR Server itself?Thank you!

This week I was investigating some imbalance in size on two (scale out) repositories. Every repository gets the backup of a subset of all VMs and copy these to the second repository. And vice versa. So in theory, both repositories should be very similarly utilized. But when you look at volume properties, this is not the case. We see quite a large difference. So I used PowerShell to query VBR and sum all data of each VM on both repositories (I will post some code snippets next week). And I found out, VBR does not know about a notable amount of data (VBR-query showed much less used data than volume properties did).So there seems to be backup data, VBR is not aware of. I call these files orphaned files. What are your experiences with orphaned files? Do your see them very often or not at all? Or are you not aware of their existence? Please let us know.[Update] See my new blog post on how to find orphaned backup fileshttps://vnote42.net/2021/11/30/query-backup-job-space-on-veeam-repositorie