Solved

Ciao a tutti, qualcuno di voi ha esperienze con il DR di tenant vCloud utilizzando NSX-T? Quali sono le configurazioni necessarie? Capisco che ogni scenario è diverso da un altro, ma mi piacerebbe sapere se ci sono delle linee guida “generali” / requirements da seguire. Grazie Marco S.

Hello,I tried to find out how to cleanup backups taken before and I am wondering where to find this feature. Do I risk any problems if I delete the backups in my s3-location? Thanks a lot. 

Hi, I have a new issue after an upgrade / reinstall : cause:  cause:    cause:      cause:        Code: 1        Err: {}      file: kasten.io/k10/kio/kopia/repository.go:528      function: kasten.io/k10/kio/kopia.ConnectToKopiaRepository      linenumber: 528      message: "Failed to connect to the backup repository: invalid repository password"    fields:      - name: appNamespace        value: pux-gitlab-runner-live    file: kasten.io/k10/kio/exec/phases/phase/export.go:205    function: kasten.io/k10/kio/exec/phases/phase.prepareKopiaRepoIfExportingData    linenumber: 205    message: Failed to create Kopia repository for data export  file: kasten.io/k10/kio/exec/phases/phase/export.go:127  function: kasten.io/k10/kio/exec/phases/phase.(*exportRestorePointPhase).Run  linenumber: 127  message: Failed to copy artifactsmessage: Job failed to be executedfields: [] Can you help me ? Have a nice day ! Thanks !

We are testing out Kasten to do a Export/Import to migrate an application from one AKS cluster to another.  The export is working fine and we are able to export to Azure blobstorage. Verified that the files and directories were also created successfully. However, when we do an import we are running into the following problem:cause:  cause:    cause:      cause:        - cause:            Code: 1            Err: {}          file: kasten.io/k10/kio/kopia/repository.go:441          function: kasten.io/k10/kio/kopia.CreateKopiaRepository          linenumber: 441          message: Failed to create the backup repository        - cause:            Code: 1            Err: {}          file: kasten.io/k10/kio/kopia/repository.go:528          function: kasten.io/k10/kio/kopia.ConnectToKopiaRepository          linenumber: 528          message: "Failed to connect to the backup repository: repository not found"      file: kasten.io/k10/kio/kopiaapiserver/api_server.go:200      function: kasten.io/k1

Hello,I am trying to snapshot and export an K8s application through the execution of a Kasten Policy.My environment is installed in air gapped mode and when I ran the policy on K8s the “k10-namespace-generic-volume-2.0.13” blueprint is automatically created. I am guessing if there is a way to overwrite the tag image in the blueprint YAML so the image would be pulled from my private repository and not from public one.I wanna change that image: ghcr.io/kanisterio/kanister-tools:0.72.0toimage: myprivaterepo.io/kanisterio/kanister-tools:0.72.0Many thanks! 

Hi everybody,we are evaluating the ElasticSearch blueprint and are getting the following error message:cause: cause: cause: cause: cause: message: context deadline exceeded file: kasten.io/k10/kio/poll/poll.go:95 function: kasten.io/k10/kio/poll.waitWithBackoffWithRetriesHelper linenumber: 95 message: Context done while polling fields: - name: duration value: 44m59.987738528s file: kasten.io/k10/kio/poll/poll.go:65 function: kasten.io/k10/kio/poll.waitWithBackoffWithRetries linenumber: 65 message: Timeout while polling fields: - name: actionSet value: k10-backup-elasticsearch-blueprint-elasticsearch-master-elgjmdn file: kasten.io/k10/kio/kanister/operation.go:278 function: kasten.io/k10/kio/kanister.(*Operation).waitForActionSetCompletion linenumber: 278 message: Error waiting for ActionSet file: kasten.io/k10/kio/exec/phases/backup/snapshot_data_phase.go:630 funct

Dears, I have Veeam backup & replication connected to Veeam service provider console, and I would like to customize a user on VSPC to be allowed to run and stop specific jobs on VBR and not all the jobs created.Because my client wants to run some jobs manually and not periodically and I do not want him to have access to all the jobs created on VBR. Regards.

Hello!We are trying to set up the MongoDb blueprint in our test environment. The MongoDb replicaset there has no authentication activated.Please advice how to customize the secret sections in https://raw.githubusercontent.com/kanisterio/kanister/0.73.0/examples/stable/mongodb/blueprint-v2/mongo-blueprint.yaml at the following places:actions.backup.phases[0].objects.mongosecret.name: <mongo-secret-name> actions.restore.phases[0].objects.mongosecret.name: <mongo-secret-name>

