Solved

dears, please we have configured the backup job to be encrypted from advanced menu and we create and pass for encryption, but when try to restore individual file the file restored normally and visible without asking for key, so please i need to know how to fix it  

Hi,I testing Kasten K10 in a new installed AWS EKS cluster using k8s 1.29, so I follow the latest documentation and installing using helm and the extra set parameters  secrets.awsAccessKeyId and secrets.awsSecretAccessKey.Almost all Pods comes up and PVC accept one pod and PVC that is catalog-svc. When I do a kubectl logs -n kasten-io <PODNAME> --all-containers=true it give me nothing, but if I do a describe on the pod it doesn’t give me a lot of information.  Containers:  catalog-svc:    Image:      gcr.io/kasten-images/catalog:6.5.10    Port:       8000/TCP    Host Port:  0/TCP    Requests:      cpu:      200m      memory:   780Mi    Liveness:   http-get http://:8000/v0/healthz delay=300s timeout=1s period=10s #success=1 #failure=3    Readiness:  http-get http://:8000/v0/healthz delay=3s timeout=1s period=10s #success=1 #failure=3    Environment:      AWS_ACCESS_KEY_ID:                              <set to the key 'aws_access_key_id' in secret 'aws-creds'>      Optional:

Can you use and test with SureBackup if you are only using a Linux Hardened Repository?

Hello everyone, This morning during my VMware VM backup job, I encountered the following error:Error: Cannot proceed with the job: existing backup meta file 'Prio 0.vbm' on repository 'ds_veeam_sanctl03' is not synchronized with the DB. To resolve this, run repository rescan As explained in the message, I initiated a rescan of the datastore on my NAS. The scan failed with this error:11/01/2024 09:10:58 Warning    Failed to import backup path nfs3://xxxxx:/|volume1|ds_veeam|Prio 0|Prio 0.vbm Details: '.', valeur hexadécimale 0x00, est un caractère non valide. Ligne 1, position 1.  I did not find any information about this error in the knowledge base or other forum messages. I am using Veeam Backup & Replication 11.0.1.1261 P20220302. Thank’s for advance.Philippe.

Hello, Thanks, I am not able to perform an instant restore of a linux VM.I am stuck that the helper appliance dialog box.I select a server from the list, but the OK button is disabled?Using VBR 12.1.0.2131I searched around the forum and internet, could not find the answerPlease advice, thanks, David  

This is very high priority if that is not clear by the title.The webinar was earlier this week and included instructions - does anyone have a copy or a link to the replay? Thank you!

Hey everyone,We've encountered an issue with our immutable backup setup. We've configured our Ubuntu server to shut down after completing the backup, turning it on before initiating the backup process. As a result, the server shuts down at 1 AM every day after finishing its backup routine.However, once a week, we receive the following error message. I've been able to resolve it by deleting the file, but it keeps reappearing. Is there a way we can extend the immutability time to avoid this issue recurring?  A problem occurred during setting the immutable flag: repository time shift detected, immutability flag cannot be set. Please refer to KB4482 for more detailsProcessing finished with warnings at 3/17/2024 10:33:16 PM

Hi,I am trying to create a SureBackup job using replicas rather than run from the backups (For performance reasons) but when I go to add a VM from replicas there are no objects in the Select Replica screen.the replica is stored on a standalone Hyper-V host with large DASI’ve created replicas from live VM’s and current backups and although they exist in the replicas folder, there is nothing appearing in the Select Replica screen in the SureBackup application group settings.I’m running VEEAM 12.1.1.56 Any ideas, it’s driving me nuts ThanksRhys 

I have to set up a structure like 7 daily, 4 weekly, 12 monthly and 5 yearly backups for my workplace, but am somewhat restricted in budget and storage space per device, so I have two NAS as backup repository, but each one allone is to small to save all the backups.Now I am looking for a way to spread the backups over both NAS, e.g. save daily and monthly to NAS A, weekly and yearly to the NAS B. My initial idea would be:A regular Backup Job for daily Backups, targeting NAS A, set up asSchedule: Run everyday at 9 pm; full backup every saturday Storage Retention Policy: 7 restore points Keep certain fulls longer: unchecked Configure secondary destinations: checked Secondary Target: Weekly Backup Copy Job Monthly Backup Copy Job Yearly Backup Copy Job My next step is to set up the Copy Jobs, they all share the following settings:Immediate copy (mirroring) Object is the Daily Backup from above Schedule is any timeDepending on the backup the target differs:Repository is either NAS A o

