Discussion Boards

Yesterday I came across an interesting bug using version 12.1.1.56 I have been creating plenty of jobs and test jobs to Wasabi without issue for quite a while. For some reason, one of the jobs I created gave me an error.  I thought this was odd as I had not enabled rollbacks, and there isn’t even a setting to adjust the setting for transform previous chains into rollbacks on Object Storage jobs.  Following KB4390 https://www.veeam.com/kb4390 There are 2 easy PowerShell commands to fix this issue.  The first command will find all jobs using the Transform previous backup chains into rollbacks option. Get-VBRJob | where {$_.BackupTargetOptions.TransformIncrementsToSyntethic -eq $True} It found the job in question, along with one of my snpashot jobs that had it enabled as well. Once again, slightly odd as it doesn’t use this feature. There are 2 ways you can resolve this using powershell depending on if you want to use Forever Forward, or Synthetic Full jobs. Disable Transform previous bac

Hello everyone!After reading some of your experiences and submissions, specially @Madi.Cristil s one, I’ve found some time to tell you mine,this is a personal story, here we go: Back on 2000 - 2001 , I was an exchange student flying from Spain to the US, without knowing any English at all, just few words, the worst pronunciation ever, scared and to the unknown.At the beginning, it was fine to take pictures with “single use cameras” (I’m felling very old right now)but after a while, I saw on Walmart a Digital camera, a Sony Cybershot!! OMG! 😱 1.3mpx of super high quality pictures, jpeg, TIFF and GIF! a monster!!I bought it, and quickly I started fulling the 64MB memory Stick!! tons of pictures, fortunately, the Computer I’ve got in the house had a 100MB ZIP Drive, so I started backing up my pictures in a Zip Disk, of course, encrypted, but nothing else.I came back from my exchange, life continued, and I just stored my ZIP Disk in the safe with other memories, letters, gifts, etc.Once i

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

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,I have 2 Hyper-V hosts:Host no.1: several VMs, VM replicas from Host no.2 and a VM with Veeam B&R server (v12) Host no.2: several VMs, VM replicas from Host no.1 including a VM replica with Veeam B&R server (v12)The repository for backups and replicas is an additional NAS server.I need to completely reinstall Host 1, so I need to temporarily move everything to Host 2 - including the Veeam B&R server.These are production servers, so the whole operation must be stable and fast. What is the best way to do this?

hi Veeam communityI want to run a sclae out repository and I need your help and experience.I want to buy suitable storage for all three tiers (performance, capacity, archive) and I want to have immutable capability in all three levels.Your experience and guidance can help me make the right choices.What features should be taken into consideration when choosing storage, what storages have you had experience working with and were they good experiences.Thank you in advance for all your comments   

According to Veeam documentation, migrating a legacy VBR (v11) to a new one (v12.1) requires disabling the services on the current server. This legacy server retains the ownership of all the Azure blobs used as scale-out repositories. All blobs are used to long-term backups. Regular short-term backup jobs are configured to local disk repositories.  My question lies in the moment after the restore process ends (with the option to migrate flaged). Do I just need to request ownership of the blob or is some additional procedure required to re-enable this scale-out repositories. Is there any chance to lose the chain inside this blobs after the restore? If restore fails somehow, can I just jump back to the legacy server? I cannot risk losing the backup chain held there, cause we are talking of dozens of TBs.  If there is some guide to migrate VBR with Azure blobs or anyone has ever had this need somehow, can please share the steps taken?

Hello, I am facing a connection problem between my VBR and my VEM.I applied a hardening since the connection with the local administrator account (built-in) is impossible I cannot find what could be blocking it, still investigate.MFA was enabled in VBR, so I had to create an entry for my built-in administrator account as a service account with Veeam administrator privilege.Unfortunately the session failed to openThe connection with another service account with admin privilege works..Any idea? The account must be assigned the Veeam Backup Administrator role. In term of security I’m not a big fan cause I have an account with admin right without MFA. How do you configure VEM on your side?

