Solved

Hello,Today, the backup of our domain controller is no longer working and we can't access the host. Everything was working fine until now.17/11/2024 21:00:44 Failed Unable to install backup agent: failed to connect to "domainename" Error: Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. Failed to connect to share '\XX.XX.XX.XX\ADMIN$'.The package is accessible when I try to access it manually. I don't understand. The account entered is the domain admin account and even with another account, it doesn't work.I've scoured the forums and I can't find anything.Could someone help me? Regards 

 I am testing Kasten on an RKE2 cluster and have encountered an issue during the disaster recovery (DR) restore process. Below is a detailed overview of my setup and the specific error I am facing: Cluster and Namespace Setup: I have installed Kasten in the kasten namespace (not in the default kasten-io namespace). Restore Process: During the restore, I am running the following command: helm install k10-restore kasten/k10restore --namespace=kasten --set sourceClusterID=<cluster id>  --set profile.name=k10-test Error Encountered: I receive the following error message during the restore process: cannot get resource "configmaps" in API group "" in the namespace "kasten-io" Additional Context and Question: It seems the restore process is attempting to access resources in the kasten-io namespace rather than the kasten namespace where Kasten is installed. Is it not possible to restore Kasten with Kasten DR if the namespace is not kasten-io? If there is a confi

Good day team,Is there a plugin solution for Postgresql running on ubuntu/linux desktoip edition(application level). Have some databases that i want to selectively backup and restore. I do not want to backup at the image/file level which is simple.I need something similar to the veeamsql plugin where i can configure the plugin, open the “backup database” app on a gui/desktop and view databases, run the backup on selected databases and the corresponding jobs pop up in veeam BR gui. Need to be able to Restore as well. Thanks guys

A few issues that needs to be addressed urgently though1. I see the successful application plugin job listed under jobs in vbr12 gui but the EDIT, START, RETRY, CLONE and STOP are greyed out. Can this be fixed 2. On the Sql test server, where do view these veeamsql plugin jobs, their schedules in SMSS or the plugin app. Whenever i close the backup database icon and reopen it, i see no job/schedule, just a new blank window. How can this be addressed? 3.Do i have to keep the "Backup Dtabase" icon/app up all the time, i see no schedule

Is the updated installable ISO available yet for the VHR?

Hello,we want to use VEEAM for a backup on a WORM Drive. It is some kind of NAS with a WORM partition. The Problem is, that the after the first backup the backup job ends with an error. This is because the meta file (.vbm) needs to be altered for every backup. But since it is a WORM system, this is not possible.I searched and found out, that there is a possibilty for a tape WORM server in VEEAM. But firstly, the NAS is not a tape server und secondly this option is greyed out, maybe it is some sort of license problem.Has anyone an idea of how to resolve this issue?

Detail:A month ago I posted a question with specific version 7.0.10 in the topic.  I had issues and needed to revert, so I went back to my working 7.0.6 version.  Today I went to try again. Kasten Upgrade page says to apply 7.0.10 before 7.0.14.  Of course, 7.0.10 was pulled and doesnt exist.  7.0.11 says it was to specifically address the issues in 7.0.10, so I read this as a re-release.Since 7.0.6 doesnt know about 7.0.10 or 7.0.14, it must come from an external system. This should be corrected to reflect that 7.0.10 no longer exists.So I apply 7.0.11. Totally fine. Then move on to 7.0.14.Issue:the “state-svc” pod is failing to start with a CreateContainerConfigError state. Specifically, the admin-svc container. The event-svc and state-svc containers are starting.The admin-svc container is demanding a specific set of env variables, including:    CONCURRENT_SNAP_CONVERSIONS         <set to the key 'concurrentSnapConversions' of config map 'k10-config'>    CONCURRENT_WORKLOAD_SNA

