Community

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 to all,I would need advices from you guys on how to approach to this setup the best way possible.We have two locations. Both locations have 64TB Synology NAS and also on one side we have one additional NAS for air-gapped solutoin. Now we would like to implement cloud storage and want to ask you guys what would be the best solution in configuration of this scenario.Scale-out repository or similar.At the moment we are doing backups on the one location (Vienna, Austria) and doing Backup Copy Jobs via WAN Acceleration to other location (Novi Sad, Serbia)Would like to configure it to best practices and in the most secured way possible. 

I’m new to the community and to Veeam.Does anyone know of a report that will show what I listed? Or at least some of it?Server All dBs for the server Backup time Time backup took to run Type of backup Restore points Success, fail, warning Error messages Enabled\disabled jobThanks much and look forward to contributing once I get a handle on using Veeam.-Mark

Hi Fellow Hubians! So can someone explain to me the reason for the upgrade backup chain format?https://helpcenter.veeam.com/docs/backup/vsphere/backup_copy_change_type.html?ver=120&_gl=1*wzxbvg*_ga*MTMwNTg0NDUyNC4xNjg3ODAyODk4*_ga_PMJS81E58L*MTY5MDIyNDYzNS4xMDAuMS4xNjkwMjI1ODYyLjI3LjAuMA As I understand this changes the chain from having one single metadata file to separate for the per-vm backups. I can see this being a good idea from the separate and conquer point of view (or deal with less hassle if one of the metadata files gets corrupted, so if you only have one, it is much less fun) but are there any other reasons for the move?

We are using community edition to backup two VMs. This setup was done by another user, and now we need to move the VM hosting the backup interface to another host.If I am not wrong, the service is actually running on the underlying host which is Hyperv…. What steps do I have to take to achieve this?I am confused if the community edition runs at hyperv level or not. Useful to know in case hosts are terminated

I really struggled with sharing this story because it’s quite embarrassing. But, if it helps 1 person, it’s worth it. And, not all ‘save the day’ stories are about us being flawless Systems Admins/Architects...we are human, but rather how well we’ve setup and configured our recovery processes. Thanks to @Madi.Cristil for prompting me to “go for it” and just share. 😊I did end up saving the day, but it was at the cost of my own initial negligence the issue arose in the first place, albeit an honest mistake. Interestingly enough, a fellow former Veeam Vanguard (now Veeam employee) and I were discussing this very configuration mishap potential via direct message in the Vanguard Slack channel prior to it actually happening to me.CatastropheSo, what did I actually do to cause the catastrophe at my organization? First, let me start by giving a high-level overview of my backup environment. I use physical serv

Hi Folks, When I think about being a Systems/Backup Administrator all of these years I can’t single out one single story that fully represents the highs and lows of this profession. So instead I have decided to write a few short sound bytes, streams from moments of memory suffixed with rhymes like one of the those “_restored” attachment names we use in order not to overwrite production. Every moment is also and emotion. We add a taint of emotional metadata to events and memories that we often don’t fully comprehend ourselves. Our work is matrix of puzzles and problems that we face everyday with our silicon little friends. Although sometimes it feels like they are our foes.  Gratitude The call broke through the comforting calm silence of a Friday morning IT room like a waiter’s tray that gets turned over in a busy restaurant. An important file was missing. It had been erroneously deleted in one of those careless human

