Discussion Boards

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, so I could just se

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 desirable, but unfortunately, I'm not able to comment on the decision process behind this; and regrettably, I have tested in lab to upgrade a v11 Veeam environment that violated the new SOBR limitations, and I did not receive a warning during upgrade either.I am sorry to hear that this situation occurred, as historically Veeam has tried to be very transparent in all such matters, but I'm afraid that I cannot find where it was advertised.I have alre

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 of the migrated mail, the next

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）。

One thing I really miss from other backup products I have managed, more detail displayed about what an active job is doing.  For example, a running Backup for 365 is taking a really long time.  The whole job summary says how many objects it has processed, number of items processed and the data transferred.But it does not show the same details in the actions. It only shows the name of the item and how long it is taking.  It would be really handy to know how many items and how much data has been transferred at the object level. Would help me understand what is going on and would allow me to investigate what changed to prompt a difference in backup times. 

So we're 7 days out from the big day, and thought we could put a collaborative Spotify playlist together for the event. I've added a couple of obvious tracks, but feel free to add more relevant tracks. Let's get an amazing playlist to match an amazing event.https://open.spotify.com/playlist/2iVGkhPztcEQyW7BrNJYGd?si=6a29d22cae4349d2

Any idea for this? It’s pure Hyper-V with Azure, not AWS. 1/31/2023 10:06:49 AM Warning Failed to connect to AWS plug-in: Failed to login to platform service: The HTTP resource that matches the request URI 'https://vbr11:9402/api/v1/account/login' is not supported.  

HiWe running an VBR11.0.1.1261 using SOBR with an QNAP as capacity tier. QNAP is supported S3 repository by Veeam and Veeam is partnering with QNAP. Also Immutable option should work as stated in https://www.veeam.com/sys469.After running while this setup we start getting strange errors.  Error deleting multiple items from SOBR invalid URI - which refers to cleanup operations on the S3 repository base on retention policy. VBR runs this operations in regular intervals.  In Veeam One - Data Protection View we get error type [v] (never seen before) and a Knowledge information that stats: S3 object storage added to VBR as repository may face overflow with small metadata file of 0 kb size. Cause: malfunction in object delete algorithm. Resolution - contact support to get a private fix. To get backups to SOBR working again we to delete objects from QNAP using qnap utilities. Now we try to synchronise SOBR with VBR DB but it takes forever. Has somebody came across this situation with AWS S3 o

Hello all,As many of you may have noticed, the VeeamON AMA did not broadcast as scheduled. There were some technical difficulties, and we apologize for that. An update on the new date for the AMA will be shared here once available. Until then, continue checking out the pre-event sessions that are available now on the VeeamON Attendee Portal! https://www.veeam.com/veeamon 

🐱Hello all,  It's less than three weeks until VeeamON Miami 2023! The anticipation is building, and we can feel the excitement in the air!But, before that @Rick Vanover and Product Strategy team have prepared a LIVE Ask Me Anything (AMA) session! Join us on May 11th for a chance to ask any questions you might have about Veeam and VeeamON! Get a sneak peek at the exciting content that will be featured in both the in-person and virtual experiences. Don't miss out on this incredible opportunity to connect with the experts and get the answers you need!Use the link below to register today:  https://connect.veeam.com/flow/veeam/veeamon2023/attendeeportal/page/sessioncatalog/session/1678240245854001tCwA Best, Madi

Hi,We have published VBR plugin to a tenant in VMWare vCloud director for VBR v12. It was successfully published, roles and self service configured. However, when i log into customer tenant from vCloud director and goto veeam protection under more. it pops up Error "Unable to connect to the Veeam backup infrastructure. Please contact service provider". Thanks.Best Regards,Farhan Ali

I have a problem when I tried to use quick migration jobError shows2023/5/5 下午 05:21:18 :: Copying snapshot files Error: Failed to open VDDK disk [*********] DRAP/AP.vmdk] ( is read-only mode - [false] )Logon attempt with parameters [VC/ESX: [XX.XX.XXX.X];Port: 902;Login: [root];VMX Spec: [moref=71];Snapshot mor: [71-snapshot-1];Transports: [nbd];Read Only: [false]] failed because of the following errors:Failed to open disk for write.Failed to download disk 'vddkConnSpec>'.Agent failed to process method {DataTransfer.SyncDisk}.  2023/5/5 下午 05:22:57 :: Failed to process VM DRAP at Friday, May 05, 2023 17:22:57 Error: Failed to open VDDK disk [*********] DRAP/AP.vmdk] ( is read-only mode - [false] )Logon attempt with parameters [VC/ESX: [XX.XX.XXX.X];Port: 902;Login: [root];VMX Spec: [moref=71];Snapshot mor: [71-snapshot-1];Transports: [nbd];Read Only: [false]] failed because of the following errors:Failed to open disk for write.Failed to download disk 'vddkConnSpec>'.Agent failed