Can someone enlighten me on my queries? If I have to replicate the backup from Prod to DR, what will be the best approach?I believed you can install veeam in the VMware Prod only then Replicate the VM directly to the DR VMware environment, it means no Veeam Mgmt in the DR installed, but on the failback what will the approach for that? I handled other backup before, on Arcserve I must have arcserve on both sites to do the replication, is that approach is feasible to veeam? must have both veeam mgmt for prod and dr If customer have exisiting vsphere replication for critical apps. Do I need to maximize the CDP feature instead of veeam replication?Thanks :)

Regarding the guidelines in the K10 documentation K10 Resource Requirements does the “Dynamic” specification of 1 core + 1GB RAM mean that this is required per concurrent policy/job run or that 1 core + 1GB RAM is generally suitable for 100 applications as the guide seems to indicate.If the latter further assuming that some sort of internal throttling occurs if all 100 policies are set to run at the same point in time?Trying to accurately gauge K10 backup processing insertion impact on cluster compute...

Dear, I am trying to integrate Kasten K10 with Keycloak via OIDC. I have followed the other post:  Our Kubernetes cluster does use a Self signed CA Certificate for HTTPS, and is used by Nginx Ingress Controller via Cert Manager.However when I navigate to http://xxxx/k10/#  the pod: auth-svc logs the following error:{"message":"Failed to init OIDC provider","function":"kasten.io/k10/kio/auth.initOIDC","linenumber":137,"file":"kasten.io/k10/kio/auth/oidc.go:137","cause":{"message":"Failed to setup OIDC Provider","function":"kasten.io/k10/kio/auth.provider","linenumber":126,"file":"kasten.io/k10/kio/auth/oidc.go:126","cause":{"Op":"Get","URL":"https://xxxx.com/auth/realms/yyyy/.well-known/openid-configuration","Err":{"Cert":Here then it logs basically our CA Certficiate content, and the log ends as:"hostname":"auth-svc-5fc8dcfb76-vjfnf","level":"error","msg":"Failed to create OIDC provider","path":"/v0/authz/k10/","time":"20220212-08:35:35.043Z","version":"4.5.8"}We are running Kasten K10

I set up a linux hardened repository for immutable backups. In the Backup Repository I have set the minimu 7 days as immutable.The Backup Job finished sucessfully on this linux repository. But i can still delete the backup. I have also checked in Linux directory, there should all backup files have an extension “i” to say that this file is immutable. But there is also no “i” in the directory. What am I doing wrong? Can someone help me?

My default storage class has was setup with reclaimPolicy: Retain. Everytime Kasten exports backups, it will create copy-vol* pods which request kanister-pvc’s with the same storage class as what they are copying. This means that everytime a 20G volume is backed up, a new 20G PV is requested and used up. This quickly leads to running out of storage.I’ve already set up kasten 4.5.9 with a storage class that has “reclaimPolicy: Delete”, but since it the copy-vol containers seem to mirror the SC of existing PVs that doesn’t help. Is there anyway to prevent the PV buildup as a result of backups? For now I’m manually patching all released PVs with “reclaimPolicy: Delete”.

Now this is just for my own curiosity. When Backup Jobs complete, Veeam runs Health Checks on the backup files to check for any corruption on the vbks. What happens if the VBR server goes offline whilst a Health Check job was in progress? Does it carry on from where it left off, or does it start the whole process again?Additionally, would it affect the vbk files in any way? 

We use Veeam Backup and Replication as well as Veeam for Office 365.Whilst we have restricted access to our Veeam for O365 server to specific backup admins, our information security team have asked if it’s possible for the auditing logs to be fed to a log server outside of our team’s reach so that we can confidently say all of these actions are logged and an admin is unlikely to have tampered with the logs.Basically, this isn’t about monitoring the backup jobs themselves, but we’re interested in recording that Admin1 opened Veeam Explorer for Microsoft Exchange, browsed to User23’s mailbox and opened X email in their Inbox. This can be reviewed by generating the logs, but we’re interested to find out if anyone has done this/it is possible to do this on a continual basis.

