Solved

I recently updated a client from Veeam 11, I think .816 to the latest version available. Everything went as usual as I do these quite often but this one is throwing a pop up that states, "unable to upgrade plug-ins under the current user, please open the console under an account with administrative privilege's:" when I launch Veeam. I am logged in as a local administrator account and have updated this client in the past with no issues.I just click on okay and it opens up like normal. I also checked for any updates to the managed machine and there is upgrade option. This is a stand alone Veeam system with no remote components.I don't think it's going to impact the functionality but will know more after tonight's job run.Appreciate any feedback!Thanks,Poettone!

Hi, we have a strange issue where if we boot to VEEAM recovery media created in server 2016 or Server 2019 we can see the recovery EXT HDD but it shows as needing to be formatted and unreadable, we are currently using Western Digital My Passports formatted with REFS. Thanks in advance

Hi everyoneWe did install in our test environment Veeam VBR V12I want to test the gMSA.Installed as subscribed inhttps://helpcenter.veeam.com/docs/backup/vsphere/using_gmsa.html?ver=120Is it possible to run the Veeam Service with gMSA and so yes on which services I should run it on.Currently the Veeam services on this test VBR are running with the local system account.I have on a production VBR the services running with a service account worked fine but after the last crittical update I had to change the Veeam NFS service to local system as It did make my SureBackup during the mounting phase.Looking forward to your comments! 

Hello,I have upgraded "Veeam Backup and Replication Community Edition" from v11 to v12 and "Veeam Agent for Linux" from v5 to version v6.0.0.1060.Since then, I receive no more Backup Status mails from any Agent running v6.The only status mails I receive, ist for a Windows client with Agent version v5.0.3.4708.I have already checked the notification settings on the "VBR" several times. Various test mails are delivered successfully.Does anyone have similar problems after the upgrade, or a solution?I would be very grateful for any feedback

Hey all, I’m just dipping my toes into Veeam ONE and am getting inundated with alerts.  I’m sure there’s some fine tuning to play with, but every day when my backups run, I get alerts about suspicious backup sizes.  Does this analyze backups from days past, or is there a training period going forward?  I’m guessing the former, but I found it strange that for 3 or 4 days now all backups are suspicious.

What does " Warning: Task was not processed in the current session " mean? I receive the warning after it tries to run a backup copy job.  Any advice on what this means, why this happened, or how to solve the issue?I get the same message after running a new sync after about 10 minutes. Job will finish with warnings, with no successes. 

Trying to migrate Enterprise Manager to a new Server. I stopped the Veeam services on the old server and disconnected it from the network. I installed the EM on the new server and pointed it to an old DB that was used by the old server. There was a dialogue window confirming that the DB was owned by the old EM server and that it would be transferred to the new EM server.What happened next is that the the service account was getting locked out. So I had to roll back the changes. Good thing, I did not uninstall the EM from the old server per the instruction on https://www.veeam.com/kb1889 . Curious what happened here.

Hi,I have a successfull running backup job of 10 vm (which is the limit). I recently moved that vm to another server/datastore and the backup job claimed that this machine wasn’t found the following evening.To correct that problem, I edited the job, removing that vm and re-adding it to the job.Since that time the backup job report that I exceeded the maximum, which is not true!Is that someone can help me with that please? Denis GravelCEGEP de Thetford

Likely a noob question, but just want to be sure things aren’t broken.I’ve got a setup with Veeam B&R Community Edition on a single windows machine. I have full backups scheduled weekly, and daily backups every day, to a Quantum LTO-7 drive, using LTO-6 media.The console reports the total capacity of the tapes as 2.1TB. Allowing for the whole base 10 / base 2 argument, this is what I’d expect. The full backup (done last night) reports total transferred is around 1.1TB, but the tape is only reporting around 250GB free. I’m expecting around a TB free (2.1TB - 1.1TB). You can also see that the “daily” tapes are reporting 2.1TB free (again, this is expected - there’s not a lot written, maybe ~90MB per day, so not enough to make a difference to the free space reported)Is there something amiss somewhere, or am I going to have to migrate to LTO-7 media a lot sooner than I thought?  

