Solved

Cleaning tape CLNU00 is in unrecognized media and checking on the properties Wear is N/A. Is there anyway we can change to number of usage? 

So, my backups were not running and it was giving me DB is not synchronized error, I tried to resolve it but I couldn’t resolve it. So, then I made a new Backup Policy and added a new storage, but now a VM 2.8 TB (2TB used) has took more than 65 hours and it's still not completed. So, can anyone look into this matter urgently?

I encountered the above error when using a new Windows server. I'm certain that communication between servers is normal, and the ports are open. I've successfully added several servers of the same type without any error. And I've tried the following:Disabling the firewall and antivirus software. Adding a new account with administrator privileges. Using the IP address instead of the DNS name. Checking the registry or services to ensure they don't affect the relevant services. However, this issue still persists.My server is not within a domain, and this server is not a virtual machine

I am trying to create a Backup Copy job in VBR for my Veeam Backup for AWS jobs in S3 but the icon is greyed out. I have an enterprise plus license so should I not be able to do this?   

I removed the veeam B&R server and Enterprise manager from the domain due to security issues, and now I want to know if it is possible to log in to these servers, which are workgroups, with domain users ?Is there a best practice? 

Buenas tardes estimados, Mejores practicas Veeam y su integración aun Dominio Active Directory Una consulta, estamos evaluado la implementación de Veeam y se mencionó que no se recomienda su integración al dominio. ¿Esto es cierto?  Me gustaría tener claro este punto, ya que de mi parte he visto varios artículos que mencionar su operatividad.2.- ¿Es recomendable integrar Veeam al Dominio Active Directory? Y si es recomendable, donde puedo obtener esa confirmación oficial? Agradecido de antemano por la ayuda que me puedan brindar, Saludos cordiales,

We have two DCs running VMware clusters that have independent vcenters managing each of the clusters. A instance of Veeam B&R instance is proposed to be deployed in each DC to backup the local clusters. IN addition, there will be replication of some of the VMs across the DCs using Veeam B&R instance. Multiple packs of Veeam VUL licenses have been procured for all the VMs in both clusters. Need to understand on how we should be splitting the licenses across the two instances and the impact of VMs being replicated on the license consumption.

We have several Synology NAS devices that we would like to essentially backup to tape to take offsite via our monthly tapes. I stumbled upon an article about backing up files to tape and hitting the 10GB limit on the SQL Express DB. I’m not sure if this would be an issue for us or not. We’re on 12.1.2.172 Enterprise Plus Edition. Would this be an issue for us and we’d need to migrate our DB to our MSSQL Server (which we have and could possibly do). File to tape limitation - R&D Forums (veeam.com) Apart from that, I’m also interested in the best way to tackle this. Would it be best to backup directly to tape OR backup to a repository and then process said backup to tape? None of the current NAS devices are on our 10Gbps infrastructure. We think we have a way around that by using Synology Replication replicating the shares (as read-only) to one of our NAS which do have 10Gbps interfaces which would help when writing to tape.​​

We have 2000+ documents that need restoring from different paths on the same server.  Is there a way to put those paths into a spreadsheet or csv and run a script to restore them all?

What does the deleted_files_...log indicate in Malware detection log? Is veeam removing files from the production server or the backups?

Hello,We have an issue with restoring SharePoint lists to another pre-production location. A case has already been opened under reference: 07261975, but we haven't received any explanation so far.Do you have any idea about the error shown in the screenshot, please?  

Title says it all, attempting to backup AWS S3 bucket, have confirmed bucket does contain data, but when the backup job runs  Any ideas?

Does Kasten K10 support the NFS CSI driver?I tried the following but failed to create a snapshot.Install External Snapshotter Install NFS CSI Driver Create StorageClass Create VolumeSnapshotClass Perform Pre-flight Checks Install Kasten K10 Test K10Install External Snapshottergit clone https://github.com/kubernetes-csi/external-snapshotter.gitcd external-snapshotterkubectl kustomize client/config/crd | kubectl create -f -kubectl config set-context $(kubectl config current-context) --namespace kube-systemkubectl -n kube-system kustomize deploy/kubernetes/snapshot-controller | kubectl create -f -cd .. && rm -rf external-snapshotterInstall NFS CSI Driverhelm repo add nfs-csi https://raw.githubusercontent.com/kubernetes-csi/csi-driver-nfs/master/chartshelm repo updatehelm install nfs-csi nfs-csi/csi-driver-nfs -n kube-systemCreate StorageClassapiVersion: storage.k8s.io/v1kind: StorageClassmetadata: name: nfs annotations: storageclass.kubernetes.io/is-default-class: 'true'provi

