Community

In the ever-evolving landscape of cybersecurity threats, safeguarding data integrity within backup systems has become paramount. Malware, in its various forms, poses a significant risk to the reliability and security of critical data backups. This article delves into the pivotal role of robust malware detection in ensuring the resilience of backup solutions, emphasizing real-time scanning techniques, periodic scans, and updates to identify and contain potential threats promptly. Understanding the Threat Landscape Direct attack of the Backup SystemsMalware, including viruses, ransomware, and other malicious software, can infiltrate backup systems through various vectors. Whether through compromised network connections, infected devices, or malicious email attachments, the threat is omnipresent.Once in the backup environment, malware can lie dormant and wait for the right moment to strike, compromising the integrity of the backup data. In the worst case, the entire backup repositories ar

I’d like to share a new vCommunity Podcast that’s been in the works lately.We discuss all things vCommunity. A gathering place if you will of people from all walks of the tech community. Its not vendor specific, but you may find a few friendly faces from time to time. Special thanks to @keiranshelden for pushing to have this start off. Along with regular guests @tsmith,  @JoeHoughes and myself @Tyler Jurgens we tackle a range of topics and questions. Check us out! You can find us on (other platforms will be added as we can):Youtube: https://www.youtube.com/@vCommunityioPodBean: https://vcommunity.podbean.com/Apple Podcast: https://podcasts.apple.com/us/podcast/vcommunity-podcast/id1733005383

I thought I’d post a slightly different take on an experience I had several years ago in a previous role, sometimes even the good guys need some luck. We had recently taken on a new client and hadn’t had a chance to review their infrastructure, unfortunately for them, everything was domain-joined and backed up locally to a NAS.The client got hit by ransomware and it ran amok encrypting the production VMs and unfortunately for the client also files stored on the NAS. This happened during the middle of the night and the client only noticed the next day when they turned up for work. Frantic calls followed to the help desk and the recovery effort started.Initial response efforts found that the backup server encrypted and it looked like the backup metadata was also affected. Upon further investigation, Lady Luck shows up. It appears that a number of the VBK files were being written at the time and were locked, so they were not affected.We deployed a new VBR server and set about importing th

Years ago, before 3-2-1 and 3-2-1-1-0 were household terms, I had a lot of photos from my early teens, and other important documents stored on my computer.  Fixing PC’s from an early age, going on college, then work for a large IT company I knew the importance of data backup, and have seen people upset when their precious photos were gone forever. I had an old Dell prebuilt PC that was cutting edge at the time. I paid thousands for it, and it had one of those nice big square monitors. I still have the recept somewhere to remind me not to keep spending so much on items the depreciate in value so fast. (as I type on a computer with a 4090 GPU and 14700k CPU🤣)  I bought a USB hard drive for backups, and copied over everything. One day, when my computer crashed I was happy when I bought a new hard drive, and restored all the files. I never really thought about it too much, and felt like my own hero for not losing all my data. I continued on, copying all my photos and files to the drive fo

This is a very interesting warning. I migrated lots of VBR servers, and it’s the first time I've run into this warning.The detailed warning message is below:Warning Failed to connect to Red Hat Virtualization plug-in: Failed to login to platform service: The remote certificate is invalid according to the validation procedure.It happened after I migrated from the VBR server with SQL Express to the new VBR server with PostgreSQL.All Hosts and repositories are pure Hyper-V environments. There are no Linux servers or repositories.It’s easy to fix this issue. I rebooted the VBR server and ran the backup configuration again. The warning message is gone. Does anyone have the same experience? 

Yesterday I came across an interesting bug using version 12.1.1.56 I have been creating plenty of jobs and test jobs to Wasabi without issue for quite a while. For some reason, one of the jobs I created gave me an error.  I thought this was odd as I had not enabled rollbacks, and there isn’t even a setting to adjust the setting for transform previous chains into rollbacks on Object Storage jobs.  Following KB4390 https://www.veeam.com/kb4390 There are 2 easy PowerShell commands to fix this issue.  The first command will find all jobs using the Transform previous backup chains into rollbacks option. Get-VBRJob | where {$_.BackupTargetOptions.TransformIncrementsToSyntethic -eq $True} It found the job in question, along with one of my snpashot jobs that had it enabled as well. Once again, slightly odd as it doesn’t use this feature. There are 2 ways you can resolve this using powershell depending on if you want to use Forever Forward, or Synthetic Full jobs. Disable Transform previous bac