Morning All Just moving over from Hornet / Altaro to Veeam 12 Community Edition. Set up is in Production have 3 Hosts with 9 VM’s between them. Mainly Server 2016 but one Linux and one Server 2022.All backup every 12 hours onsite and then Backup copy offsite.Offsite copy is onto a different VM Host with enough oomph and memory / storage to run whole lot in an emergency although PAINFULLY Slowly.Anyhow have done a test restore and all Server 2016’s and Linux come up fine (Need a couple of re-boots to recognise new Network etc to talk properly to each other. Server 2022 comes up will not boot due to the Key Protector could not be unwrapped as obviously a different host with different TPM Etc.If I kill the VM but keep the Virtual HDDs and create a new Virtual machine with same settings it all works but is there any way round this?

Happy Friday everyone!It’s time to get competitive 😁 What’s the fastest backup speed you’ve ever achieved with Veeam? I was working with a system recently that wasn’t using any flash within the backup repositories, but beefy RAID controllers and multiple RAID 60’s, and saw a pretty impressive 3GBps throughput at a job level. Sure it’s not NVMe speeds, but it’s certainly no slouch! And I can’t talk about this subject without bringing up my favourite ever UI Bug within Veeam, when I ‘achieved’ a speed of ~429.49PB/s 😂On your marks… get set… post!

Have an old ESXi 5.5.0 update 2 ver 5.77.3 host. Downgraded Veeam from ver 12 to 11, with the understanding that ver 11 supported ESXi 5.5. VeeamZip starts and quickly errors out with “Current VSphere license or ESXi version prohibits.” any thoughts?Thanks.

I’ve posted this before in a Friday Fun comment a few months back, but I think it bears repeating, especially because Veeam really did save the day, and maybe a few lives as well!  Details may be fuzzy, but it’s all true.  It’s a long story, so maybe set aside some time for some light reading, or maybe use it as a 15 minute distraction from working so that you can reset your brain.  And I hope you learn something too!I’ve been having issues getting this post, so as much as I hate to do it, I’m going to send you over to my blog to view the entire post.  Seems like I my have gotten a bit wordy but I’ll give you a preview below. Setting the StageLong, long ago (okay, it was 2020) in a galaxy far, far away (otherwise known as a small rural community in centralish Nebraska), there resides a community hospital who shall rename nameless.  We, an eastern Nebraska-based MSP, sourced this new client and it’s looking like the beginning of a fabulous relationship.

I know it’s late on a Friday, but I wanted to get this out of my head and off my mind before I forgot.  For our internal backup infrastructure, I’m the proud owner of a new Dell PowerEdge R550 with lots of space on local disk.  It’s going to replace a Synology RackStation that is slowly dying and is several years old.  The new server also has dual 25Gb connectivity (and dual 1Gb connectivity) that will allow me direct ISCSI access to our PowerStore 500T array.  This server will be the primary backup repository for our primary site. I am aware that if set this server up as a VHR/LHR, I cannot utilize direct storage access because functions required as a proxy server are not available when the server is hardened.  If I choose to forgo the direct storage access capabilities as a proxy server and move forward with a LHR, are there any caveats of using a LHR as your primary repo?  I don’t really NEED direct storage access.  There’s not that much data to backup every day, and I can

📢System Administrator Appreciation Day , celebrated on last Friday of July, is a time to recognize and appreciate the hard work and expertise of system administrators. It's a day to express gratitude for their tireless efforts in maintaining our digital infrastructure and ensuring the security of our systems.During this special occasion, organizations and colleagues unite to honor their system administrators with gratitude and admiration. Special events and awards are organized by companies to acknowledge the invaluable contributions of these SysAdmin "heroes’’.🏆To make this year memorable for our Veeam Community, we have planned some exciting surprises and activities for all our members!In July, our Blog of the Month activity is dedicated to all Sys Admins out there! If you have an interesting story to share with our Veeam Community about a

Happy Tuesday to the Community! In January VMware released an updated VCP-DCV 2023 Exam Blueprint for vSphere 8. It came out in good timing, at least for me, for a couple reasons. First, I wanted to get my DCV certification up to date, since for the past 2 years was not able to because the exam version on Pearson had stayed the same since I last took the vSphere 7 version in April 2021. Second, I had a long several week recovery period at home the past 2 months so it gave me plenty of time to review all (most) of VMware's vSphere 8 User Documentation and update my VCP-DCV 2021 Study Guide to 2023.As some of you know, I've been creating various certification Study Guides for close to 15 years. I started making them for my benefit to help me in my cer

Problem: Like a shooting star, sometimes can happens that some backup job on a Synology NAS fails with this error:Error: Incorrect function. Agent failed to process method {ReFs.SetFileIntegrity}.with VB&R 11.0.1.1261 and DMS 7.0.1 with a SMB share.It seems to be related to “Fast clone” feature inside Synology control panel.  Solution: Adding this registry key in the VB&R machine seems to solve the issue[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication]"UseCifsVirtualSynthetic"=dword:00000000 As reported in this thread, that registry key tweaks the full fast clone feature.

Veeam Backup and Replication V12 have a lot of improvements and new features in it.  If you are upgrading to V12 or installing Veeam Backup and Replication, there are many things that you should consider when planning your upgrade or installation.The following are a few of my thoughts to help guide you in forming your implementation and configuration decisions.If you are upgrading to VBR V12,  your first step should be to consult the following documents located at helpcenter.veeam.com:What’s New Release notes VBR V12 User Guide The release notes document has a good section detailing the upgrade process.

I’m using Veeam Backup for Microsoft Office 365 version 4.0 and want to copy all of the OneDrive data from users into their new accounts $DestinationSubfolder = 'Restored Work'$VeeamBackupJobName = 'BMC_M365_Data'$M365Credentials = Get-Credential$Job = Get-VBOjob -Name $VeeamBackupJobName$Session = Start-VEODRestoreSession -Job $Job -LatestState$UserToRestore = Get-VEODUser -Session $Session -Name 'Joe Bloggs'$UserDocuments = Get-VEODDocument -User $UserToRestoreif($UserDocuments){ $TargetUserName = 'Joe Bloggs 2' Restore-VEODDocument -User $UserToRestore -RestoreChangedItems -RestoreDeletedItems -Credential $M365Credentials -TargetUser $TargetUserName -TargetFolder $DestinationSubfolder}Else{ 'No OneDrive content found.'}Get-VEODRestoreSession | Stop-VEODRestoreSession The commands return this error th

I noticed VBR v12 RTM removed the " Install a new instance" selection from the Installation setup with the Microsoft SQL Server.An error message will pop up if the Microsoft SQL Server or Microsoft SQL Server Express does not install locally or remotely.That means I need to install Microsoft SQL or SQL express before installing Veeam Backup and Replication manager server (I knew v12 supports PostgreSQL) if I would like to work with Microsoft SQL? or is it a bug? 

I want to restore a backed-up 365 mailbox to another user. I’m following the guide in the Restore-VEXItem help page:https://helpcenter.veeam.com/docs/backup/explorers_powershell/restore-vexitem.html?ver=120I’m following example 5:$session = Get-VBOExchangeItemRestoreSession$database = Get-VEXDatabase -Session $session -Name abc.onmicrosoft.com$salesmailbox = Get-VEXMailbox -Database $database -Name "sales"$creds = Get-CredentialRestore-VEXItem -Mailbox $salesmailbox -Server outlook.office365.com -Credential $creds -RestoreChangedItemExcept I’m restoring to another mailbox, so my last line is like:Restore-VEXItem -Mailbox $salesmailbox -Server outlook.office365.com

G'day fellow Community "Hub-sters"! On the Weekly Recap a couple weeks ago, @Rick Vanover brought up what he thought would be a great Blog post for the Hub – "Rate My Design", based off a discussion he had with a customer; a diagram of folks' Veeam infrastructure.After thinking about what he said for a bit, I thought it would be fun, and thought-provoking, to provide a bit of a twist to his suggestion. What twist did I think of? To not (initially) share what my environment looks like, but rather provide what resources I have in my environment, then ask you, the Community, how you would best implement Veeam using those resources. From a high-level, I'll share capital and operational items. Then based off what's already in place (can't add other OP/CAP expenditures), you can provide a high-level design. This is just for fun only…so have fun with it. 😊After a few days or so, I'll share how I've implemented Veeam

With the release of Veeam Backup for Microsoft 365 v6 the Self Service Portal was also unleashed. In this video we run through a scenario where a new tenant is being onboarded from the Service Provider point of view as well as what steps need to be actioned by the tenants.

Hey guys!I just wanted to show my love for VEEAM - I have brought them with me from company to company over my nearly 20 year career and the product only gets better over time - I know it has some flaws as does every solution but I am happy to be implementing a new VEEAM environment and finally getting rid of the atrocious Rubrik chaos  I have been a VEEAM champion for a while now - and I have brought my VEEAM team with me from company to company and with any luck, one of these days, I will find out how to earn the “VEEAM Legend” title 

This works great for me using forever forward incremental jobs. If you are using synthetic fulls, or reverse you may get unexpected results as your latest job will show as the full size. I took my previous script and modified it so I can look at the previous 2 weeks, and see the size of the backup for each day.  If you change the (-14) you can make this weekly, monthly, daily with ease. # Location of the Veeam backup folder$BackupFolderPath = "f:\Backups"# Start and end dates$EndDate = Get-Date$StartDate = $EndDate.AddDays(-14)# Function to convert bytes to GBfunction ConvertTo-GB { param ( [Parameter(Mandatory=$true)] [int64] $bytes ) return "{0:N2}" -f ($bytes / 1GB) + " GB"}# Go through each day from the start date to the end datefor ($Date = $StartDate; $Date -le $EndDate; $Date =

For those doing forever forward incremental jobs, this is a handy scrip to see the size of your jobs each day. If you use Synthetic jobs, or reverse incremental you may get unexpected results as your latest file will be the full backup file.  While doing some planning for new storage I wanted to see how big a daily backup of all jobs on a proxy was.Here is a little script I came up with that you can modify the section “Current.Date.AddDays(-1)” to look back further. I may modify the code at a later time to fine tune this.  This worked well to go back a few days, then see the average daily size. Add that to your total full backup size and you can predict out the space needed to meet your retention policies. # Location of the Veeam backup folder$BackupFolderPath = "F:\Backups"# Current date$CurrentDate = Get-Date# Date of the day before$PreviousDay = $Cu