Actually I have tried to install v12 RTM as a in-place upgrade on 4 customer servers now and all fail.Veeam support has been on remote session and we will continue the work tomorrow since it also failed at last attempt after hours of troubleshooting. Would be interesting to hear if there is anyone else who has been issues with the upgrade? The servers I have tested has the latest v11 build and server 2016. Very simple deployments with few config settings so no big issue. But so far I am a bit concerned to start upgrading larger deployments.
Hi,after backuping ubuntu ever since without problems, the first fresh installed ubuntu 22.04 came up with this warning message in our latest veeam b&r 11: Failed to index guest file system. mlocate was not found. As since ubuntu 22.04 the package mlocate is just a transitional package to plocate, there is no mlocate binary.So I did a ln -s plocate mlocate and expected the message to be gone - but it keeps reporting, that mlocate was not found. updatedb and locate do not show any errors:root@ubuntu2204:/var/log# updatedb -Vupdatedb (plocate) 1.1.15Copyright (C) 2007 Red Hat, Inc. All rights reserved.This software is distributed under the GPL v.2....root@ubuntu2204:/var/log# locate -Vplocate 1.1.15Copyright 2020 Steinar H. Gunderson...So whats to do now?
Hello,Refer below setting:- backup job vm_to_disk with full and incremental keep 14 days- backup job file_share_to_disk keep 14 days, it should be full and incremental for file share backup- backup job vm_to_tape- backup job file_share_to_tape- two jobs vm_to_tape and file_share_to_tape backup to one tape setup with "Do not create, always continue using current media set", manual execute end of every monthrefer two jobs backup to one tape and it will require use "Do not create, always continue using current media set", t will append backup content to the content that was written to tape with a previous backup session. If, however, a backup set is started with a new tape, Veeam Backup & Replication will create a new media set for it.Does it mean jobs vm_to_tape and file_share_to_tape execute full backup when insert new tape? Best regards,
Hi All,with latest version of Veeam B&R, i have a Backup Jobs (that make copy on a remote Mac Folder via SSH that ends with this warning: 23/06/2022 04:33:51 :: Failed to transfer operation summary to backup server: Failed to delete file 'C:\ProgramData\Veeam\Backup\vMac_Files\__IP_USERNAME\Report\__IP_USERNAME_2022-6-23T4331.csv' If i go to that folder i’m able to delete the file.Any suggest?Thanks
Hey guys, I have faced this error in customer environment where backup SOBR offload to cloud failed because it shows the error “ TLS version is not permitted on this storage account”, the TLS version is 1.2. I referred some articles and they suggests to add a registry value. One article shows the following registry value details:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Dword: AzureConcurrentTaskLimitvalue: 1 will this registry value work?
Hello, ishttps://forums.veeam.com/veeam-backup-replication-f2/v8-new-forward-incremental-forever-backup-confusion-t24239.html#p125277still the thread to read when trying to decide which backup-mode we want to employ? 1 VM is a large file server with ~6-8TB where all other VMs are smaller application servers (~250GB). BRFrank
Hey All,I’ve tried to get some automation for the backup of my Citrix base images. I have a script that adds a machine to the backup job based on the name. Of course, these machines get created and deleted like flies, and I was wanting to automatically remove them if they’ve been removed from vCenter. I guess I could use tags, but then I’d have to rely on my Citrix admin to use the tags, and if it’s forgotten then there’s no backup, so I’ve decided a script is the way to go. So adding machines to the jobs works wonderfully, but I can’t seem to nail the way to remove the machines that aren’t in vCenter inventory. I also have the auto delete from backups turned on to prune the base images after x days. Here’s the snippet of powershell causing issues:#Searches the backup job to find any VM that don't have a size associated with the VM and assigns it to the variable ie. VM is still in the job but the VM is deleted.$NullVM = Get-VBRJobObject -job $Citrixbackupjob | Where-Object -Prope
Login to the community
Log in with your Veeam account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.