Solved

You can review my journey upgrading form 7.06 to 7.0.14 in this post.I have a 200Gi PVC that is 155GB written of tiny little index files. It does take quite a bit of time to clone the snapshot, and Kasten would time out after 15min of waiting. I fixed it by increasing kanister.backupTimeout  (KanisterBackupTimeout) parameter from 45min to 150min, and the kanister.podReadyWaitTimeout  (KanisterPodReadyWaitTimeout) from 15min to 45min.During my upgrade journey to 7.0.14, I saw that these parameters were depreciated and replaced by timeout.blueprintBackup and timeout.workerPodReady respectively. So naturally I added them to my helm update command and they were added to my k10-config ConfigMap.  My ConfigMap now has both old and new parameters for the Worker Pod Timeout (copy-data-xxxxx pod) set to 45min but I am now getting timeout errors that my “Pod did not transition into running state. Timeout:15m0s”I have tried without the old values in the ConfigMap as well and no change. I have als

ciao, a qualcuno è mai capitato di vedere questo errore nei report di un job che salva su un hardened repo linux? Errore capitato sporadicamente.Da interfaccia sulla Veeam Console l’immutabilità non appare impostata sul restore point corrispondente, anche se andando dentro il sistema operativo linux pare proprio che ci sia.Ho aperto un caso al supporto ma il cliente non è rapidissimo a fornire i log richiesti e al momento non ho accesso diretto al sistema quindi chiedo intanto qui se è cosa che avete mai visto 😉

Hi, does Veeam Backup for Microsoft 365 require a Veeam Cloud Connect licence per customer when backing up from Azure to a remote (non-Microsoft) data centre?  Thanks, Nick

Para os amantes de Solaris...Estamos com algumas falhas com os logs abaixo dos Veeam Agens For Solaris:[28.12.2024 19:02:53.653] <      22> fb     | ERR |Failure during entry [XX.amap] processing[28.12.2024 19:02:53.653] <      22> fb     | >>  |Invalid bitmap access. Sub-bitmap number: [26044]. Count of bitmaps: [26044].[28.12.2024 19:02:53.653] <      22> fb     | >>  |--tr:Failed to allocate [3] data blocks.[28.12.2024 19:02:53.653] <      22> fb     | >>  |--tr:Failed to change file coverage. Size: [8627].[28.12.2024 19:02:53.653] <      22> fb     | >>  |--tr:Failed to set file size. New size: [8627].[28.12.2024 19:02:53.653] <      22> fb     | >>  |An exception was thrown from thread [22]. Não encontrei muitos posts sobre, apenas o item abaixo:https://forums.veeam.com/veeam-agents-for-linux-mac-aix-solaris-f41/va-for-aix-v2-error-when-backing-up-larger-files-t69822.html Outras extensões estão ocorrendo a mesma fal

Running Veeam Backup for M365 v 7.1.0.1501 on a Windows Server 2002 Standard VM (the VM is AD joined) and trying to create a backup repository on an SMB shared folder on an AD joined NAS on my LAN, and I'm unable to add the repository. In Veeam, if I go: "Repositories > Add > Backup to Local Disk > Path" ...then enter the path to the SMB shared folder on the NAS ("\\NAS-NAME\SHARE-NAME\FOLDER-NAME"), I can click "Get free space" and Veeam calculates the correct amount of free disk space (so it seems to be able to see the NAS), but if I click "Next" to add the repository, I see: "Specified folder does not exist on the backup proxy. Do you want to create it?? If I click "Yes" I get the error: "Access to the path "\\NAS-NAME\SHARE-NAME\FOLDER-NAME" is denied." I'm able to browse the share in Windows explorer and browse to the folder I'm trying to add. Veeam is installed on an AD joined VM, and I'm using Windows (AD) credentials to log into Veeam console when it starts up. I've ch

Hello,If we not setup team chat this mean VDC only backup teams channel and teams group? Also when click ‘set up teams chats’ there are information ‘may incur additional cost’.Cost of what? Any calculation to estimate the extra cost?

