Veeam Backup for Salesforce 3.1
Recently active
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.
Dear Expert, Greetings! I have configured a lot of VAW server few of them server reset the portI checked this issue with the network security team and found that the traffic passed the firewalls, but there was a reset ports from the server side. Please put your feedback on this. Thank you.
Hello everyone,I have been looking for some options that are activated only when the "CTRL" key is used simultaneously. In a quick search on the user guide for VMware, I found 22 occurrences, but not all occurrences activate specific functions. Does anyone have a list of all the additional functions activated when using the "CTRL" key? The rebalance option is available only when the “CTRL” key is used with right click pressed at the same time.
Hi everyone, I’m trying to resize the Veeam console, but the smallest size that I have still big, I can’t get is smaller than the screenshot bellow.Does anyone knows how to reduce even more the console big?Thank YOU
Running Linux Mint Mate 20.3. Successful weekly backups for several years. Today forgot to connect b/u medium when starting veeam, got “warning” message in the “success” column. Tried exiting and restarting backup with medium connected, got another warning message. Not sure what to do next.
Hi Veeam Team, I just tried to overview veeam with proxmox. add inventory and add worker is working properly. but during creation job job in step schedule backup. I found error like below : Failed to register job. One or more validation errors occurredThe body field is required.Failed to parse 22.00. Please specify time parameters in the h:m format and try againFailed to parse 22.00. Please specify time parameters in the h:m format and try again if someone in this forum found same issue and has been solved it. kindly inform how to resolved it. thanks
When we enable ‘Guest file system indexing and malware detection’, this mean if the VM source infected by malware then VBR will send alert to us and keeping backup running?If i want to test this, can i testing by simply put eicar file into the source VM?
We have upgraded VBR and EM to version 12.2. According to our discussion with the OS team, due to a vulnerability, they need to remove the older version 3.1.32.31915. We can only see the highlighted .NET version required for version 12.2NET Framework and ASP.NET Core Shared Framework 8.0 We observed .NET Core runtime 3.1.32 and .NET Runtime 7.0.20 in VBR server We would like to know if we can remove .NET Core runtime 3.1.32 and .NET Runtime 7.0.20, as it is not mentioned in the articlePlease advise.
Hi Team:I am trying to set up Gitlab as OIDC provider but got failed: The authorization server encountered an unexpected condition which prevented it from fulfilling the request. **FYI**Kubernetes version: 1.30.6Helm chart version: 7.0.14GitLab Community Edition: 17.6 Here is the helm values.yaml:clusterName: kasteningress: create: true name: "kasten-ingress" host: "my-kasten.com" urlPath: "/k10/" defaultBackend: service: enabled: true name: "gateway" port: name: "http"auth: oidcAuth: enabled: true providerURL: "http://my-gitlab.com" scopes: "profile email" redirectURL: "http://my-kasten.com/" clientID: "xxxxxxxxx" clientSecret: "xxxxxxxxx" Here is k10-oidc-auth.yaml:apiVersion: v1data: client-id: xxxxxxxxx client-secret: xxxxxxxxx groupAllowList: "" groupClaim: "" groupPrefix: "" logout-url: "" prompt: select_account provider-url: http://my-gitlab.com redirect-url: http://my-kasten.com/ refreshTokenSupport: "false" scopes: pr
Hi!I am testing Kasten K10 and we want to be able to backup and restore Postgres databases. We currently use the StackGres Operator to deploy Postgres database clusters.What is the recommended way to backup and restore a StackGres Postgres Cluster using Kasten? If you don’t use StackGres, what is your approach and why?Thanks in advance!
Hallo zusammen,ich benutze den Veeam Agent for Windows Free Ich möchte gerne ein Datei aus einem alten Veeam Backup, welches auf einer USB-Festplatte liegt, wiederherstellen Leider meldet das File Level Restore Programm folgende Fehlermeldung “Veeam Agent for Windows is unable to open backup files create create by Veeam Backup & Replication.Das Backup wurde 2019 mit einer alten Veeam Agent for Windows Free Version erstellt. Gibt es eine Möglichkeit an die Sicherung heranzukommen?Herzlichen Dank Ihre Hilfe. Gruß Jesja4512
Can VBR backup VBR it self?My VBR server ip address is 10.18.120.200 then when i try to make Backup Job using Windows Computer then fill the VBR IP Address, i can see the job have failed with below picture.
hi all….I have question about VRO and VBR placementFor DR to cloud part, I refer to the architecture belowHowever, what if I need to cater both backup and DR to cloud simultaneously? Our customer is having on-prem VBR server, all jobs and policy are running on-prem.While they want to explore the possibility of DR to Azure, in case the production site is down, when on-prem VBR server is goneWhile the VBR server on Azure does not have any data, the failover seems can’t be success Any workaround for this scenario?
Ein Kunde möchte zusätzlich zur Sicherung in die Cloud auch eine Sicherung seiner VM-Umgebung auf ein Medium, das er zu Hause verwahren kann. Mein Gedanke war hier RDX. Ich hätte ihm 2 RDX-Platte zu je 4 TB angeboten.Meine Frage:Benutzt jemand RDX-Laufwerke zur Sicherung und wie sind die Erfahrungen / Performance usw.Ich kenne das Handbuch von Veeam (Backup Repositories with Rotated Drives - User Guide for VMware vSphere). Wenn ich es richtig verstehe, muss man also einen zusätzlichen Sicherungs-Job für die Sicherung auf das RDX anlegen - ich kann nicht die Kopie eines Sicherungs-Job dazu verwenden.Und .. wird das RDX-Laufwerk nach Beendigung des Sicherungs-Job ausgeworfen, damit der GF weiß dass er jetzt das RDX mitnehmen kann.Danke schon mal.
Hello, I currently have a problem with Veeam, I have two instances that are in error with the message : Error: Failed to call RPC function 'EpAgentCollectSystemInfo': [WMI] Empty result. I check my WMI deposit it is consistent.My firewall is open, the user has been created, and I added the LocalAccountTokenFilterPolicy registry key
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
Hi, I’m seeing the following error for just one of our offsite backups. The local backups are working as expected.Agent: Failed to process method {Transform.Patch}: Cannot create a file when that file already exists. Asynchronous request operation has failed. [requestsize = 4202496] [offset = 706145980416]Processing finished with errors at 18/11/2024 05:41:10This issue is only occurring on our SQL server. A 2019 Windows Server.Any troubleshooting pointers will be greatly appreciated. Thanks
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
Hello, for our applications we use PGO postgres cluster. In case that kubernetes cluster contain more than 1 postgres cluster is not possible create backup. PGO cluster are in difference namespaces. Backup process is failed with this error."pgoDBStatefulSet" not found When i keep same policy configuration and remove one postgres cluster backup will successfully done.Could you please check what is wrong.Thanks
hi all….I am puzzled if I create a SOBR:performance tier = backup appliance, immutable for 14 days capacity tier = Azure BlobCan data move to the capacity tier within 14days?Can I set policy to move them monthly so that the backed data is no longer immutable?Or I have to use SOBR copy function?If only SOBR copy, it does not release storage space from the backup appliance, what’s the different if I use BCJ to Azure Blob?
Hello,I try to restore one of my Application VM, then after restored i can see our application is having error.When the VM restored, is this VM identically same with the VM source?
Hello,I am experiencing an issue with my backup system. Backups run normally for about 3-4 days, but then an error occurs, and the backup stops. After restarting the system, everything works fine, but the issue repeats after a few days. All system and software updates have been completed, but the problem persists.The error message displayed is: Job has failed unexpectedly Error: Managed session be2c40b2-5ce6-40ee-bf83-f8c4dbd74b82 has failed. JobId: 7718e3f2-a680-40be-8f4f-68179fda8The NAS and the location are functioning properly, and there are no network disruptions. Backups were running smoothly at first, but after the mentioned period, the error starts appearing.I have attached screenshots of the error for your reference.I would greatly appreciate any advice or suggestions on how to resolve this issue.Thank you for your help.
