VeeamON 2025 San Diego, California
Bring your knowledge and expertise while creating blogs and podcasts
Recently active
Hello, everyone.I am posting the guide for those who need to migrate their Enterprise Manager for various reasons.I had the need to migrate EM to consolidate VMs.The MSSQL database is a dedicated VM.KB1889: How to migrate Veeam Backup & Replication or Veeam Backup Enterprise Manager Export all Keysets from the old Backup Enterprise Manager web console. Take note of which keyset was Active. Uninstall Backup Enterprise Manager from the old server. Install Backup Enterprise Manager on the new server. During the installation of Backup Enterprise Manager, do the following:If presented with the Default Configuration step of the installer, check the box labeled "Let me specify different settings"For the Service Account Credentials step, provide an account with the appropriate permissions to the SQL Instance where the VeeamBackupReporting database is located.On the SQL Server Instance step, choose the option to "Use existing instance of SQL Server" and specify the SQL Server and Inst
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 also present will be @michaelcade and @HunterLAFR . In fact if I am not mistaken @HunterLAFR is the organizer even!! As for videos I hopefully wi
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 booting up. And also the 2 day old restore point behaved the same.At that point we
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. It was August 10th 2022, enjoying my summer holidays before moving into a new company, celebrating my 37th Birthday at the Swimming pool area with my family, and surprise, my phone dings, and I just had a quick look and this came up on the screen:“We’ve got a Virus in our Systems” I felt goosebumps all over my body, I left my pint of beer (Yes, I love beer) on the table, and I addressed my wife and told he, “I gotta go” ransom! I change my clothes, from my comfortable swimming suite to jeans and a t-shirt, went to the office to get a better understanding of what was going on, an
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 disks were stuck, so the volume was broken and all data was lost on that hyper-v server!On that server a couple of virtual machines were running including one of their most important server : their big file-server!That was not the only issue : the hyper-v host was not in warranty anymor
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 where we delivered the bulk of the se
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/public/docDisplay?docId=sd00002919en_us&page=GUID-D9CE533F-9920-4656-A77D-4210E4EC56DE.htmlUntil now, an attacker would have been able to cause damage if he got access to the Admin and Security officer credentials. I described this process in Part 2 of the series: Veeam V12: Immutability with HPE StoreOnce - Part 2Now, with 2FA, the security of HPE StoreOnce backup repositories gets a huge boost.Enable T
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 folder to replicate it without confirming the
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 servers, with Windows OS, as combo Repo/Proxy devices for my backup environment. I also u
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 moments of blissful neglect. The stakes were very high. First attempt
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 arrive onsite on a hot June day