I’ve been testing syslog with v12.1 and I cant seem to see messages related to an unsuccessful login to the VBR console. We see messages for logins and logouts but not unsuccessful.I’ve also configured Veeam ONE syslog and this seems to show all logins but not VBR.I have even tested this with the Veeam lab “test drive 12.1” at https://propartner.veeam.com/hands-on-labs/ has anyone else tested this at all or had experience of it? We need to get unsuccessful logins somehow…. thanks

Ho letto nell’articolo di VEEAM sull’Immutable Storage che è necessario creare un data repository basto su Linux server.Qualcuno a qualche informazione in più ?Distribuzione ? RAM ? CPU ? Tipo di storage consigliato ?Devo ancora approfondire ma intanto volevo sapere se alcuni di voi hanno fatto dei test.Grazie.Fabio. 

This is a very interesting warning. I migrated lots of VBR servers, and it’s the first time I've run into this warning.The detailed warning message is below:Warning Failed to connect to Red Hat Virtualization plug-in: Failed to login to platform service: The remote certificate is invalid according to the validation procedure.It happened after I migrated from the VBR server with SQL Express to the new VBR server with PostgreSQL.All Hosts and repositories are pure Hyper-V environments. There are no Linux servers or repositories.It’s easy to fix this issue. I rebooted the VBR server and ran the backup configuration again. The warning message is gone. Does anyone have the same experience? 

My console stopped opening yesterday, crashing and complaining about clr.dll. There’s a R&D post about removing the user.config file (Here), but that didn’t work. Anyone else recently seeing this? Log Name: ApplicationSource: Application ErrorDate: 12/7/2023 6:27:37 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: MANBK-CARM-VEMDescription:Faulting application name: veeam.backup.shell.exe, version: 12.1.0.2131, time stamp: 0xf82aa70aFaulting module name: clr.dll, version: 4.8.4645.0, time stamp: 0x648f6f63Exception code: 0xc0000005Fault offset: 0x0000000000018551Faulting process id: 0x2064Faulting application start time: 0x01da290041bfb33eFaulting application path: C:\Program Files\Veeam\Backup and Replication\Console\veeam.backup.shell.exeFaulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dllReport Id: 53fe947b-0942-450e-9476-4cda770d3a62Faulting package full name: Faulti

Hi!I am testing Kasten and currently face a problem with Exporting the snapshot of a PVC that belongs to a VM to S3.Error:- cause:    cause:      cause:        cause:          cause:            message: volume's storage class does not support block mode export          file: kasten.io/k10/kio/exec/phases/phase/artifactcopier.go:874          function: kasten.io/k10/kio/exec/phases/phase.(*ArtifactCopier).maybeUseGenericBlockUploader          linenumber: 874          message: volume's storage class does not support block mode export        file: kasten.io/k10/kio/exec/phases/phase/artifactcopier.go:632        function: kasten.io/k10/kio/exec/phases/phase.(*ArtifactCopier).getSnapshotConverters        linenumber: 632        message: blockModeUploader      file: kasten.io/k10/kio/exec/phases/phase/artifactcopier.go:268      function: kasten.io/k10/kio/exec/phases/phase.(*ArtifactCopier).Copy      linenumber: 268      message: Error converting snapshots    file: kasten.io/k10/kio/exec/phase

After upgrade kasten 10 i received the next errors in pods: And deployments The console show me this: Other upgrade show me this:root@SIPC09074:~/kasten10# helm repo update &&   helm upgrade k10 kasten/k10 --namespace=kasten-io -f k10_val.yaml --version=6.5.4WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/.kube/configWARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /root/.kube/configHang tight while we grab the latest from your chart repositories......Successfully got an update from the "kasten" chart repositoryUpdate Complete. ⎈Happy Helming!⎈WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/.kube/configWARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /root/.kube/configError: UPGRADE FAILED: Unable to continue with update: ConfigMap "k10-eula-info" in namespace "kasten-io" exists and cannot be imported into the current

Patched VBO to the latest version; installed windows updates recently; tested console restore and backups and both were fine. however, notcied the next day that portal is not functional.  The portal appears, you input credentials, it takes you to azure portal; you input credentials again and url chanegs to the portal again and it just stays thereLogs show14.03.2024 09:30:11.727]   55 (19664) Authorization started (grant type: OperatorAccessTokenResponse)[14.03.2024 09:30:12.260]   55 (19664)  Authorization succeeded 14.03.2024 09:30:12.261]   55 (19664) Error: IDX10634: Unable to create the SignatureProvider.Algorithm: 'RS256', SecurityKey: 55 (19664) Type: System.NotSupportedException this algo is supported in Windows already checked  We are using the same self-signed certificate when restorng using the VBO console which works fine and the backups have been runnig as well;  I have already tried a new self-signed certificate for restore app; still the same issue.  Veeam support advised

