Discussion Boards

Hello guys,One of my customer has encounter the following error message in a backup job.I never saw this message before. The Veeam version is 11 last patch.It’s a linux repository.I asked to my customer to open a support case, but in parallel maybe one of you has already meet this one ?!

Ok, I had a test server which I used to test out Windows Agent backups.I’ve now built a more robust server to handle veeam (community edition as we only have a few servers), when I try to backup the same server, I get:I’ve removed the backup jobs, and uninstalled the agent both using the old server and manually going into Add/Remove programs, yet the same problem exists. I’ve also added the registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication AgentDiscoveryIgnoreOwnership DWORD=1Still no joy.  When I go into the registry editor on the machine in question, I can see why Veeam is having a problem.  The values in BackupServerIPAddress, JobSettings, and VBRServerName are all pointing to the wrong server. I’m loathed to start deleting this key.  What do I do to ensure this server I wish to backup now has the correct agent installed?RegardsIan

HI Community, I am currently using Veaam v12 B&R community edition.I have tried to add a service provider for ekco.I have followed steps from https://www.ek.co/publications/using-veeam-cloud-connect/Once I add veeam.cloudhelix.io and the username and password I get the below error.Is the issue down to the fact I am on community edition V12 or is it an issue from ekco’s side?(I have already logged a ticket with ekco support to see what their response will be) 

My question is, if we are excluding SQL data volumes from the original backup job, can we still do full SQL backups and transaction logs using application-aware processing?For some background, in our current state my team is backing up our Windows SQL VMs using a Backup job, then use a Backup Copy job to get those offsite. Since the team has historically ran SQL Agent jobs to do daily full and hourly log backups for each DB they decided to exclude any volumes storing SQL data from the Veeam Backup job. I see the reasoning and I suppose this works, but I’d like to shift to including Veeam on SQL backups so we can easily get those offsite using the existing backup copy jobs.Finally, a sort of related question, if we can use Veeam and the SQL agent jobs in tandem, which one should truncate those? In my testing I’ve had to set the SQL Agent job to copy only mode for things to work, but I feel like setting Veeam to copy only mode should work as well, but I must be missing something since I

Hello to all,As I configure a testing Job with Multiple VMs with the same OS, I can see that there is no difference in the deduplication rate in Report when I run the VM itself alone or in the Group.One more point to ask:The VMs in the Backup Copy Job are all started at the same time when the job starts.Is this how it should be or they need to be run one at a time?

I'm here to show you a little working proof of concept I put together during the Veeam 100 Summit in Prague last week. It's very much a work in progress, but I'm excited to share it with you.(video and callout at the bottom for feedback) Let's dive into the tech stuff and some notes on what we're using.So, we're making use of the Veeam VBR Rest API, as you will know I am a fan of any API especially when it comes to Veeam. The prototype is put together using Node.js. It's like the middleman between the frontend and my VBR server and OpenAI. (we're rocking the gpt-3.5-turbo-0613 model). Although I'm thinking about going with a locally hosted model in the future, especially for sensitive backup server data. But for now, in this prototype and my lab setup, I'm good with this setup, nothing for me to worry about with the few machines I am protecting.For this prototype, I've focused on Backup Jobs and Backup Sessions, and it chats with four VBR Rest API endpoints to make it happen./api/v1/jo

We have configured our backup copy jobs to execute in a continuous mode and hadn’t any issues until the other day.  Ten (out of 100) of our backup copy jobs failed, with the error of “Unable to copy the backup: some backup files are located on an unavailable scale-out repository extent”.  Checking the restore points on the source and target repositories, we noticed the restore points (for the most recent backup) for the target repositories were in an incomplete state.  We performed the following manual steps to resolve; Disable backup copy job After reviewing the target repository from the backup copy job, the identified servers with the error, have the most recent restore point showing incomplete. Rescan the target repository Then process the incomplete restore points by selecting forget Rescan the target repository Enable backup copy job and executeWe did open a support case and the engineer discovered the issue we experienced stemmed from the backup copy job interfering with the bac

