Community

 Hey all!I thought this would be something of your interest therefore I decided to share it in here: On March 29th at 12 pm ET ,Veeam’s Edward Watson, Principal, Product Marketing, will do an exclusive #AMA about NEW Veeam Backup for Microsoft 365 v7 on the official Veeam Twitter account: https://twitter.com/Veeam. He will be answering questions about the newest features, M365 backup and more.If you have questions ahead of time, feel free to submit your questions below here in the Community Hub or use hashtag #AskVeeam on Twitter. Best, Madi

I’ve been using Agent for Windows for a long time. I’m setup to do scheduled daily Entire Computer backups to Shared Folder (on DSM) with periodic Active full backups early one morning each month, with periodic health checks one other morning each month, and with 32-days retention. It’s been rock-solid dependable. Until Windows 11, that is. On Windows 11, I’m seeing two issues:First, and most critical, is that it doesn’t seem to be respecting the periodic full backup setting or reliably respecting the 32-day retention cleanup of obsolete backups. Three months in a row now, I’ve looked the morning after the full backup was supposed to have run and found only the incremental ran--or even it didn’t run (see next issue). I’ve done full backup on request from the UI. This morning for my laptop I have at least 71 backups, full or incremental, with 33 incrementals newer than the second oldest full. The oldest full is 12/25/22--69 days old, with newer full sets on 1/30/23 (33 days) a

CDP Policy of 5 minutes and above  - must have a VMware STD license because of access to vSphere APIs for I/O filtering  ?

Today we updated our cloud connect server to v12. Once that was complete we upgraded two of our managed clients running Veeam backup and replication to v12.My issue is once the Tenant side was updated to v12 I am no longer able to connect to the service provider. I believe this is the related log…[14.03.2023 16:07:00.582] <117> Error        A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respondBut this is only happening from tenants that updated to v12, all other tenants running v11 are able to connect without issue.We have a support case open, Case # 05943021

Further to my earlier question about backing up between networks, I tried to start removing the Veeam components that are installed on the Hyper-V hosts.  One of the hosts is being a real pig and will not remove with error ‘Connecting to installer service Error: The RPC server is unavailable.’  On checking, the Veeam Installer Service is not running and will not start with an errors 7009 and 7000.  Trying to delete the service as per KB2263: Failed to start service ‘VeeamDeploySvc’ - The system cannot find the file specified. does not work either!  Any suggestions on how to manually remove Veeam components from this host? Slight curveball is that it is Windows Server Core 2019.Thanks!

Running the https://docs.kasten.io/tools/k10_primer.sh  for Kasten 10 I eventually get Validating Provisioners: driver.longhorn.io:  Is a CSI Provisioner  -  OK  CSI Provisioner doesn't have VolumeSnapshotClass  -  Error  Storage Classes:    longhorn      Valid Storage Class  -  OK I’m running Longhorn 1.2.4 and according to this (https://kubernetes-csi.github.io/docs/drivers.html) it looks like I need v1.5 for a CSI driver? But Longhorn only goes up to 1.4.0. How do I get this rectified? This product looks extremely useful for our environment.

Veeam Backup and Replication is comprehensive data protection and disaster recovery solution which is capable of creating image-level backups of virtual, physical servers, cloud machines, and restoration as well. You may encounter the following errors when installing the Veeam backup and replication tool “VEEAM service is unable to start, error 1064: An exception occurred in the service when handling the control request”. Therefore, I will be showing you the steps on how to resolve this issue very quickly. Here is a detailed link to this post.If you are here reading this troubleshooting guide "new Veeam Backup server but then Veeam won’t start", this means you must have recently instal

Hi all,if you are planning to connect your Veeam Backup for Microsoft 365 to your Veeam ONE 12 infrastructure and start monitoring this type of backup as well, one thing to keep in mind is the license versions of the two products.Below the licensing-level compatibility matrix:https://helpcenter.veeam.com/docs/one/deployment/license_types.html?ver=120 As for the actual connection, in my case I ran into the following issue:

Is that any way to trigger notification when backup job start?

Today I will share a customer success story of Veeam Disaster Recovery Orchestrator. This customer is looking for a disaster recovery solution to protect production virtual machines. VMware SRM and Veeam are common Disaster Recovery solution in my region. Existing EnvironmentPlatform: VMware vSphere 6.7 and vCenter 6.7 Storage Array: NetApp ONTAP Storage Backup Solution: Veeam Backup and Replication v9.5 RequirementsAutomatic data recovery and failover No impact on production environment during data recovery and failover Data recovery in an isolated network environment for internal testing Application-aware processing Test DR plans with zero impact to the production environmentAfter the discussion with their system team, I listed out the comparison table of VMware SRM and Veeam (refer to below table) for reference. Finally the