Guys, I don’t know if everyone is aware, but VMware has this course for free until 06/15/2023: https://learning.customerconnect.vmware.com/site/program.do?dispatch=showProgramSession&id=18657ec2-4eb2-11ed-b5a6-0cc47a352292You also win 1.500 points in VMware Reward and a chance to win a VCP Exam voucher.More information here: https://blogs.vmware.com/learning/2023/04/27/invest-in-your-cloud-skills-and-earn-1500-rewards-points/

In this post, I will show how to create the Orchestrator Plan in VDRO v6 and execute the Datalab Test.EnvironmentVMware vCenter Server Appliance 8.0 VMware vSphere 8.0 Veeam Backup and Replication v12 Veeam Disaster Recovery Orchestrator v6 Microsoft SQL Server 2012 (Protected VM)Remark: This architecture is NOT used for production environment, it can be used for home lab only.  For architecture, please refer to this link https://helpcenter.veeam.com/docs/vdro/userguide/architecture_overview.html?ver=60LicensesVMware vCenter Server Standard Edition VMware vSphere Enterprise Plus Edition Veeam Data Platform – Premium Edition v12 Veeam Recovery Orchestrator v6Configuration FlowCreate a virtual lab environment in VBR Setup a VM replication job in VBR Create an Orchetration plan Execute the Readiness Test Execute the Datalab Test For details of virtual lab and orchestration plan configuration, please refer to my blog:https://wuchikin.wordpress.com/2023/05/03/veeam-disaster-recovery-orchest

Hi, is it possible to use the same VUL license on two different standalone VBR servers ?the VBR in the main site doing the backup to disk and then backup copy and replicate only one VMto the VBR server in the DR site to his local repository. the license is for 5 VM bundle and in practice only one VM is backup and then copy and replicate to DR.Thanks

Forever Forward Incremental Backup + Backup Copy job Tape Out.With one Forever Forward Incremental Backup job can we configure multiple tape out Backup Copy job with Virtual full option for each day targeting to different media tape group.Primary Job will be one (forever forward incremental backup job) and a separate Backup copy jobs for each day Monday to Sunday.Will it work. And  if we restore tape backup from any one day (Monday group to Sunday group) i hope will it restore the full backup.

Outlook PST incremental backups ( Block level )  is possible in Windows Agent based backups.

Hey guys,  i run a small server in a NGO, our Veeam is still in version 9.0 without support since 2019. I’ve recently run into a backup problem, and our support IT company, told me that i should get a newer version of Veeam, and install in a new  VM(5th).I asked if it was possible to upgrade, which they said, no, and now Veeam only does subscriptions, and proceeded to give me a budget for 3 year. From what i read perpetual is still available, just more expensive than subscriptions, but what about upgrading? Could i not install 9.5 on a new VM, renew and upgrade up to 12? What do you think?

When I Backup Job compleate Then Backup Copy Job Is next run .Can Setting Backup Job Copy Run Completed is Call  Backup Job is Runremark : because i can’t setting Backup Job Schedule Time because I don’t know Backup Job Copy Long time to backup .  best regards

Hello, does anybody know if Hyper-V backup needs enabled checkpoint creation in Hyper-V console ?Regardszleffa

Fresh default install of B&R 12 on Windows Server 2022."Veeam GCP Service" and "Veeam Kubernetes Service" refuse to start. Produce the following error in de System Log:“The Veeam Kubernetes Service service terminated with the following error: An exception occurred in the service when handling the control request.”

Hi guys,We have to take backup from large number of virtual machines in our environments and sometimes backup jobs are still running during working hours. It has impact on virtual machines performance. Is there any way to define backup window for jobs and backup/replication jobs pause temporarily? Thanks

Hi, I’m running a backup job of fairly big VM (HDD1 = 1 TB and HDD2 = 3.9 TB) using VEEAM 11.0.1.1261.After Deduplication and compression, the backup size ends up around 2.4 TB.The backup storage is a NAS mounted using an NFS connection. In the console, I can check that it still has 3.2 TB left.It has been working fine until last week. Error message : 28/04/2023 16:12:33 :: Processing ubuntu Error: No space left on device.NFS status code: 28Cannot get count from WRITE3res.Failed to download disk 'EvaBuntu_2 - Copy.vhdx'.Shared memory connection was closed.Failed to upload disk. Skipped arguments: [shadowSpec>];Agent failed to process method {DataTransfer.SyncDisk}. Why is my backup job complaining that there is no more space left while I have 3.2 TB left on my repository?Any advice much appreciated :)