Hello everyone!After reading some of your experiences and submissions, specially @Madi.Cristil s one, I’ve found some time to tell you mine,this is a personal story, here we go: Back on 2000 - 2001 , I was an exchange student flying from Spain to the US, without knowing any English at all, just few words, the worst pronunciation ever, scared and to the unknown.At the beginning, it was fine to take pictures with “single use cameras” (I’m felling very old right now)but after a while, I saw on Walmart a Digital camera, a Sony Cybershot!! OMG! 😱 1.3mpx of super high quality pictures, jpeg, TIFF and GIF! a monster!!I bought it, and quickly I started fulling the 64MB memory Stick!! tons of pictures, fortunately, the Computer I’ve got in the house had a 100MB ZIP Drive, so I started backing up my pictures in a Zip Disk, of course, encrypted, but nothing else.I came back from my exchange, life continued, and I just stored my ZIP Disk in the safe with other memories, letters, gifts, etc.Once i

Nutanix has been around for sometime but I have only recently decided to take a peak at it.I am going to install a single node cluster nested in my Proxmox homelab.First step is to create your Nutanix account (free) and login. Head to the Nutanix Community Edition page by pressing launch.Press Launch under Community EditionISO and InstructionsDownload the ISO and then upload into your Proxmox. Now time to setup the VM. Create the VM Choose the ISO.ISODefault Settings You need at least 3 disks and 2 of them need to have SSD emulation turned on. The first disk can be relatively small but the other two mush be at least 200GB200GB diskLast disk for data.3rd diskIn my case I chose 4 sockets 2 cores for 8 vcpus and processor type hostCPUMemory AllocationNetworkSummaryAfter creating start the VM.StartAfter the boot screen completes eventually the Nutanix CE Installer will appear.The Use column should fill out automatically but you can edit if need be. Keep in mind that the Hypervisor boot dri

My console stopped opening yesterday, crashing and complaining about clr.dll. There’s a R&D post about removing the user.config file (Here), but that didn’t work. Anyone else recently seeing this? Log Name: ApplicationSource: Application ErrorDate: 12/7/2023 6:27:37 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: MANBK-CARM-VEMDescription:Faulting application name: veeam.backup.shell.exe, version: 12.1.0.2131, time stamp: 0xf82aa70aFaulting module name: clr.dll, version: 4.8.4645.0, time stamp: 0x648f6f63Exception code: 0xc0000005Fault offset: 0x0000000000018551Faulting process id: 0x2064Faulting application start time: 0x01da290041bfb33eFaulting application path: C:\Program Files\Veeam\Backup and Replication\Console\veeam.backup.shell.exeFaulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dllReport Id: 53fe947b-0942-450e-9476-4cda770d3a62Faulting package full name: Faulti

Hi Everyone, Quick poll here. There might be some interesting news coming.  

Patched VBO to the latest version; installed windows updates recently; tested console restore and backups and both were fine. however, notcied the next day that portal is not functional.  The portal appears, you input credentials, it takes you to azure portal; you input credentials again and url chanegs to the portal again and it just stays thereLogs show14.03.2024 09:30:11.727]   55 (19664) Authorization started (grant type: OperatorAccessTokenResponse)[14.03.2024 09:30:12.260]   55 (19664)  Authorization succeeded 14.03.2024 09:30:12.261]   55 (19664) Error: IDX10634: Unable to create the SignatureProvider.Algorithm: 'RS256', SecurityKey: 55 (19664) Type: System.NotSupportedException this algo is supported in Windows already checked  We are using the same self-signed certificate when restorng using the VBO console which works fine and the backups have been runnig as well;  I have already tried a new self-signed certificate for restore app; still the same issue.  Veeam support advised

Hi guys,I need some help to export my incremental files on tape.Policies: Archiving Full backups once a week on new tapes and used tapes are exported, archiving Incremental backups on new tapes and used tapes are exported. Entity Configuration settings Media pool Full and incremental backups use different media pools. Media pool (retention) Protect data for <desired period>  Media set (retention) Create new media set for every backup session Source (backup job) Forward incremental backup that runs daily with synthetic  Tape job Export current media set.. on specific days Scheduling Forward incremental job running every day with weekly full backup. Tape job has been scheduled to run every day after primary backup.  When I configure only Full backup archiving everything works fine, my synthetic are created the Friday night, the tape job is scheduled the Saturday morning, the job copy only the latest backup files.Now I have configured my job to copy the