Hi, Folks,i am getting this error on the export phase when running a policy, the location profile is a S3 bucket, anyone faced it before? - cause:    cause:      cause:        cause:          message: "Failed to exec command in pod: command terminated with exit code 1.             stdout:\             stderr: \e[31mERROR\e[0m unable to get repository            storage: error listing blobs: A header you provided implies            functionality that is not implemented."        file: kasten.io/k10/kio/kopia/repository.go:538        function: kasten.io/k10/kio/kopia.CreateKopiaRepository        linenumber: 538        message: Failed to create the backup repository      fields:        - name: appNamespace          value: kasten-backup-test      file: kasten.io/k10/kio/exec/phases/phase/export.go:270      function: kasten.io/k10/kio/exec/phases/phase.prepareKopiaRepoIfExportingData      linenumber: 270      message: Failed to create Kopia repository for data export    file: kasten.io/k10/k

Hello,I import agent backup into VBR, now how i can remove this from VBR?  

I've been using Veeam Agent for Windows for a bit, and have successfully used backups to restore individual files. I wanted to upgrade my NVME system drive to a larger one, so I figured I would try using the restore.I made sure my Windows 10 was up to date, updated Veeam to the latest version, created a new recovery ISO, and created a fresh backup. I then swapped in the new NVME and booted from a recovery USB. I stepped through the wizard, selected system volumes only (there is a data SSD I don’t need to restore); I did not use the Manual restore.After it copied everything to the new drive I rebooted, and then was stuck in a boot loop which ultimately ended in a recovery environment. Looking through the manual, there is a note about driver injection, so I tried again and disabled driver injection, still stuck in a loop. I put the original NVME back in and started looking for answers - any insight appreciated.

Hello,It’s true that VDC have unlimited storage, ant term and condition apply for this unlimited storage?Also the VDC is SaaS and this mean we no need to preparing the Azure VM for this, am i right?

Hello.This is my first post here.Please let me know if I'm doing anything wrong. I'm using Veeam Community version 12.1.1.56 and since I updated to this version, my "file share" backups have been experiencing issues.I have two backup jobs of this type.The problem I'm going to report only occurs when I activate the option "Configure secondary destinations for this job" within "Backup Repository" in the job properties.If I create a backup job now, it will execute the task normally. However, on the following days, Veeam starts to encounter problems. It always copies the files in the primary job normally, every day, but in the secondary jobs, it immediately starts the task along with the primary job and the logs show the following error:"[12.03.2024 19:01:20.918]    <28>   Error (3)    Item [Data from 03/12/24  7:00:28 PM restore point] is locked by running session SRV-02 - Arquivos [File Backup], SessionId: [aac32375-bfca-4f36-afe2-d7b1a6f5627a][12.03.2024 19:01:20.918]    <28&gt

  Hi Experts,Our environment is below.ESXi server - FC HBA External storage - FC HBA Proxy and Gateway servers  - FC HBA HPE StoreOnce Target side deduplication Catalyst over FC We found a Primary bottleneck point to Target every backup jobs.Backup details already show “san”. Thank you in advance. 

After upgrading to 12.1.2 this morning, all of our backup copy jobs went into a failed state with the error“5/22/2024 8:08:10 AM :: Error: One or more Veeam components on host This server are not up to date. You must upgrade them first. The job has been automatically disabled due to too many failures. Please fix all issues preventing the job from running before re-enabling it.”The “on host This server” is the exact wording in all cases.  They were indeed all disabled.  Re-enabling manually seems like it’s working, but none of the copy jobs actually have any work to do until later in the week, so I can’t say for sure. Anyone else seeing this?