Hello, I have a query.In a scenario with large mail files (OST and PST) that only change partially.Is there an option in Veeam Backup to only copy the part that has changed?How does deduplication.Does Veeam implement this functionality?Thank you for your attention.A greeting.

I am having a hard time trying to migrate our Veeam365 (azure marketplace image) VM in Azure to another subscription, due to Microsofts restriction regarding move VMs with a plan attached. My latest idea was to use Azure Recovery Service to replicate the vm, and then do a permanent failover. The ASR supports cross-over subscription so it would do the job.When doing the failover, I get an error saying that I need to accept the terms of the image vms.This should be done with the azure cli command: az vm image accept-terms --urn veeam:office365backup:veeamoffice365backup:3.0.0have also tried with the subscription id in the paramteres, but the results is the same:The VM image can not be found. I guess its because its an older vm-image which Veeam now doesnt offer on that azure marketplace. So where can I go from there..? I am starting to perhaps use Veeam for this just case but before spending more time it would be great to now if this Plan paramteres is somehow following the imagedisc in

Some time ago K10 went bananas and I had to disable it entirely. I have 20TB used on snapshots, it just keeps growing. I got to delete restore points, yet nothing happens. I’m now stuck with a small army of FCD’s I cannot delete manually or expand or do anything with. Where do I get rid of all these snapshots K10 created? I’ve deleted EVERY single restore point for each backed up application. This was backing up ~2TB, now I’m filling up my SAN at a rate of 5TB/day if I don’t disable the policy. I cannot find anything using all the documented commands via kubectl. Latest version K10, vsphere 7x etc. Do you have some tool that use the VDDK api to delete orphaned or all snapshots? I’m getting close to kicking K10 out.  

Bonjour tout le monde,Je vous remercie par avance pour toute l'aide que vous m'apportez régulièrement.Comme toujours, j'ai besoin de votre aide pour migrer vers la version 12 de Veeam. Actuellement, nous utilisons la version 11, mais le support a expiré il y a deux ans. J'aimerais savoir s'il est nécessaire de renouveler le support et comment procéder pour effectuer la migration vers la version 12.Merci d'avance pour votre aide.Cordialement.  

Hello,As I’m doing Backup Copy Jobs to second location I think it would be good to have Veeam B&R on that site also if somethings happens with primary location.For me I would need advice on licensing the second Veeam B&R.My primary Veeam B&R is on the primary site so If everything goes down there is no way to restore VM’s without it.

I have installed Veeeam Backup V12 Community edition on a local Windows 10 PC.  I have a 4TB external USB drive connected to this machine that I intend to use as a backup repository.The local machine uses a VPN connection to connect with a shared windows server 2019 drive located on a remote server. The connection is always on.In my reading across various forums, Veeam seems to the the product of choice to accomplish this. The tutorials I have read thus far appear to target a much higher level of backup sophistication (VMs, Hyper* and whatnot). Can anyone please advise or point me in the right direction to accomplish this somewhat trivial task?Thanks

One of the great features we’ve gotten with V12 is object-lock with Azure S3.@Rick Vanover did a great walkthrough for MS Ignite last year with a V12 beta already.With new storage accounts and containers it works as he explained, which I could prove in a few environments already. My (and some of my customer’s) question now is: can we enable it safely and supportedly on an existing blob bucket with let’s say hundreds of TB of data already inside? First, you would have to enable “version level immutabilty” within the container: Quite easy while creating a new container like Rick has shown, but if you would want to do this afterwards, you first had to enable a policy on the container: Having this policy also makes the container differ from a freshly set-up immutable container. The latter would not have this policy.To add this policy one would also have to enable versioning for the storage account beforehand: I tried that in a testing environment and ended up being able to activate immutab