Azure PortalIn order to use Immutability with Azure Blob Storage, you must setup Storage Account creation.On the “Data protection” tab of storage account creation:Disable “soft delete for blobs” Enable “Versioning for blobs”  Select “Keep all versions”  Disable “Version-level immutability support”Set “Blob public access” to Disabled and create a container. Give the container a name and set the “Public Access Level” to “Private”.Container-Level SettingAfter creating the Storage Account with the required settings, create a new container with the following setting:Expand the Advanced section, and Enable “Version-level immutability support”Notes:Do not configure lifecycle management policies for the container`s data.Do not enable any default immutability policy at the storage account level.After the Container is created, go to Security → Networking, Access Keys and copy the key1 key. Veeam Data Platform SettingLaunch New Object Storage Repository WizardAdd Backup Repository, Object storag

Lets say a periodic legacy backup copy job “LEGACY” was configured to copy 3 source jobs: JOB-A, JOB-B, JOB-CDuring the creation of the new-format backup copy job named “NEW”, only source job JOB-A was initially included.  On the storage tab, target mapping was used to point to the “LEGACY” job.   This triggered a format upgrade for all items inside the LEGACY job, creating a new target named “NEW”.Now I want to edit the “NEW” job to add “JOB-B” as an additonal souce.Do I need to return to the storage-tab of the job and choose target mapping and select “LEGACY” again?What happens if I do?Will it recognise that this chain has already been converted and correctly target “NEW” instead?

Hi Everyone,I need some guidance on deploying a new hardened backup repository as a SOBR extent. Current we have a customer which uses a regular windows repository as extent doing copy to an Azure blob. We need to move all the content (backup chains) from this Windows repository to the hardened one (using imutability). I´m trying to find out the appropriate way to do that. There is only one performance extent (with data locality policy) and we are not able to add the hardened repo because all extents need to have same imutability settings. Cannot evacuate because there is no other extent to evacuate.How can I accomplish this without having to download metadata or resync data with Azure blobs? Our goal here is to only offload old repo content to the hardened repo and set them as extent copying data to Azure, if possible, doing little to no change on Azure tiers/blobs to avoid costs. 

Hello,I have 2 Hyper-V hosts:Host no.1: several VMs, VM replicas from Host no.2 and a VM with Veeam B&R server (v12) Host no.2: several VMs, VM replicas from Host no.1 including a VM replica with Veeam B&R server (v12)The repository for backups and replicas is an additional NAS server.I need to completely reinstall Host 1, so I need to temporarily move everything to Host 2 - including the Veeam B&R server.These are production servers, so the whole operation must be stable and fast. What is the best way to do this?

My story goes back many years ago. At the time I was working abroad for an American real estate company. My manager was a decent person but very much into the whole "I am a manager" thing. He loved playing mind games with the staff by giving them the evil eye when he was not pleased and making elusive comments about imminent cutbacks in staff with a regretful but obvious smirk on this face. He also enjoyed demonstratively taking people into the server room for confidential talks. One day he asked me to come and have a talk in the server room so I knew that something unpleasant was afoot. He explained that the branch office in K. needed to do a server upgrade and he would have gone and performed the task himself but....blah blah. In short there was obviously something wrong with that office and he did not want to go.I had a very early flight and arrived at the branch office before 8 am. Much to my surprise the local boss was already there. He immediately informed me that he was a former

Hey y’all, doing a bit of testing with VB365 v8 and documented my way through getting PostgreSQL setup on a ubuntu 22.04 server for this purpose and it seems to be working very well. Here’s the link if you think it will help you out! https://www.koolaid.info/postgresql-on-ubuntu-2022-4-installation-configuration-for-veeam-purposes/

I’ve seen this multiple times now with VMware. You cancel a task via vCenter or the ESXi UI and it just stays there hanging and nothing further happens. Normally this situation resolves itself after some time, but just last week I had a case where the task never stopped. While the Webclients weren’t really helpful in that case, we were able to cancel this task with the ESXi commandline.Warning: Interupting certain tasks, for example snapshot consolidations or Storage vMotions, can lead to issues or corrupted VMs. So only do this if you don’t have any alternatives and need the task to be canceled. And better have a backup at your hand.SolutionStart the SSH service on the ESXi host where your VM is registered Connect via SSH Query the VM ID: vim-cmd vmsvc/getallvms Query all tasks for this VM: vim-cmd vmsvc/get.tasklist “VM ID”Check the Task information: vim-cmd vimsvc/task_info “haTask….” Is the task still state still active? Note: The screenshot is just an example; the task state is s

Let’s walk through the steps to perform a Physical to Virtual machine (P2V) conversion using Veeam Backup and Replication (VBR) to migrate a physical server to a Cluster virtual machine.Install Veeam Agent on the Physical MachineInstall the Veeam Agent for Microsoft Windows on the physical server you want to convert. Ensure the agent is properly configured and connected to your Veeam Backup and Replication server.You can also create a Protection Group to install it. We will show you how to convert it from the Veeam Backup and Replication Management Console.Create a Protection Group and add the physical machine to the protection.Ensure you select the Install Backup agent. Create a Temporary Backup JobIn the Veeam console, Select the Protection Group and create a new backup job for the physical machine.Select Server Type and Manage by Backup Server Mode.Assign Job name and Description.Select the entire computer in backup mode.This is just a temporary job. Change the Retention policy to 1

hi Veeam communityI want to run a sclae out repository and I need your help and experience.I want to buy suitable storage for all three tiers (performance, capacity, archive) and I want to have immutable capability in all three levels.Your experience and guidance can help me make the right choices.What features should be taken into consideration when choosing storage, what storages have you had experience working with and were they good experiences.Thank you in advance for all your comments   

According to Veeam documentation, migrating a legacy VBR (v11) to a new one (v12.1) requires disabling the services on the current server. This legacy server retains the ownership of all the Azure blobs used as scale-out repositories. All blobs are used to long-term backups. Regular short-term backup jobs are configured to local disk repositories.  My question lies in the moment after the restore process ends (with the option to migrate flaged). Do I just need to request ownership of the blob or is some additional procedure required to re-enable this scale-out repositories. Is there any chance to lose the chain inside this blobs after the restore? If restore fails somehow, can I just jump back to the legacy server? I cannot risk losing the backup chain held there, cause we are talking of dozens of TBs.  If there is some guide to migrate VBR with Azure blobs or anyone has ever had this need somehow, can please share the steps taken?

Hi allMany people in the community probably are already aware of the fact that in Q4 of 2023 Microsoft will launch in preview their own 365 Backup and Archive service.For those who doesn’t know yet, they are now informed 😎.More info can be read and viewed on following links : Welcome to Microsoft Inspire 2023: Introducing Microsoft 365 Backup and Microsoft 365 Archive - Microsoft Community HubMicrosoft 365 Backup and Microsoft 365 Archive My goal is to have a summary of pro’s and con’s of this MS service vs the proven existing Veeam solution!As a partner we are offering at this moment a Veeam SaaS solution and my idea is to keep it that way of course 😊, but therefore I have to convince the cloud team that this is still the best solution to offer to our customers.The MS backup solution is a built-in solution to backup M365 (Onedrive, Exchanage and Sharepoint).The MS archive solution is to put less frequently data on cheaper cold storage but can still be directly used.Is this Microsoft

Hello, I am facing a connection problem between my VBR and my VEM.I applied a hardening since the connection with the local administrator account (built-in) is impossible I cannot find what could be blocking it, still investigate.MFA was enabled in VBR, so I had to create an entry for my built-in administrator account as a service account with Veeam administrator privilege.Unfortunately the session failed to openThe connection with another service account with admin privilege works..Any idea? The account must be assigned the Veeam Backup Administrator role. In term of security I’m not a big fan cause I have an account with admin right without MFA. How do you configure VEM on your side?

Hi Team, My customer has a setup for StoreOnce (3660 with Firmware 4.3.7) and Veeam (12) configured with Veeam Standard license.Scenario 1:Customer tried to take a VM backup to one of a catalyst store which failed due to licensing issue in the logs. However, I did not get any documentation mentioning Veeam standard edition doesn’t support catalyst stores. As per Catalyst store configuration I double checked and its as per HPE standards.Error: “Backup to HPE StoreOnce Catalyst requires valid enterprise edition of Veeam Backup and replication.” Scenario 2:Customer tried to back up the same test VM on StoreOnce NAS share and that passed successfully. Resolution:Could you share me any documentation which says the Veeam standard edition does not support StoreOnce catalyst store? Are there any changes in Veeam that needs to be done to support the above Below are the backup logs captured?