I’m very new to Veeam. We use VMware vSphere. I need to be able to backup an entire VM, and be able to restore just individual files from that backup. I thought that doing a “VMware Backup” type of job, with “Guest File Processing” enabled would allow me to do that (i.e., restore just one file from drive E:, as an example). But when I try “Restore Guest Files” on that VM, , I get “Unable to mount disk: unsupported disk type” when it goes to Browse. Have I totally misunderstood what type of backup job I need to be doing, to be able to do an individual file restore of a Windows VM? What type of backup do I need to be doing then, to accomplish what I need? This type of backup looks like I can only restore the entire VM, like a bare metal recovery. Which is good, and I might need that, but I definitely need to be able to restore individual files. Do I need to make a backup job of type “Windows Computer”? I won’t need to push the Agent, because the VM is always connected.Sorry for the newb

Please see the new NetApp StorageGRID and Veeam Best practices link below. You will see some recommendations from NetApp around using a larger object blocksize. This will increase the size of incremental backups. Please work with the NetApp StorageGRID team to optimally configure and size NetApp StorageGRID appliance for customer capacity and performance expectations. As always if you encounter issues please open up a support ticket to track the issues that the customer encounters😀. https://docs.netapp.com/us-en/storagegrid-enable/tools-apps-guides/veeam-br.htmlThanks,Pete

Hi All,Why does Veeam Backup for Azure (Azure Files) have no scheduling option for yearly retention?Is this in some way related to the Azure only allowing up to 200 snapshots on Azure Files? In which case would a feature like we have with VM snapshots being used to create a more traditional backup be worth thinking about if you require longer term archiving? Cheers,

my goal isI use veeam to back up my vmware vm machine to a NAS, and then I back up the backup files from nas to aws s3. Then I can directly read the files from s3 and restore the vm machine in aws.But I am currently encountering a problem. The backup from veeam to nas and then from nas to aws s3 goes smoothly, but my veeam cannot read the files backed up by nas in aws s3. Please tell me how to set it correctly.

Hi to everyone,I want to create a DR plan in AWS.Is there a way to restore a Domain Controller (Windows Server 2022) in AWS keeping all its configuration and function as AD, DHCP and DNS? When i try to restore it into the cloud, i’ve this error:Impossible join with these credential because your domain isn’t available….. Do you have some advice? Thanks. 

I’m using NetApp 9.12 just a cifs smb share. I followed the instructions from veeam to create the storage infrastructure for netapp and the subsequent NAS filer. I created a file to tape job to use vss and confirm that the snapshot is being created by veeam on NetApp. I have the virus scanning to exclude the directory based on NetApp’s published kb on excluding snapshots from vscan. What is the right format of '-paths-to-exclude' in 'vserver vscan onaccess-policy' command? - NetApp Knowledge BaseUse Snapshots to backup SMB File Shares on your NetApp ONTAP system (veeam.com)With vscan enabled veeam will just stop transferring completely for long periods of time. With vscan disabled it backs up normally. How can I tell if veeam is actually using the snapshot it creates and not just trying to access the files? In the file to tape job I have use ms VSS checked in the options. in the SMB file share I have it set to backup from a ms VSS Snapshot and “failover to direct backup if a snapshot i

Hello,We had 13 Backup Jobs that were all started in the same time period from 21:00 to 22:00.VBR server had 32 GB of RAM and 10 cores. It was a VM.All Backup Jobs were with single VM inside of it.Was this good approach or it was too much for our VBR Server to handle.We didn’t have any off-host Proxies and VBR Server and 60% of VMs were on the same Hyper-V host.It was acting then as only proxy for those jobs as I can assume.What would be the better approach on this?I’m still trying to grasp Veeam with his technologies as best I can..

I’m using Veeam Community (free) license, and I want to use swapped external hard drives as offsite backup for my locally hosted repository.  But when I try to create a pruning Backup Copy job, it keeps saying I need Backup and Replication Enterprise Plus.  The descriptions I’ve read make it sound easy, but they’re all vague about what sort of license is required.  It’s like they are conflating “community” as a forum and as a license?  I absolutely cannot upgrade to a paid license.What am I missing?

