Discussion Boards

I have what I hope is a simple question. What’s the best practice for the a high availabilty SQL server for the VSPC or Veeam ONE configuration database. I see in https://www.veeam.com/kb2301 how to deploy SQL AOAG for VBR and VEM. I’m not sure if this applies to VSPC or Veeam ONE.

Hi all,I want to share with you a problem I encountered on a customer while upgrading Veeam Enterprise Manager from v11a to v12 latest release. The environment This is a simple Veeam v11a installation, VBR + EM.The customer uses Windows Defender for Endpoint (Antivirus/EDR) on the server, the exclusions are correctly set as per KB https://www.veeam.com/kb1999. The upgrade..Ouch! After successfully updating a dozen Veeam environments to v12, I start this new upgrade with the confidence "It works!".Once I get to the end of the wizard and start the update, at some point you receive the error "Failed to create website 0x80070020".

Hello guys! It’s the first time I got this error message in one of my backup jobs. I got it in random virtual machines, after a retry the backup is ok.I check the logs:On the VBR I have this:“Error        Failed to construct ClientAgentProtocol. (Veeam.Backup.Common.CRegeneratedTraceException)[27.03.2023 10:06:42.851] <46> Error           at Veeam.Backup.Common.CExceptionUtil.RegenTraceExc(Exception originalExc, String formatString, Object[] args)[27.03.2023 10:06:42.851] <46> Error           at Veeam.Backup.AgentProvider.CClientAgentProtocol..ctor(CBaseAgentService svc, Boolean redirectOutput, Version version, IAgentProtocolLogger logger, IOutputAnalyzer outputAnalyzer)[27.03.2023 10:06:42.851] <46> Error           at Veeam.Backup.AgentProvider.CClientAgentProtocol..ctor(CAutoRef`1 svcRef, Boolean redirectOutput, Version version, IAgentProtocolLogger logger)[27.03.2023 10:06:42.851] <46> Error

Hello Everyone,SOBR has 10 NFS shares repos with Linux gateway, each time resync the repos from SOBR, all Repos become unavailable and I have to open each one’s properties and click finish to become available again.Any thoughts?

I'm seeing this error "Failed to process VM: Failed to create MachineMutex" when doing storage snapshot. The first try fails but the 2nd try succeeds and usually the issue comes and goes. Failed to create snapshots on primary storage: Failed to wait mutex sandiscover7c39d713-bdbb-40f1-ac8d-af87774de299_b72e5bb7-87e2-4802-9043-2d6a76f9052d: timeout 600 sec exceededFailed to create storage snapshot for datastore abcdef: Failed to wait mutex sandiscover7c39d713-bdbb-40f1-ac8d-af87774de299_b72e5bb7-87e2-4802-9043-2d6a76f9052d: timeout 600 sec exceeded Who has seen this issue and cause/resolve info? 

I am not able to install Veeam Backup & Restore on standalone W11 machine.Keep getting:Exception has been thrown by the target of an invocation.andFatal error during installation. I was successful installing on internet connected W10 machine, but have not been in standalone W11 machine. Any insight will be greatly appreciated.

Hello Guys, is it possible? Storage Spaces Direct for Veeam Server (only one Server NON cluster)Disk whit trww way mirroring?How many disk failure a can have? Thaks a lot

Thank you for checking out my ‘What I Wish You Knew About SureBackup’ session! If you have any questions, please feel free to reply below or create a new topic within the Veeam Community Hub, I’d love to talk to you about how you’re using, or planning on using SureBackup within your organisation or for your customers. As mentioned on the session, if you want to see my ‘Deep Dive’ into SureBackup from a recent Veeam User Group talk, you can find the YouTube video embedded below. 

Hello Everyone,Someone asked this question in Nutanix Forum:“We are running asynchronous Protection Domains and also employee Veeam backups of VMs. If we failover to the secondary site and then failback to the primary site, Veeam no longer recognizes the VMs in previously created backup jobs. We have to delete all the old backup jobs and set them up again. This is with ESXi hosts. Is that normal?”Didi anyone face this issue before and how to fix it?

Hi, since this is not really a Veeam question I will not post it on the forums, so I’ll post it here ;-). We are using backup from storage snapshot on our NetApp running Ontap 9.12.1 and Veeam 11. Every time Veeam is taking a backup, lots of errors show up in the Netapp eventlog. Errors like this:tsse.scan.start.failed: 'Cold Data Scan' failed to start on 'VeeamAUX_iscsi_netapp_02_Rescan_68vTfMjeYHNw4M9BNF0NKb' - Scan was stopped.and other numerous errors regarding SIS. It appears that Ontap is starting a SIS operation to duplicate the volume that is mounted from the snapshot by Veeam. However, Ontap can never complete this scan since Veeam dismounts this volume once the backup has finished. This is filling up the eventlog of the Netapp quite substantially and we risk missing critical events due to this clutter.Does anyone know of a way to have Ontap not start a SIS scan when Veeam mounts a snapshot as a temporary volume? p.s. sorry f

We can well backup Oracle databases sitting on ASM clusters using the RMAN plugin:Veeam Plug-in for Oracle RMAN - Veeam Plug-ins for Enterprise Applications But there is more to ASM clusters. You might also have ACFS as an Oracle-homed cluster FS. It is not used for the database files themselves as these are located in the ASM itself. ACFS is rather meant to host supporting files around the databases throughout the cluster (general purpose files, shared database homes, administrative files, log files, trace and audit files, scripts, etc.).It appears to be necessary to backup those files in conjunction with an ASM/RAC clusters next to the pure DB using RMAN and the Veeam plugin as well. Dead-end #1:Most Oracle systems run on physical systems for the “unconventional” license requi

When troubleshooting vSAN issues, we need to complete understanding of the vSAN environment. Today I will introduce a good tool "vSAN Objects Viewer" that quickly converts vSAN information from text to graphics, including the followings:vSAN cluster topology vSAN nodes information vSAN disk group information VM and object composition Component distribution and statusRequirementsVMware vSAN OSA 6.x/7.x/8.x DockerDeploying the ToolPull the Docker image by running the following command:docker pull projects.registry.vmware.com/fling_vsan_objects_viewer/fling_vcmd:v1.5.7

It has happened again… the very reason we encourage multiple media types in the 3-2-1-1-0 rule.SanDisk Extreme & Extreme Pro devices have firmware issues causing data loss and devices becoming completely unreadable.I don’t want to rewrite the article verbatim but one user reported a lot of read/write errors as the drive approached halfway consumed, and then upon disconnecting & reconnecting the drive appeared as unformatted.SanDisk have stated a firmware fix will be available soon, but if you’re using these for backups or data offloads, be sure it’s not your only data copy…Original Source: https://www.tomshardware.com/news/sandisk-extreme-portable-ssd-suffer-sudden-failures-wd-responds

Hello community,,a new cumulative patch for Veeam v12 has been released this weekend:https://www.veeam.com/kb4420Many resolved issues..don’t forget to install it! 💚

Hello Everyone,I have a challenge in decreasing the backup window for 60TB Oracle DB which takes 16 hours with transfer rate 1GB/s against Networker which takes only 10 hours.Current configuration VBR v12, Oracle RMAN plugin with 10 channels, Veeam basic compression, SOBR Repo performance mode with 10 NFS shares on Pure storage, gateway server auto.Network speed 40GB with jumpo frame enabled. 

I wanted to share this just incase it helps someone else. I was getting the following errors in Veeam B&R Community Edition 12.0.0.1420 when trying to add/rescan one of my eight Hyper-V hosts. These started occuring when moving towards a full block on NTLM in our environment.Disks and volumes discovery failed Error: A security package specific error occurred. RPC function call failed. Function name: [GetSvcVersion]. Target machine: Network path not found or invalid credentials supplied.I verified DNS was good, disabled firewalls, enabled NetBIOS over TCP/IP, among other things. None of these helped.What ended up fixing this, was enabling the “This account supports Kerberos 128/256 bit encryption” on our Active Directory user that services Veeam. I’m not sure why they other hosts were fine, but this fixed the final one and should have been done anyways.

Hello,With Veeam Agent for Microsoft Windows FREE edition, I wonder if there’s a way to test the encryption key? I tried removing job but when restoring it still didn’t ask for password.And, can I re-add job after removing it or add the current jobs to another PC?Thanks

To back up data from M365 one can pre-create an app within AzureAD and connect via a certificate from VBM. Then no additional login to M365 is necessary:Step 5. Register or Select Azure AD Application - Veeam Backup for Microsoft 365 GuideKeep in mind that you do not need to select this check box if you have granted the required permissions to the specified Azure AD application beforehand and already registered its certificate in Azure Active Directory. If the Grant this application required permissions and register its certificate in Azure AD check box is not selected, Veeam Backup for Microsoft 365 skips the Log in to Microsoft 365 step and proceeds to

Hard disk 20 (3.5 TB) 1.9 TB read at 41 MB/s [CBT] - Can anyone tell me how long it should take this disk to complete backups? The backup ran for 13:21 hrs and failed to complete due to backup window setting. The backup window for the job is set for 15 hours 5pm - 8am. In addition how can i confirm if  a FULL or Incremental backup is running for a VM that failed backup.Backup type is VMware Image Backup. 

We have a file server that we are going to backup directly to an S3 compatible storage with immutability enabled.We want to put an incremental backup with full synthetic.Is full synthetic already compatible with S3 immutability with direct object storage?What do you recommend for the least resource consuming backup type? Thank you very much.

I have 2 Veeam V11 VBR servers. Which backup different servers. Servers are mostly VMWare, Windows/Linux and some Agent backups. No NFS/CIFS/ network share backups. At one point in time, these were 2 VBR servers in 2 separate data-centers but these data-centers got merged so now they’re located in the same data-center. They each use backup copy jobs to offload backups to Azure. For Azure, they’re using the same account, but upload to a different folder. Both servers have different proxies and different backup repositories. Backup repo’s are a combo of Windows and Linux (immutable). Each server uses a different SQL (server 2019)  back-end. Now, the idea is, to upgrade Veeam to V12 and merge these 2 V11 VBR servers into one V12 VBR server. Is this even possible? An upgrade to V12 can either done on the existing servers and then merge or I could build a new VBR server, install Veeam V12 and migrate both servers to the new one. The on-prem jobs cover about 15 days or so, s

Just want to run this by all the Service Provider Gurus here. It seems that for Multi-tenant O365 Veeam no longer wants you to place the console on the Cloud Connect server. Instead you install it separately and have it connected to the VSPC and expose a portal for restores. The old method of having the CC tenants go through the SP in the local VBR server is not seen as the optimal option. This diagram from the BP would suggest this:  Does that sound correct? I have been away from O365 for a bit now and the world is changing.

I found out there is a difference in the allowed number of active extents for an SOBR in VBR Enterprise Edition which could cause your backups to fail after upgrading from v11 to v12.This is the documentation for v11 (3 active extents max.):  And this is the documentation for v12 (2 active extents max.):  This is not mentioned in the release notes and it turns out you don’t get a warning during the upgrade.I raised Support Case 06063519 for this issue, this is the response from Veeam Support: I understand that the change in the policy is not desirab

More of a note about an effect I experienced using the new Microsoft Purview Compliance tool for Data Lifecycle Management and Retention Policies.We are new to M365, and are still migrating to it. As part of the setup before I started migrating, I did create a “Default Retention Policy” in Microsoft Purview for Exchange objects. I started migrating, setup Veeam M365 Backup to protect the migrated mailboxes, and all was good.As we expanded our use of M365, I reviewed the “Default Retention Policy” and learned a few more things about it. Long and short of the story, the default policy I had created was not applying to anything (for reasons undetermined). I deleted the retention policy and recreated it and all heck broke lose as the Purview retention policy applied.At this stage of our migration, roughly 1 TB of mail had been migrated, and our “every 30 minute” Veeam snapshots were keeping up easily.After the Default Retention Policy started applying to all

env:1、vbr11a、vspc6、backup server（win2022） with backup agent success。2、upgrade to vbr12、vspc7。3、backup server（2022） with bakcup agent failed。4、no Capacity/Archive tier，just back up to vbr local disk.5、Only two Servers（vbr + vspc）。