Hi!  I’ve been kicking the tires of Kasten k10 in my home k8s environment and had it mostly working until I upgraded to 4.5.1 recently.  I’m not exactly sure it was the upgrade that broke things, or me doing something else around the same time (upgrade from 1.21.3 to 1.22.3?). All policy runs fail now. Using the dashboard, and clicking in to details, gives me this similar error:ause:  cause:    cause:      cause:        ErrStatus:          code: 404          details:            causes:              - message: 404 page not found                reason: UnexpectedServerResponse          message: the server could not find the requested resource          metadata: {}          reason: NotFound          status: Failure      fields:        - name: Resource          value:            Group: extensions            Resource: ingresses            Version: v1beta1      function: kasten.io/k10/kio/exec/phases/phase.k8sObjectTypeObjects      linenumber: 302      message: Failed to list resource    fun

We have a project study backup SAP and SAP HANA, High Availability from 2 Suse Hosts HA. As knew, the 2 Hosts each has local disk for store Database and log, and it work as Active and Standby Hosts. So my question is that when we installed Veeam Plug-in for SAP HANA for both hosts. Can Veeam support backup SAP HANA,HA from both hosts?  If the SAP HANA, HA use VIP (Virtual IP) for access both hosts, can Veeam support backup from SAP HANA, HA using the VIP? What will the database and log backup from HA Hosts? Will it keep only 1x copy (Database and log) from Active Host or keep duplicate from Active and Standby from both Hosts?

Hello All,I have a case i’m working on it customer has DC in cloud provider site and needs to move it to new DC he can’t make backup throw WAN because of traffic costs so we offers to get storage and put it in the cloud provider site and create second copy to it then move the storage to the new place and create replica seeding and make planned failover and commit the failover  any suggestion recommendation? 

Hello, I need to create a SQL DB backup for VeeamBackup DB (VBR 10). I’m using MS SQL Server Management Studio with Windows Authentication however the DB is not accessible with this user, do I need to use SQL Server Authentication with th “sa” user? if yes, I don’t have the password, is there a default password? if no, can I try to reset this password without problems? Thanks for your help, Omar De Souza.

Hello,Everything is in the title, it’s the first time i’m using Veeam.So, i have a VM on ESXi A, i want to setup an incremental backup of this VM to ESXI B that has a LUN assigned to it (the datastore is created).But i have no idea how to do it. When i create a backup job, when i get to “storage”, i can only chose the default backup repository, which is on the local hard drive where Veeam is installed...I don’t know how to create a new repository that will point to my “backup-LUN” datastore on ESXI B …Can you help me ?Thank you in advance,Regards

Hi,Backup jobs target is SOBR with capacity tier.I have an option to configure versioning and lock on the capacity tier bucket.Can someone please tell me what could be the impact?Thanks,Moshe Mazor

Hey guys,I am currently using v11. To use v11a, should I perform upgrade or download a cumulative patch and perform update?

I’m using Veeam 11 (11a? not sure how to tell) Community Edition on my home network.  Mostly everything is working fine; however, two of five win10 computer agents (5.0.1.4584) in the inventory are showing :  Microsoft Windows version installed on this machine is not officially supported by Veeam yet.  which is AFAIK is incorrect - both are standard Windows 10 Pro installs (I have never used any dev or pre-release builds).  For example, the machine that gave the above is 10.0.19044 N/A Build 1466 which according to this page https://docs.microsoft.com/en-us/windows/release-health/release-information is a production release, not a Technical Preview. Where is the issue?  How do I convince Veeam that it a production OS? PS, in case you are wondering; the backup still works.  The issue is my reporting mechanism… since Veeam reports a Warning due to “Technical Preview”, I keep getting alerts about the issue. 

Hello,We want to perform VEEAM backups on a server that has MAXDB. Is there an agent allowing MAXDB backups including logs as it is the case for SQL Server? Moreover, it seems to believe the forums that restoring a VM with a MAXDB database leads to an inconsistent database if you don't freeze it first. Is it always the case? cordially

I am just starting out doing Veeam SQL backups and one thing I found is I need to be able to exclude certain dBs from getting backed up in Veeam. The dBs that I do not want backed up are for dev and the dB is restored to a different server nightly so when a Veeam SQL log backup happens I’m getting the error “Collected SQL Server transaction logs do not match any existing database backup: DatabaseName” which is 100% accurate.I do not take full backups every day so when the logs are getting backed up this particular dB does not have a full associated with the log backups.This dB would not need to get backed up at all.