Me again with new topic 😁At the moment our VBR Server is located on the Hyper-V Host where are also the 50% of VMs that we are backing up. Without Using Off-Host proxies I can guess that all load will come to Hyper-V host which is hosting VMs and VBR also.I guess that data movers from source VM and VBR are run on the Hyper-V host itself.What would be the best practice for placement of VBR?Is it good idea then to isolate it from the VMs that we are backing up or?I can host it on some Hyper-V Host which doesn’t have productive VMs or anyAlso then our off-host backup proxy should be physical machine or somewhere where we also dont have anything?

Hello Forum,I have question about few things so that I make the change as smooth as possible.The plan is to create everything from scratch because our current configuration is really awful and time for change has come.  Current Situation is like this:VBR V11 on Hyper-V VM Subscription: Enterprise Plus Instances: 20 (13 used) Inventory: 1 Hyper-V Cluster  2 Standalone Hosts Now I need to remove everything from this server and to transfer the license to the new one Questions:How to transfer the license? How to properly remove Inventory so that I don’t have problem when adding it to a new V12 VBR server? I know that few folks had problems when attempting to add the hosts to new VBR, something stuck on the old VBR etc. I will not do a configuration backup because I want everything from scratch. Please feel free to write any other recommendations that I need to take care off.I did it one year ago but I would need the help from Veeam Legends to do it the propper way this time 😁

Since upgrading to V12 VeeamBR (and having to revert to a snapshot due to critical error) I get this on every SOBR tier job. I have rescanned both the hypervs as well as the azure blob then ran tier job now but still get the same error every time  Backup file version mismatch: scale-out backup repository rescan is required.

What does Orphaned and Imported indicate next to Disk in Veeam Backup and Replication under Home tab? 

When attempting the restore I get the log into Microsoft with the device code and it connects fine, hit next and veeam errors out saying Failed to open mailbox: gives the name Mailbox does not exist. I can guarantee the mailbox does exist.

Hello. The question concerns the display of repository capacity in the Veeam user interface:In the EMC DD console, the capacity is displayed in TiB and is equal to 166.7 TiB. In the Veeam UI, after adding EMC DD as a repository, the same capacity is displayed, but with the TB label.If the size of repository is displayed in TB, then it should be approximately 182.5 TB.Is this a Veeam UI error?  

Hello everyone.Am not sure if this is the write place to ask this..I forgot the encryption password i have set for my veeam backups, and i want to access the veeamBackup database to get the encrypted password and decrypt it as the online manual says. But as soon as i login to the database with sql server studio with the windows authentication settings, the Veeambackup is not accessible. The sa user is not active. This manual here ‘How to install Veeam Backup and Replication 11 Community Edition with a dedicated SQL Server | Veeam Community Resource Hub’ is exactly the same as my setup, but as soon as i get to the part there i am suppose to open the database VeeamBackup to see the tables etc, i get an error ‘The database VeeamBackup is not accessible’. Also added a screenshot below to show it.Any help on what am i doing wrong?Thank you  

hello,I would like to know, can we use backup copy to SOBR repository as a target ? Thank You

Hello, Thanks,My question is about Veeam catching memory errors during the backup itself.Sure, sometimes ECC can catch that.For example, Let’s say Veeam:Reads a sector from disk into memory. Whilst that sector is in memory, the memory is corrupted. Veeam writes that corrupted sector to the backup file.A Health check would not catch that.Does Veeam have a way to catch that, by re-reading the source sector again or some other mechanism?Thanks much,David   

Hello, I will need to migrate my Veeam Backup & Replication (v12) installation to a new server because my current server is 2012 R2 and it’s not supported anymore as you know.My new server (virtual) will be a Windows 2016 and I want to migrate my Veeam B&R install the proper way in order to avoid loosing any “block change tracking” or things like that and have my backups and replications running the same as before on the new server because I have around 25 TB of data to backup and replicate and if Veeam needs to re-read the entire volume (instead of “change blocks”) that would be 48+ hours lost! 😵 Thank you!!