Hi Team, My customer has a setup for StoreOnce (3660 with Firmware 4.3.7) and Veeam (12) configured with Veeam Standard license.Scenario 1:Customer tried to take a VM backup to one of a catalyst store which failed due to licensing issue in the logs. However, I did not get any documentation mentioning Veeam standard edition doesn’t support catalyst stores. As per Catalyst store configuration I double checked and its as per HPE standards.Error: “Backup to HPE StoreOnce Catalyst requires valid enterprise edition of Veeam Backup and replication.” Scenario 2:Customer tried to back up the same test VM on StoreOnce NAS share and that passed successfully. Resolution:Could you share me any documentation which says the Veeam standard edition does not support StoreOnce catalyst store? Are there any changes in Veeam that needs to be done to support the above Below are the backup logs captured?      

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, 

Servers & Drive Numbers - Cause Chaos So, I thought for the blog of the month special edition I would go back to when I first started out in the IT world early in my career.  I found a job as a Systems Administrator at a small law office in downtown Toronto.  I was so excited to get my IT career going and this was my first job in the Sysadmin space.  The firm also had an external IT company as well under contract, but they felt the need to have someone onsite to provide easier assistance to users, manage servers, etc.So, I was working there for a few months when I happened to one day do my daily routine check in the server room and noticed an amber light on one of the drives in the server.  Now keep in mind I was new to IT and did not understand the concept of the hard drives starting at Zero not One (you can see where I am going with this 😂).So, to be diligent and ensure things were done right I contacted the person at the IT consulting company, and he told me that server drives

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. 

Hello team,Today, I replaced an HPE Gen 10 server. After adding it to the cluster, I encountered an issue with remediating it to install the IO. I observed that VMware has removed the HPE Gen 10 Proliant from their Cycle Center, making it challenging to apply the CDP IO. Has anyone else noticed this issue?   

We are beginning implementation of the DB2 plugin in v12.1. Looking at the documentation online, we see commands and examples for backing up and restoring backups, but you have to know the date/timestamp for the file to restore. There is no command to list available backup files using the plugin that is documented online (that I can find, anyway). However, a helpful engineer that we consulted with during pre-buy provided us with a command to list the available backups using the agent (db2 list history backup all for <db name>).Now I’m wondering why that isn’t documented online, and if there is a document somewhere that lists all of the commands or methods possible with the DB2 plugin.Does anyone know where we can get that documentation?

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  

Taking SMF file share backup on Linux hardened immutable repo 7d retention,  want to retain same data for 10 years with immutable on AWS  glacier storage . (minimum storage cost ). Is that possible. Any alternate option..

Hi, got a warning email from backup profile. Detail as below:Source is storage server HPE MSL3040 3250 Destination is workstation with OS Win Server 2019 Profile backup is File to Tape Details warning is: Failed to create a VSS snapshot for E: Details: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))I’m tried to follow this but doesn’t work: https://www.veeam.com/kb3099Please anyone if you have clue or suggestion for this issue. Thank you.

Ok gang, I have a weird situation.I have a job where I removed a server and added another one that replaced it.  Different server names, IP’s….Everything was running fine for a long time but all of a sudden, when the job runs, it completes without issue. Then a second job runs with the same job name but showing the previous server and job settings (which of course fails due to the server no longer being there).  It’s even doing the typical 3 tries before it gives up.Any ideas on how to get rid of the second run?Thanks in advanceJD

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?

Hello, I need to install the product for new customer and I don’t find anything on internet about how to manage job for organisations “medium size”.My customer has 8 Active directory forest and all are sync inside the same Azure tenant.I need to backup all of them.Is it “better” to have only 1 Exchange job (same for sharepoin, ...) for all or better to create 1job / domain name (each forest has a different public domain).I mean : Exchange job - Target organization and select only mail + archive and add exclusion for what I don’t want.ORExchange domain1 job - Target AAD group with domain1 users and repeat it for all other domain. What is the solution to be sure I backup actual object AND futures one. If I select organization → It’s ok. If I select group, I need to be sure user is inside the group (Dynamic group is ok). What about sharepoint site ? When I select a group and check sites, it will backup personnal sharepoint site right ? but for the other one how do you manage it ?  I don’t

Are SharePoint permissions backed up using Veeam for Microsoft 365? Scenario:  A group with inherited permissions is removed from a SharePoint folder but later found to be required.If we restore the folder, will it restore the security groups/permissions associated with that folder at the time of backup?

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.