We are doing backup evacuation to that we can recover some of the storage. However, after the evacuation, some of the backup files show the following:If I copy the path, it points me to an available extent where the file has been copied. I also did a restore with the some of the files shown above and able to do a restore. So why does it still show that the files are in an extent in maintenance mode which is not correct since the files have been moved already. Bug or defect or has a information purpose?

SQL Transaction log backup seems to be failing with "Failed to perform internal backup."We just did a big repair of one of our DBs. When I re-enable the backup job (with SQL transaction log backup), it started failing with the following error. Failed to perform internal backup (DBName): Code = 0x80040e31 Code meaning = IDispatch error #3121 Source = Microsoft SQL Server Native Client 11.0 Description = Query timeout expired COM error: Code: 0x80040e31 We can see data being moved as shown in the Report so is the Transaction Log backup really failing or it is just doing catch up with the large change? I’m sure if we run a full backup or possibly change the log backup interval to longer, this will resolve the error. Thanks.

In data odierna grazie a due post sul forum ufficiale di veeam Anton Gostev ha indicato alcuni punti fondamentali per il passaggio alla nuova versione di Veeam v13 che verrà rilasciata nel secondo semestre del 2025.Si parla di funzionalità deprecate e di requisiti di sistema e compatibilità con componenti infrastrutturali e/o relative ai Sistemi operativi supportati nel prossimo futuro.Una novità importante è che il supporto alla V12 è stato prolungato di un anno per permettere a chi non potrà effettuare l’upgrade nel breve periodo di mettersi in linea e procedere successivamente.Di seguito i link ai due articoli:[V13] System Requirements for our 2025 release [V13] Deprecated and Discontinued features for our 2025 release Da leggere assolutamente per prepararci ai futuri aggiornamenti. Saluti a tutti

Hello.The question is related to adding S3-compatible object storage. Company-developed proprietary BLOB stores in ceph have their own implementation of the S3 surface. When adding S3, you can select a bucket, but when you select folders inside the bucket or when creating a new STORAGEClass error, the storage class uses erasure code.The question is what storageclass does veeam12 use?! since it worked on version veeam 10.How can I see through the logs which storageclass is trying to connect to the storage?  

I have more than 2000 Entra ID users but only have 900 M365 subscription licenses.When we setting the VDC to backup all tenant, will the VDC only take any user who have active license in M365?

I noticed a discrepancy between the Kasten Cluster ID and the actual cluster UID retrieved from the namespace.Kasten Cluster ID: f2c3c6f4-dc62-42d9-ac13-7933c4289xxx Cluster UID (via kubectl): 557f2513-0d07-4fbb-ad26-4325ffe12xxxIs this mismatch intentional?This discrepancy poses a challenge for automated disaster recovery, as I haven’t found a reliable way to extract the Kasten Cluster ID programmatically. //edit: Sorry, I did not see that there is a dedicated support group.

i am trying free tier of Veeam, Proxmox and AWSI have a Proxmox VE community edition installed on an old PC 5TB Hard drive, I would like to try to backup a ec2 instance from AWS Free tier and store all data to my Proxmox, Veam VM is installed in my proxmoxis this possible 100% no cost ?any document, links or suggestion for me to test this situation is appreciated.

Is it possible using Veeam to create a bootable clone of a system disk to a second local drive? I don’t want to have to use recovery media to restore the OS.I have a server with two physical spinning disks that are not RAIDed (can’t rebuild the server to do this) so I want to create a bootable clone. There are numerous free tools out there, but as we already use Veeam I thought I’d find out if it can do this first. Thanks

Anyone know why my VBR server log using . (dot) and use 24hours format in the time ?The server actually use 12 hours format with : for the time. 

ciao a tutte e tutti!per rompere il ghiaccio propongo un sondaggio:“cosa ci farà lavorare di più su Veeam nel 2025?”passaggio alla versione 13 (ovviamente se arriva 😉) backup EntraID ​​backup dei nuovi hypervisor (es ProxMox) progetti di DR varie ed eventualiaggiungete le vostre idee…credo che al ritorno del freddo la prima opzione sarà abbastanza importante