Hello to everyone, from yesterday I am receiving this error. Veeam Backup & Replication 12 Community E. (today updated to v. 12.1.2.172) installed at Windows Server 2016VMware Tools at the Veeam Server is the newest / Kompatibility OKWindows Updates the latest. Firewall disabled. 3 Jobs (to the local / virtual HDD and to the NAS Server). Everything was just fine. Same error before the Veeam Update and after the update. Backup mode: Reverse incremental / VSphere VMware Tools quiescence is and was disabled Credentials Test completely OKAll Infrastructure re-scanned OK I have also tried to completely delete one job from disk and start a new one: still the same error. Veeam Server has been rebooted many times already, other Virtual Machines will be rebooted at the evening. This is what the log is showing up: [06.06.2024 15:51:52.204]    <28> [000Z]    Info (3)    Waiting for backup infrastructure resources availability[06.06.2024 15:52:37.698]    <22> [000Y]   Error (3)    

Hallo zusammen,Ich bin noch ziemlich neu in Veeam. Ich will eine Umgebung eines Kunden, die ich vor kurzem übernommen habe, von vmware auf hyper-v umziehen. Aktuell gibt es 2 veeam Backupserver, wovon einer den vmware Esxi Server backupt und der andere die hyper-v Umgebung. Ich würde gerne Veeam für diesen Umzug der VMs nutzen. Ich habe bereits versucht ein Backup einer Linux VM mit dem alten Backupserver, auf ein Storage, auf das beide Zugriff haben, zu machen und über die Restore Funktion des neues Servers auf Hyper-V wiederherzustellen aber er zeigt unter "Entire VM restore" leider dieses Backup nicht an. Die andere Möglichkeit wäre, den vmware Server auch auf dem neuen Backupserver, als managend Server" hinzuzufügen. Geht das, dass 2 Backupserver auf eine Umgebung (in diesem Fall den vmware Esxi Server) zugreifen können? Wäre es über den Weg möglich die vmware VM zu backupen und unter hyper-v wiederherzustellen?  

I am facing an issue while restoring an instance to Google Cloud Platform.error: HTTP exception: Error in SSL handshake: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed, error code: 110 (Veeam.Backup.Common.CCppComponentException)notes: All ports are open on the firewall, and the service account has full permission (owner).logs: HTTP exception: Error in SSL handshake: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed, error code: 110 (Veeam.Backup.Common.CCppComponentException)[12.06.2024 10:54:08.328]    <01>   Error (3)       in c++: [AmazonS3RestApiWriteStream] Failed to open Amazon S3 Rest API write stream. Bucket: [veeamrestorebucket-d0dab41870e6], Object: [disk-023b2689-7121-4143-82ea-4d985cfd5008.raw][12.06.2024 10:54:08.328]    <01>   Error (3)       in c++: [CAmazonS3Disk] Failed to write [1048576] bytes of data at offset [0] (current offset [0])[12.06.2024 10:54:08.328]    <01>   Error (3)    

I’m trying to figure out how to install Kasten on our vSphere 7 with Tanzu cluster so that I can backup our NSX Application Platform (NAPP) installation and restore it to a new storageclass since there is no other way to migrate a PV from one datastore to another.  We aren’t running NSX to manage the Tanzu cluster (running on our management cluster which is not licensed for NSX), but are using dvswitches.  I can’t seem to find any documentation or install guides to help me install on this specific type of environment.  My Tanzu/Kubernetes experience is not extensive, but I have lots of VMware and Linux experience.  If there are any guides or docs I can look at to help get started I’d appreciate it.  Thanks.

I have a backup environment that consists of: 1 physical Backup Server with a 10gbit connection to the switch that is also the primary backup repository1 VM for VMware backup proxy configured to use virtual appliance (8vCPUs & 16GB of RAM)3 node vSAN cluster all connected to the same switch via 10gbit ports When running backup jobs, Veeam starts running well, reaching read speeds close to 450MB/s for some jobs. After a while, the read speeds drops significantly for both incremental and full backups, going down to ~70MB/s in some cases.The backup proxy and the backup repository are configured to process 8 concurrent tasks. The bottleneck in all the backup jobs show 99% in source. How/where should I look for the reason of this bottleneck and what types of tests can I run to find which part is holding the backup speed down?