Hello Everyone,I pass the VMCE exam today. Anyone can help me how can I get the certification? I need to submit the certifcation as documents one of my upcoming project.Thanks in Advanced.

In very restricted environments, What is the best tool to test required open ports for Veeam distributed components requirements?

My backup repository is an iSCSI mount from some NAS which can take snapshots on iSCSI LUN I’m thinking about a very simple backup plan with 30 days retention, and monthly snapshot and replicate the iSCSI LUN. If I need to restore something e.g. 3 months ago, can I just dismount the current repository, mount the 3 months old iSCSI snapshot, rescan it and restore files from it?   

Due to other things pending the outcome of our V12 testing, I figured I’d just update V12 in production :) Worked great, no issues, my backup speeds actually look fantastic too. Still on SQL, most likely going to migrate to full blown SQL servers this week as we have enterprise licenses. I don’t think there are any advantages to postgres, but I could be wrong. The new license for file to tape is what I am currently investigating as we archive a ton of data and don’t want any surprises.   

I am having a hard time finding any information regarding the v5 which will come this month.Does anyone have a sources for new features, compability and what we need to know?Was asked by deploy this for a customer this morning from the new v12 vbr console, but doesnt seem like the azure plugin for vbr is updated since it said you would need v11a..I just saw Veeam had a webinar for v5 2 days ago, sorry I missed that, but perhaps there is a recording?Would also be interesting to hear if Veeam backup for Azure does have a better fit than Veeam Agents for small azure customers with 1-5 vms? with veeam agents, vspc v7 and the seucre mode we can backup directly from the veeam agent to wasabi, with immuability without going through our vcc/vspc server regarding the traffic. How does VBA compare?

Dears,We’re facing an issue since yesterday that we have a VM on vCenter that we’re trying to take a backup from it using Veeam BR, The VM has 3 disks and dependent as shown in the vCenter VM Settings. The issue now that we’re facing is that 2 disks of the 3 is backed up successfully and third one is stuck at 0 B   

I was trying to restore an on-premise VM into Azure, which I had done many times before, and I got this error:"Failed to process request: (Unauthorized). AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app ..." I thought there was something wrong with our Veeam Azure appliance, so inside of Veeam I tried to Edit the appliance or Rescan the appliance, and I kept getting a “Value cannot be null” error.I opened a ticket with Veeam support and here is what I learned:The Veeam Azure appliance has nothing to do with a restore from on-prem to Azure.  That is used for running Azure backups and for performing a backup copy from Azure to on-prem. In Veeam, go to Manage Cloud Credential

Hello,I have updated some of the V12 VBR servers with the patch from Tuesday.The server is running and backups are possible.But I see on all servers a warning for a system process ( Veeam Console → History Tab → System).Are you seeing this warning/error, too? Edit:Seems to be a timing issue with both V11 and V12.The next planned execution of the Catalog Cleanup on day later runs successfully.So, It’s a “cosmetic” issue.

I added a 10 Gbe NIC to my server hosting my SMB repository. That new NIC has a different IP address. I have a bunch of machines that backup via Windows and Linux agents and I don’t have the option to edit them from the Veeam Backup & Replication console (the Edit menu item is grayed out). Most of these machines are currently offline/not accessible. I’d like to avoid remoting into or physically going to each of these machines (so many) - how can I change the IP address of this SMB repository within VB&R console so the machines will pick up the revised repository when they come back online to perform a backup?

After patching our VBR v11 to the latest 2023 patch due to the latest CVE reported, I’m asked to "Select Servers to update….”.Some of those servers in the list are production. Does this process require a reboot on those servers?Can I wait for a bit (days until a team decides when to reboot the aforementioned servers) and hope that no backups will be impacted if I don’t update right now? RegardsO

Hey guys,So I created two VMs in my AWS console and I installed VBR in 1 VM and planning backup the other VM. Both VMs are in the same region and also have the same gateway but unable to ping the IPs of both the VMs. Can anyone suggest what should be changed here?

Hi, I have VBR11. Have added Debian vm to Physical Infrastructure. Agent and other linux components were installed successfully. Added account with sudo privilege. When I try to create backup of Entire Machine/Volume or even File Based I get error : Error: Failed to execute agent management command startBackup. table JobSessions has no column named end_time Unable to run query. which leads me to nothing. What seems to be a problem?