We’re trying to add a Proxmox server to Veeam, and are getting the “Failed to reach hypervisor” error message. We’re using root, tried disabling 2FA, and confirmed all the ports are open.The log files show essentially the same error message than we get on the UI:[12.11.2024 10:32:30.006]   <233>    Info (2)    [PVE plugin] External infrastructure api [post] request #1 https://localhost:8545/api/v1/proxmox/validateSshConnection {"certificateThumbprint":null,"credentialsTag":"e502fcbb-ce66-4d55-88c5-88ce4cadf5a1","ipOrDnsName":"X.X.X.X","port":8006,"sshPort":22,"sshKeyFingerprint":null}[12.11.2024 10:32:30.612]    <01>    Info (3)    Creating splash form[12.11.2024 10:32:30.622]    <01>    Info (3)    Showing splash form[12.11.2024 10:35:02.072]   <233>    Info (2)    [PVE plugin] External infrastructure api [post] response #1 {"errorMessage":"Failed to reach the hypervisor","errorType":"Other"}[12.11.2024 10:35:02.087]    <01>    Info (3)    Disposing splas

Good day,What caused this error?This is a hyper-V backup job for a linux vm, worked excellent for days, for 3 months now, what happened all of a sudden?I retried, same error after 20% then fail. I restarted the veeam server, now attempting backup again. It has been stuck on 20% for like 15 minutes now.Where did this come from all of a sudden and how do i fix?

With the recent VMWare licensing consolidation and Broadcom moving to a subscription/core model, it has caused many SMBs to explore new options for a hypervisor. (such a shame.. pouring one out for my years of VMWare experience.) XCP-NG and ProxMox keep coming up in various communities. I personally have tested both and they perform really well. My only issue with them is that currently there is no native Veeam integration for the two platforms. Are there any plans for Veeam to support XCP-NG and/or ProxMox?

Failed to backup database SchoolDB. Error:  Error code: 0x80070005 Access denied. You must be logged in as a Windows administrator to create a virtual device. Failed to start VDI backup.  All conditions are met, veeam backup service account is apart of local admin group on sql server, requisite sssms server roles assigned to same service account etc What is causing this?

Good day, anyone knows how to fix this and why this happens. Backup Jobs for MONTHS now going on perfectly for this server in veeam 12.1. Now i wake up, logon to vbr to see this crap. What the hell is this?

Hi everyone,In this scenario, I have two EC2 instances on Amazon Web Services and a Microsoft 365 tenant. I need to back up both using Veeam.How can I do this with low resource usage?I believe the EC2 costs for Veeam for Microsoft 365 are high (8 vCPUs and 16 GB RAM with Windows Server). So, if I use Veeam for Microsoft 365 on-premises (as the backup server) and use a data mover (backup proxy) on AWS, will I save costs?Thanks for your help!

I have tried requesting an NFR key for a few days now and it never shows up in my email. It has worked every other time I have requested one in the past. I tried opening a case but they said I had to contact sales. So I contacted sales but haven't heard from anyone. Can anyone help or point me in the right direction? Thanks

Hello,If we have NFR license, can we open case to veeam technical support if we found technical issue?

Hello,Can we test Veeam WAN Accelerator using NRF License? I already configure the WAN Accelerator but when edit the job, i can’t find ‘Data Transfer’ menu to select the WAN Accelerator.

Hello,I’m learning for the VMCE Exam. There’s a question with this correct answer: Question: An infrastructure with 50 VMs has a power outage. After the VMware cluster hast booted up again, three large VMs seem to be stuck in a boot loop.Assuming only the OS is installed on the VM OS disk, which method would require the least amount of backup data transferred to allow the VMs to boot? Correct answer: Perform a Virtual Disk Restore with the quick rollback feature disabled. Why it’s not with the quick rollback feature enabled? 

 Dear Community did anyone face this issue while installing the new Veeam One? Need your best guideline in the logs file i can see that  

Hello to community. I have question regarding Veeam SQL plugin. Is it possible and supported to use Veeam proxy when configuring SQL plugin. Thanks to everyone. 

