Community

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 ? 

As already announced (see here), the first draft of the Backup Scanning Tools Menu has just been made available in my GitHub repository. This script is designed to provide a user-friendly, menu-driven interface for triggering the various backup scan tools that I have provided in the past. It allows the user to choose from a number of options, each corresponding to a specific type of backup scan. The script provides detailed descriptions of each scan operation before prompting the user to enter the required parameters for execution.Besides the actual Scanning Tool Menu script I also created an installer script that "installs" all necessary scan scripts into the selected directory.InstallationFollow these steps:Download the Installer Script Download the

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

Hi Folks,If anyone is preparing for the CKA certification feel free to share or ask me any questions. My 3 years is up and I need to redo the exam as well. I am very lucky to have been asked to lead with fellow Kodekloud Ambassador Nitish Kumar  https://www.linkedin.com/in/nitishkumar06/ a closed CKA study group over the next few Months on Kodekloud but am more than happy to try and help folks here as well. Group study makes everyone stronger! So much for taking a bit of rest in the summer. Other upcoming events and tasks, I got talked into taking part in the Tanzu hackathon which hopefully won’t be too embarrassing since I don’t feel I know Tanzu well enough to hack it :). On August 31 I will be taking part in an online panel discussion with about Kubernetes and Tanzu data protection. The Veeam contingent there is going to be very strong as als

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 %pro

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

Hi folks,My wanderings in the wonderful continue. I need to move an M365 repo from a REFS drive (as far as I know this is not good, NTFS is the best practice) to a new drive. I have read on the forums that the Move-VBOEntityData powershell is NOT the way to go. Instead this is the procedure: 1. Disable all backup jobs related to the repository you want to move.2. Stop all the Veeam Backup for Microsoft Office 365 services before moving any data.3. Copy the backup repository data to the backup repository location on the new repository location (using robocopy for example).4. Start the Veeam Backup for Microsoft Office 365 services.5. Add the new repository with the moved data.6. Open backup job settings and specify to use the new repository Any comments or advice from folks who have been through this. I would like to avoid any pain since I had a wisdom tooth pulled this week and have enough already :)  cheers

My Sysadmin story is rather old, from my own beginnings in IT. It’s not directly Veeam related but the message is valuable for every backup administrator.The outageThere’s been a certain Linux VM which was running a very critical software for that company. Software updates were done by the vendor itself so there wasn’t much to take care of. Of course, besides including it in the backup process.At some point there was an outage in the datacenter which shutdown all virtual machines. After the power had been restored, all virtual machines were started again without any issues; at least almost without any issues.The Linux VM didn’t come up and stayed at the boot screen without any progress. After a bit of debugging without a solution, we decided to restore the VM as it was in the morning and no changes occurred since the nightly backup.Unfortunately, the restored VM had just the same problem and refused from bootin

Hi There!I've shared this story in my VUG Group, Spain,But I wanted to translate it to English and share it with all of you,It’s a Personal experience, the latest I’ve got in Prod before changing my role,and now re-publishing it for the Sysadmin month. Hi,I want to share with you my latest experience as a IT Infrastructure responsible, just a week before moving into a new company, also in a new role / position. 

I work already more than 6 years at my current company as a system consultant specialized in backup, DR, hypervisors and storage but at the first place being the Veeam Expert 🤣.In those 6 years I have seen a lot, but one of the things I will never forget, is a story that I want to share with you 🤗. When :  It happened more than 2 years ago Who :  It happened to a customer of us, a secondary school What happened :  They were using multiple standalone Hyper-V hosts with local storage.They all were using RAID5 on the data-volume (where the .VHDX files = HyperV virtual hard-disks are located) of their hyper-v hostsAs you know : in a RAID5 setup, only 1 disk may fail...On their most critical Hyper-V host 2 d

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?

Hi all,for the upcoming  "System Administrator Appreciation Day," I wanted to tell you about an amazing mis-adventure that happened to me a few years ago.But first, a brief recap of my work life: I've been working in the IT world since 2012, starting in the Helpdesk of a local IT services company, and then moving to the Datacenter Team a few years later.Over the years I've encountered a variety of problems, from the simplest and least blocking, to the most complex and critical: servers that no longer boot, applications that don't work, stuck snapshots, deleted LUN..but the one I'm about to tell you about represents for me the most unusual problem I've ever faced (and unfortunately not the most critical).Our company was a Service Provider, imprinted mainly on IAAS and other related services.We managed a total of four datacenters: one at HQ, where there were a few racks with essential internal services, and three others located at an Italian supplier

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?

Part 3 of the ‘HPE StoreOnce: Immutability with v12’ series is about a small, but very useful new feature. Before going into it, here are the links to Part 1 and Part 2, in case you’ve missed them.Thanks to Federico Venier from HPE I noticed that the latest StoreOnce release 4.3.6 did introduce two-factor authentication!StoreOnce 4.3.6 supports Two-factor authentication (2FA) which provides additional security for users logging into the StoreOnce system, granting clients access to the system only when they present at least two factors of authentication.https://support.hpe.com/hpesc/p

Rewind about 2 years. We were short staffed (still are), behind on updates and upgrades and trying our best to get rid of legacy and unsecure infrastructure. After months of work, things were getting close to the finish line. Systems were running great and we were feeling quite safe and secure. It all came to a sudden halt when someone said the service desk phone was ringing off the hook and no one could log in. I tried myself, and not only could I not log in, I couldn’t ping or lookup most of the VM’s on the network.  I rebooted one of my workstations and received a 169 address. I knew right away I was in trouble. I could tell DCHP was having issues on my desktop, but on my second PC I could still ping most of the servers with static IP’s. This told me DNS was also down. Great I thought at 4PM on a Friday. We continued to do some troubleshooting and it ended up much worse. It turns out someone decided to put a VERY large file in the sysvol

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