Hi guys,I need some help to export my incremental files on tape.Policies: Archiving Full backups once a week on new tapes and used tapes are exported, archiving Incremental backups on new tapes and used tapes are exported. Entity Configuration settings Media pool Full and incremental backups use different media pools. Media pool (retention) Protect data for <desired period>  Media set (retention) Create new media set for every backup session Source (backup job) Forward incremental backup that runs daily with synthetic  Tape job Export current media set.. on specific days Scheduling Forward incremental job running every day with weekly full backup. Tape job has been scheduled to run every day after primary backup.  When I configure only Full backup archiving everything works fine, my synthetic are created the Friday night, the tape job is scheduled the Saturday morning, the job copy only the latest backup files.Now I have configured my job to copy the

Lets say a periodic legacy backup copy job “LEGACY” was configured to copy 3 source jobs: JOB-A, JOB-B, JOB-CDuring the creation of the new-format backup copy job named “NEW”, only source job JOB-A was initially included.  On the storage tab, target mapping was used to point to the “LEGACY” job.   This triggered a format upgrade for all items inside the LEGACY job, creating a new target named “NEW”.Now I want to edit the “NEW” job to add “JOB-B” as an additonal souce.Do I need to return to the storage-tab of the job and choose target mapping and select “LEGACY” again?What happens if I do?Will it recognise that this chain has already been converted and correctly target “NEW” instead?

Hi Everyone,I need some guidance on deploying a new hardened backup repository as a SOBR extent. Current we have a customer which uses a regular windows repository as extent doing copy to an Azure blob. We need to move all the content (backup chains) from this Windows repository to the hardened one (using imutability). I´m trying to find out the appropriate way to do that. There is only one performance extent (with data locality policy) and we are not able to add the hardened repo because all extents need to have same imutability settings. Cannot evacuate because there is no other extent to evacuate.How can I accomplish this without having to download metadata or resync data with Azure blobs? Our goal here is to only offload old repo content to the hardened repo and set them as extent copying data to Azure, if possible, doing little to no change on Azure tiers/blobs to avoid costs. 

Hello,Refer below setting:- backup job vm_to_disk with full and incremental keep 14 days- backup job file_share_to_disk keep 14 days, it should be full and incremental for file share backup- backup job vm_to_tape- backup job file_share_to_tape- two jobs vm_to_tape and file_share_to_tape backup to one tape setup with "Do not create, always continue using current media set", manual execute end of every monthrefer two jobs backup to one tape and it will require use "Do not create, always continue using current media set", t will append backup content to the content that was written to tape with a previous backup session. If, however, a backup set is started with a new tape, Veeam Backup & Replication will create a new media set for it.Does it mean jobs vm_to_tape and file_share_to_tape execute full backup when insert new tape? Best regards, 

I’m using B&R 12.1.1 and having the following error with a single Server 2016 VM backup.Failed to index guest file system. VSSControl: Index failedI’ve checked that all discs have plenty space but not sure where to look for more information.Any suggestions welcomed. 

what is the correct permission to give backup repository:Ubuntu document its mention chmod 700 and in the redhat its 2775, which one is correct permission, kindly suggest. Appreciate if i get preparation process steps for redhat linux 8.x version for veeam 12.1  

hi Veeam CommunityI have a backup server that uses the drives in the backup server as a repository, and the backup server works as a workgroup. I want the permissions on these drives to be only for the veeam service.I want to do this for more security.My question is whether such an idea is good?If it is good, what permissions should I give to these drives?

HPE m'a livré la cartouche LTO sans code-barres, et Veeam Backup & Replication indique dans la documentation que c'est obligatoire. Alors, comment dois-je procéder ? Dois-je retourner chez HPE pour demander un code-barres, ou existe-t-il une autre solution?

Is it possible to make the traffic from Veeam Agents go directly to Wasabi instead of going through our VSPC/VCC server? This will create a lot of network traffic and engress cost for us in Azure. In the manuals it says we should create cloud connect repository (with f.ex) wasabi. Was hoping that even this sets the Cloud Connect Repository in Veeam Agents, it would understand it was an object storge and route the backuptraffic directly to Wasabi itself.