Guten Morgen, wir haben einen neuen Kunden, welcher von uns IT-technisch versorgt wird.Dieser Kunde hat Veeam im Einsatz, aktuell mit Socket-Lizenzen. Er möchte auf B&R Instanzen umstellen. Nun ist es so, wenn wir Lizenzen bei unserem Lieferanten anfragen, heißt es von dessen Seite, dass Veeam eine Art Erstlieferanten Schutz hat, somit bekommt mein Lieferant hier so gut wie keine Marge und dementsprechend möchte er die Lizenzen ungern besorgen. Der Endkunde möchte aber zu 100% zu uns wechseln.Was kann man in diesem Fall machen, dass mein Lieferant der zukünftige Lieferant des Kunden ist?  Viele Grüße

I hav a question about retention of a job that sends backups to a immutabble repo (like object lock repo or linux hardened). We need to use forward incremental in this case, but do i need  to make more than one full backup file during the locked period?  Example: a backup job forward incremental with 14 days retention and one syntetical full weekly, sending to a object lock s3 repo with 7 days lock retention.  In this case, do can i use 7 days and one backup full in the first backup job task? 

Unable to see DB backups from Enterprise Manager or VBR when using Veeam's SQL plugin for SSMS.Not sure if this is by design to allow DBA full control of their backup and restore processes or I’m just missing something here. Thanks again for all your inputs.

Hello,Every metadata export is failing with this reason, and it seems like my local snapshots are not delete as they should be (I have a zero local snap retention policy). Nothing changed configuration wise beside upgrading K10 to it’s latest version with helm. kind: ExportActionapiVersion: actions.kio.kasten.io/v1alpha1metadata: name: policy-run-xsnzcbw8kt namespace: kasten-io uid: d72b5bba-a5ac-11ef-94a5-f658bf251e62 resourceVersion: "672310" creationTimestamp: 2024-11-18T12:58:43Z labels: k10.kasten.io/isMetadataExport: "true" k10.kasten.io/isRunNow: "true" k10.kasten.io/policyName: nxt k10.kasten.io/policyNamespace: kasten-io k10.kasten.io/runActionName: policy-run-xsnzc k10.kasten.io/runActionNamespace: kasten-iostatus: state: Failed startTime: 2024-11-18T12:58:43Z endTime: 2024-11-18T13:04:33Z restorePoint: name: "" result: name: "" error: cause: '{"cause":{"fields":[{"name":"freq","value":"@daily"},{"name":"retention","value":{}}],"file":"k

Buonasera,devo configurare un backup con Veeam Cloud Connect ed avrei un paio di dubbi…La dimensione totale delle macchine virtuali di cui fare il backup è di circa 7TB, considerata la velocità massima in upload della connessione internet del cliente (100Mbps) il backup completo iniziale dovrebbe durare circa una settimana. Volevo sapere se è possibile limitare la banda di trasmissione di veeam in orari di ufficio (in modo da non influire sul lavoro dell’azienda) e lasciarla illimitata la notte.Inoltre volevo sapere se veeam salta in automatico i backup successivi fino a che non sarà stato completato il primo backup completo.Grazie

Hello, I’m testing Veeam Kasten for the first time, but unfortunately it won't work as expected. I’ve created a backup policy with a snapshot and an export to a s3 rados-gw (ceph) endpoint.I’ve got the following error message while exporting the snapshot:- cause: cause: cause: cause: cause: cause: cause: cause: cause: cause: cause: message: "client rate limiter Wait returned an error: context deadline exceeded" file: github.com/kanisterio/kanister@v0.0.0-20240812194716-8812756d1751/pkg/kube/pod.go function: github.com/kanisterio/kanister/pkg/kube.WaitForPodReady linenumber: 384 message: Pod did not transition into running state. Timeout:15m0s Namespace:kasten-io, Name:copy-vol-data-rpr56 file: gith