RKE2 v1.26.2  is now bundled with a snapshot validation webhook (https://github.com/rancher/rke2/pull/3944) which prevent K10 backups :  message: 'Failed to create snapshot resource k10-csi-snap-b926xgtp79mbbq6w, Namespace xxxxxx: admission webhook "rke2-snapshot-validation-webhook.csi.kubernetes.io" denied the request: expect resource to be {snapshot.storage.k8s.io v1 volumesnapshots}, {snapshot.storage.k8s.io v1 volumesnapshotcontents} or {snapshot.storage.k8s.io v1 volumesnapshotclasses}' 

Buenas!!!!Quiero configurar un backup de una VM con ciertas consideraciones y me gustaría que me dijéseis cómo lo configuraríais vosotros para ver si estoy en lo cierto o se me escapa algo.Backup de VM, siempre full, nunca incrementales. Mantenemos 15 días el backup, al día 16 se borra el fichero de backup. Si antes de esos 15 días lanzo un backup a mano, borrará el backup anterior, el nuevo será full y se mantendrá otros 15 días. (Lanzo con Start, no con Active full. Es correcto?)Aparentemente es sencillo, pero los parámetros de “reverse incremental” me confunden un poco… Además el parámetro de retención no sé si debo ponerlo a 1 punto de retención o a 15días...Gracias

Hello, it’s about Veeam Backup for M365.would it be possible to start a backup job automatically when a previously specified backup is completed?For example:I’ve a Backup Job which safe just Microsoft Teams on a Server A.So when this Backup Job is finished, then start automatically the second Backup Job with Microsoft Teams on a Server B.

Hello to all,I configured Backup Copy Jobs to the second location via VPN.Two WAN Accelerators on source side and one on destination.VM’s with low disks are going perfectly but the problem is the big ones.Our FileServer is arround 7TB. Is it normal to take this long, its the first Backup Copy job without initial seed. 

Is there any way to successfully produce a backup copy job of a set of file shares to a rotate set of USB drives that will be swapped out weekly? If not through the mechanic of the backup copy function maybe another way? Thanks,T   

Hi, I tried my luck with the subreddit but I recon this is a better place for support. I was recently pointed to Veeam products for backing up my local machine onto my NAS server.The machine runs Windows 10 with no VMs, ryzen 5900x, a 2.5gb nic, and it includes 1tb ssd and 1tb nvme (OS) for backup. The pc is connected via direct ethernet to the nas (10.0.10.1)I've gone through the job configuration OK; the backup job was created successfully.  However, when the job runs and begins to backup, it fails with an undisclosed error "28/02/2023 20:05:14 :: Error: Error in the application "   Upon investigation of the logs, 10mins into the backup: [01.03.2023 02:10:15] < 45676> cli| ERR |Failed to dispatch pending requests[01.03.2023 02:10:15] < 45676> cli| >> |Data error (cyclic redundancy check).[01.03.2023 02:10:15] < 45676> cli| >> |Asynchronous read operation failed[01.03.2023 02:10:15] < 45676> cli| >> |--tr:Error code: 0x00000017[01.03.2023 02:1

Hi,I have been trying to understand how the “Restore to MS Azure Iaas” works. I need to know hos this works so i can bring up this feature with our customers.I have an Azure Storageaccount as a SOBR + my local NAS.I hade some failures to achieve a Azure to Azure restore before i found out that restores to Azure wont work when my Performance Tier is online. The process didnt restore FROM Azure as i wanted to test out.When i put the Perfomance Tier in maintenence mode i got it to work! (Thanks Veeam Foums for this!)What i furthermoore found out is that the restore speed from the storage account is far away from the miximum perfomance of 60Gbps / 7500 MB/s.Restore Speed:My restore speed was 169 MB/s,. This can ofcourse be a “OK” speed but i cant find out what the maximum speed can be or what the bottleneck could be for restoring. Conversion Speed:After the data is restored from the Azure storageaccount the data is then converted into a VM.  My concern is really about 2 things - “Documenta

Hi, we just upgraded to the latest VB365 v7 and configure new backup job for whole organization sharepoint sites ( around 550 users) at first full we had a lot error 429, but now its still same with incremental jobs.any experience with these error ? :) tomas 

If we have established backups for a server, and we add an additional disk to said server, will and should Veeam automatically recognize and start backing up the newly added disk?