Discussion Boards

Our Azure blob storage was in the hands of another companies subscription. We’ve had that blob moved to our own subscription. Can we reconnect to a blob storage with a new path and still be able to use the backups?  Will it pickup as imported object?

Hey guys,I am getting ready to deploy VEEAM V12 into my environment (finally - took 8+ months)I am needing to delve into RBAC controls and granular access rights via AD  anyone have any advice or a direction they could point me in? thanks in advance 

Hi All,Apologies if I am asking in the wrong place, but using VBR V11 Community edition.I want to simulate a DR event. I have taken a Windows  Agent → Entire computer full backup to a USB Drive.Now i want to restore just some files from this USB Backup to a new server ( where the same edition VBR is installed.From the USB Drive on the new server , double clicking on the .VBK file launches Veeam, but my concern is the following window just shows “Restore”. I Don’t want to overwrite the entire server from this backup?  Does “Restore” actually start overwriting files, or does this proceed to show more options  ( and would be better named “Next”, rather than “Restore” ) ??Many thanks in advance.

Hello and ThanksMy personal laptop runs VAgent(Veeam Agent for Microsoft Windows 6.0.0.960 - Server Edition)My home server runs VBAR(12.0.0.1420)Both are community editions.Based on https://helpcenter.veeam.com/docs/agentforwindows/userguide/backup_cmd.html?ver=60I have multiple jobs, so I need the JobID.To Get the ID, I ran"Get-VBRComputerBackupJob -Mode ManagedByAgent" My problem, this command fails, i cannot figure out why?C:\Program Files\Veeam\Endpoint Backup>Veeam.EndPoint.Manager.exe /backup "5c2b2cb9-7092-4a9e-8e4f-b08e0e18e168"Job with id "5c2b2cb9-7092-4a9e-8e4f-b08e0e18e168" was not found Output of “Get-VBRComputerBackupJob -Mode ManagedByAgent”Id                              : 5c2b2cb9-7092-4a9e-8e4f-b08e0e18e168Name                            : ABP_EN10Description                     : Created by 192.168.62.233\administrator at 12/23/2022 4:22 PM.OSPlatform                      : WindowsType                            : ServerMode                            : ManagedByA

dear,please i will install rhel 7 on the physical server and will be as physical repository hardened linux (for compatibilty issue from server and the mounted san storage, i cannot upgrade more). so please what’s the recommended file system ? be aware that i cannot put xfs file system because it’s supported from rhel 8.2 ?

hi team need perfect solution with step wise .  

Hi all,I was checking the HCL list on QNAP QuObject devices and in the past you could find them at: https://www.veeam.com/sys469 but this now throws a 404…So checking the HCL didn’t show any Qnap devices.Aren’t they supported anymore with the QuObjects to provide local S3 compatible storage with optional immutability?   Some months ago we had a list like:  

Hi All,I have VMCE Certification. Recently i changed my job, so i need to transfer my VMCE certification to my new organization. what is the procedure for this. can anyone help me on this? Thanks in advance 

Hi, I have already calculated by using https://rps.dewin.me/rpc, do i have to add some buffer for my backup repository ? if yes, how many percent from the calculation that I have to add as my buffer ? 

In addition to backing up my ESXi virtual machines, I’d like to back the entire host up. How may this be done? Thanks!

I cannot expand a VM disk since the system is blocking this operation as for existing checkpoints.There’s no checkpoint within the chain in HyperV Manager, however some files exist on disk:I wonder if these are only some orphans created by VBR Comm. Ed., and if these can be safely deleted

Hello,A customer is using a "scale-out" repository on a compatible S3 and has Veeam version 11. They want to perform a test to recover the data stored on S3 to a new Veeam server. However, Veeam does not support direct import of data from the S3 repository in a "scale-out" configuration. To work around this limitation, the chosen option is to restore the Veeam configuration to the new server.The question is whether it is possible to restore the configuration on Veeam version 12, and what limitations should be taken into consideration.Thank you.

We’ve been running VBR on a 2012 R2 server for a long time but it’s time to get off of 2012.Is there a reason to keep running Veeam on a server? We’ve grown over the years and I have started putting VBR on Windows 10 workstations for remote offices and that has worked well.Do we need need to keep VBR on a server or is it save to migrate this over to a workstation?Interested in hearing why?Thanks!

Hello everyone,some backup files were manually deleted from D:\ storage (ReFS) andnow backup jobs don’t work.Failed to pre-process the job Error: A data integrity checksum error occurred. Data in the file stream is corrupt.Failed to read data from the file [D:\[...].8D2023-07-26T204743_9167.vbk].--tr:Error code: 0x00000143--tr:Failed to parse metadata stored in slot [528384]--tr:Unable to load metadata snapshot. Slot: [528384].--tr:Failed to load metastore--tr:Failed to load metadata partition. Delayed loading: [0]Failed to open storage for read/write access.We tried to create new repository (on the same storage) - didn’t help.ReFS partition was formatted (yes, backup data are lost) - didn’t help.The LUN on QNAP was re-created and we are getting the same error.Yesterday I tired to uninstall Veeam and I made a fresh install on VM.I didn’t help as well (note: I’ve removed %programdata% files, etc.).It seems there are still some old parts of backup chains, surprising...I didn’t find any s

It's Sys Admin Day! To celebrate, we have created a Sys Admin-themed Match game. How to play: We gathered some community posts that highlight the work Sys Admins do. (Thanks Joe and Shane!) Take a look at the 9 pictures and 9 posts below - can you match the picture # to the post? Give it a try! 😊   Posts:                                

 The last week of July brings an exciting Blog of the Month poll! As previously mentioned, this special edition is all about our fantastic SysAdmins, and we've selected blogs that showcase stories of our members' heroic saves as well as moments when they faced challenges, they failed but there are valuable tips and tricks for others to learn from.If we make it special, let's go all the way and break the rule! Instead of featuring six blogs, we've decided to select seven because they were all exceptionally good and truly deserved to be included in the poll! The winner will get a $150 gift card, blogger of the month badge+ a special SysAdmin badge and will be revealed during our livestream on Friday, July 28th! Not only will we discuss the winning blog, but we'll also delve into the two other most voted blogs during the livestream. Exciting times ahead! 🐱Please help us determine the best by voting on your favorite one by July 27th , 11 pm ET.    Good luck to all participants! 😊@dloseke

Hello everyone.I have the following query, in version 12 I see that there is the possibility of adding a proxy in the "General-purpose backup proxy" option, according to the following in the description "(...) and off-host backups of physical server" I would understand that it is possible for a physical server with veeam agent to add a proxy backup.Why the question? I have a Windows Server 2019 server that serves as a file server and when I run the job, either incremental or full, it slows down access to shared files and users complain. That being said, this proxy would help me mitigate or reduce the impact or what good practice do you recommend?The repository is an smb folder inside a Qnap NAS.

Hi Guys, lot of my customer has Veeam as virtual machine in VMware and using the virutal disk as repostitory (.vdmk), in my opinion - its old concept. One of my customer has new Storage Array and Physical backup server. The storage is direct connected to backup server via 10 GbE iSCSI.  Is there some steps how to migrate virtual veeam (also with backup repository) to brand new physical HW ?  Thx.Tomas

Hello Everyone,I have question here, If I have Veeam VBR v11 using SQL express as DB, and I want to migrate and upgrate it to V12 Postgres, is it applicable, and how?

We are currently running VBR Comm. Ed. on a Windows server 2019 which is a DC. For security reasons we would like to demote this machine to a simple server.Will this allow VBR ti run as usual after the change?

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?