We use an immutable repository based on physical RHEL 9.4 servers.RHEL 9.5 has been released and I would like to upgrade the Repository servers OS.Can anyone let me know when this is going to be supported by Veeam ? I did have a dig but came up short.ThanksPhi

I deployed kasten k10 in my test kubernetes environment with --set externalGateway.create=true via helm.and I config metallb, now I can access Kastern Dashboard with IP/http protocoldashboard is now available but I need enable https and embed certificate for Veeam kasten Integration to Veeam Backup&Replication. but i can’t find any instruction. Does Anyone know this?

Dear HOL Team,​@Chan Ekanayake ​@Ian_RSA ​@aberndt ​@ChrisWong ​@kenlu  when trying to access the Veeam Backup & Replication - Advanced HoL, I’m receiving the message below. could you please fix this HoL?  

Hello, I install VBR on the DR site and in the job i can see this message‘1/2/2025 2:47:59 AM :: No available proxies are running on ESXi management interface subnet. Using proxies from a different subnet, performance may be impacted  ‘Some one can help me to make more understanding about that message, how we can improve the performance?

Hello everyone,We have Veeam integrated with vCenter in our environment. There were no issues when adding the vCenter, but occasionally, the host discovery fails with the following error:"Disks and volumes discovery failed. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond."Environment details:Backup Server OS: Windows Server 2022 vCenter Port: 442 is open vCenter Version: 7.0.3Has anyone faced this issue? Any suggestions on how to resolve it would be greatly appreciated!Thanks in advance!

I am using Veeam B&R community edition for testing purposes on a Proxmox cluster. After accidentaly deleted a backup file, I have restored from Backblaze cloud personal and imported in VBR, but restore fails with error Failed to reload metadata bank. Declared and actual CRC are different for all bank snapshots. Failed to open storage for read access. Storage: [Nextcloud Backup_2024-12-23T030148.vbk]. Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{e8606f0a-02b4-4e7b-bd8b-5b0fd8bd3615}]. CHMOD mask: [614]. Agent failed to process method {DataTransfer.RestoreText}. Agent failed to process method {DataTransfer.RestoreText}.I use Backblaze for offsite backup and if fails it should be a big problem. Thank you

Hi Team, Are we going to get the learning paths with badges here (like kubeacademy)

Just installed Veeam free edition on Dell Optiplex 5060 desktop running Linux Mint Mate 22.  Have several years’ experience with Veeam on older versions of this OS, and Veeam setup and a couple of test backups appeared familiar.  I did notice that the new backups ran for 10 minutes or so- less than half the run time in the old OS.  IIRC those Veeam instances were v.5.x and older, the new one is 6.3.0.73.  The volume of saved data is the same and Veeam has always been set to do a bare-metal backup. Has there been a change to Veeam that would explain this difference?

Veeam, yedekleme ve geri yükleme çözümleri konusunda sektördeki en köklü liderlerden biri olarak kabul ediliyor. Uzun yıllardır faaliyet gösteren ve hem küçük ölçekli hem de büyük ölçekli kuruluşlarda güvenle tercih edilen Veeam, kullanıcılarının güvenini kazanmış bir marka. Kendi üretim iş yüklerimde ve aynı zamanda ev laboratuvarımda da bu yazılımı kullanarak, ne kadar güvenilir ve etkili olduğunu bizzat deneyimledim. Veeam Backup & Replication 12.3, firmanın zaten sağlam temellere dayanan özelliklerini daha da geliştirerek, yedekleme yöneticilerine daha fazla işlevsellik ve en yeni teknolojilerle uyumluluk sunuyor. Bu yazıda, Veeam Backup & Replication 12.3'ün sunduğu yeni özelliklere ve sağladığı avantajlara yakından göz atacağız. Gelişmiş Sürekli Veri Koruması (CDP)Sürekli Veri Koruması (CDP), verilerin kritik öneme sahip olduğu ve kesintisiz çalışma ile sıfır veri kaybının beklendiği günümüz iş dünyasında giderek daha fazla şirket tarafından tercih edilen bir özellik hali