Community

Veeam Backup & Replication v12.1 + Spectra BlackPearl = On-Prem Archive Tier Veeam Backup & Replication (VBR) v12.1 is loaded with many great new features and enhancements.  One of the new features is the extension of the Archive Tier to on-premises storage solutions that are Amazon S3 Glacier compatible.  Spectra’s BlackPearl S3 Hybrid Cloud Storage is one of those solutions.But what is the Archive tier?  It was first introduced in Veeam Backup & Replication v11 back in February of 2021.  The Archive tier is an additional tier of storage that can be attached to a scale-out backup repository (SOBR).  You can transport applicable data to the archive tier for archive and cost saving purposes.The following types of backups files are eligible to be sent to the archive tier:GFS backups Orphaned GFS backups Veeam Backup for Red Hat Virtualization GFS backups

I have seen may posts on the above topic but not is the resolutions have fixed my problem.  The account used is part of the local admin group, is part of the domain administrator group and has log on as a service.  When running the backups, most VM’s (VMware) fail with the subject matter.  When I run the Test Credential on the same backup group, most pass successfully, but then fail when the backup begins.At a loss as to where to go to next.

Good day everyone, Did some checks, seem as if for my HyperV Backups, reverse incremental is the only option recommended to save space. My management team dont plan to increase/purchase additional space anytime soon.I am seeing A LOT of VBK, VBM and VIB files,  i tell you, just incrementally taking up space. Over the weekend one fullbackup windows server agent job had like 4 vbk files (at various states/dates) with multiple vib backed over time (based on schedule not stipulated by me, but management). The local repo RAN out of space, 0 bytes free. This repo is like 7 TB, small i guess.Which is the best method you would recommend to save save space for both Hyper V and Windows Agent backups? 

Hi,Anyone can help with this error from a physical server backup?“10:30:32    Calculating digests Error: Could not find file 'C:\Windows\TEMP\tmp171E.tmp'. Could not find file 'C:\Windows\TEMP\tmp171E.tmp'.  “ 

Hi Community -Yes..I ask questions too! 😉 I recently noticed a subset of my Backup Jobs performance going from hundreds of MB/s to just 5-10MB/s since last Fri. I updated my Veeam environment on Sun and initially thought it happened after that (I noticed yesterday a few jobs took 4-14hrs to run!), but after further investigation I found the perf drop started 1st thing Fri morning. I have 2 other subsets of Jobs which run fine. Each of the 3 “sets” of Jobs use different Proxies and Repositories. So this whole subset which use a certain physical Linux Proxy and physical Linux Repo has this performance issue. Another subset which uses a different set of physical Proxy and Repo boxes are fine. And the last subset of Jobs which use hotadd are fine. So I’ve obviously narrowed down the issue is either the physical Proxy or Repo on this subset. The Job stats went from bottleneck of Source in the 90% range to Target in the high 90% range. I’ve checked my Proxy frontward and bac

We plan to do daily backups to a tape (which can be added but not deleted) for 7 days. I am confused on the following options in Veeam. Which one to use . I have  gone through the user guide, but need a simple advise on the usage scenarios. Please adviseWORM Tape protection Retention period

HelloA customer configured his Wasabi bucket with immuability set on Wasabi side. I know is not the recommendation in term of configuration normaly I set versionning and objectlock on the bucket only and the immuability is set in the repository Veeam.The problem is the consumption continues to grow on the bucket. In Veeam the number of restore points are correct but I have a lot of error in the SOBR task like: Not good!A lifecycle policies has been set, but I never used this kind of rule so I m not sure of the result especialy with Veeam. In Veeam in the repository we have this warning: 

I’m having an issue with backuping up one of my servers using Veeam Backup & Replication Version 12. Its been 15 days and I keep on getting this error:Processing [Server NAME] Error: Connection problems. Task failed. Error: Connection problems.

 I’m noticing that memory usage spikes to 95% every 15 minutes before dropping back down. Upon reviewing the history, it seems that the Configuration Database Resynchronize is performing a scan during these spikes.Is there a specific reason why the database synchronization needs to happen every 15 minutes, even in the absence of active backups? Is there a way to reduce the frequency of this synchronization?   

We want to switch to Veeam from Arcserve to see if it is better for DR scenario.  Arcserve is good product and does everything what we needed until we switched to SDWAN solution. We used to have primary backup console at production site and remote replication server at DR site. When switched to SDWAN primary server can not replicate backup to remote server (even though nothing blocked). So we have to moved replication server to the production site leaving backup repository at DR site. As a alternate solution, I copy replication server’s C: drive to DR site. If we have replication server at DR site, I can create virtual standby of VM to DR site every night. So in case of disaster this will reduce restore time. We also want to test DR solution every six month.I want to know does Veeam provide similar or better functionality in term of restore VM on DR site without relying on production VBR server?Thanks  

Hi, I am trying to back up some linux VMs, the VMs are running on Hyper-V 2016. The backup job starts fine, but it freezes at 63% and fails with the error message below.   17/05/2023 10:00:39 :: Processing SRV-SFTP-02 Error: Shared memory connection has been forcibly closed by peer.Failed to upload disk. Skipped arguments: [shadowSpec>];Agent failed to process method {DataTransfer.SyncDisk}.

Hi,  We’ve just upgraded our Veeam Backup and Replication server to v12.1.0.213.  All went very smoothly.  I also upgraded the Backup and Replication Console, which sits on another server, to the same version. We usually use this for access to Veeam.  Again, the upgrade went well with nothing untoward being apparent.  However, now my Veeam console will not log in to the Veeam Server. I get a message saying “Failed to connect VeeamBackup & Replication server: The logon attempt failed.”On investigation, I found that this occurred when I was using the server name (as the field was auto-populated with this info from before the upgrade).  However, if I use the IP of the Veeam server, the console connects as expected.  I tested this using the full FQDN of the Veeam server, but still did not connect - it only seems to connect using the IP. Has anyone got any suggestions of how I can connect using server name again?Thanks. 

Hello Community,I have been thinking a lot lately about a fourth book for my Veeam series that I have already done but this time focusing on the Security aspect of things with all the new enhancements in the 12.1.x and 12.2 releases.Would there be an appetite or need for a book like this?  I am trying to guage interest from the community to see if the effort is worth it at the moment or do I wait to just do the fourth book when v13 comes out instead like all the other previous ones.Here are some topics I am thinking of for the book to give you an idea of what I would write about.Cybersecurity - Inline Malware, Suspicious file activity, Early thread detectionRansomware Recovery & Response - YARA backup scans, threat tracking, event forwarding to SIEM/SyslogSecurity & Compliance - Four-Eyes authorization, KMS Integration, Security & Compliance monitoring (Security & C

Hello, I wanted to share with you a customer’s feedback that I encountered. They contacted me to report extremely slow restoration times during a file restoration process.I was a bit surprise cause I had tested all types of restauration on his infrastructure and everything worked properly.The restore type : “Guest File Restore” OS: Microsoft Restore option: Keep Folder Size : 64 MB Restore Time: 1h30min 😱I first checked the log in the History I directly noticed the fact that the restoration is via vSphere guest interaction API and not using a Veeam proxy .After a brief exchange with the admin, it figured out that the VM to which the files should be restored is in a new Vlan ! You’ve probably guessed it, but it’s once ag

INTRODUCTION Hello everyone, as you know the new version of Veeam released the past few days is full of new features.In this post I would like to go into more detail about the two new roles added for VBR management: Incident API Operator role and Security Administrator role. INCIDENT API OPERATOR ROLE Following the least privilege principle, this new role does not have access to the VBR console, but it can interact only with Veeam Incident API REST endpoint and manage malware detection events.MFA is not supported for this role (it is considered like a service account) and it is disabled by default.

using the free version of veeam to start testing with, currently have it installed on a single physical machine and trying to take a backup of it, and put the backup on an external drive, or even locally on the second hard drive of the computer but whenever running, it keeps failing, doesnt seem to connect, tried to set the machine as local host or even using its ip address, fails both ways, thought maybe it needs the agent installed, right click on the machine and clicked install agent but it fails even trying to do that, its a fresh install and yes already restarted so im basically trying to backup the backup server and its not working it cant access admin$ but i can access it when going via windows

Cybersecurity is a constant battle, and backups are a prime target. That's why I'm exploring how to integrate Palo Alto's Cortex solution with Veeam to further strengthen.Can you help me with these questions?What kind of integration exists between Cortex and Veeam? Is it a native integration or does it require additional components? What layers of protection does Cortex offer to my Veeam backups? Does it detect threats in real-time, analyze suspicious behavior, prevent ransomware attacks? How does backup scanning work with Cortex? Is it automatic? Can I customize scanning policies? What kind of threats does it detect? Can Cortex protect my backups both on-premise and in the cloud? Does the integration work with different cloud providers? What impact does Cortex have on the performance of my Veeam backups and restores? Should I consider additional resources?

Hi,I have a Windows 11 hyper-v need to backup VMs, but looks like this OS not supported? 

Hello Team,I have a question about snsapshots for ESXi and Proxmox.  I have taken some snapshots for some virtual machines.  The veeam backup can restore these snapshots?  As long as I remember, I got error with snapshots during restoring.  I deleted all of snapshots for ESXi virtual machines.Please let me know if I should not be included snapshots during taiking backup. Regards,

THERE IS NOW NATIVE FUNCTIONALITY TO DO THIS EASILY Greetings everyone, Audit Logging always is an interesting topic, it doesn’t matter if you need this due to compliance, or just for best practices. Having visibility of restore operations of something as critical as emails, documents, etc. should be a must.When I am mentioning the word Audit, I am talking about all the Restore operations that anybody does using the Explorers, PowerShell, or API, or even using the new Restore Portal (meaning opening an email, restoring it, saving it, etc.)As we stand today, we have the next methods to Audit the Restore Operations:Inside the Veeam Backup for Microsoft 365 Console, under History - Restore On Windows Logs, on the

According to @Rick Vanover , the Scale-out Backup Repository (SOBR) is a logical entity that groups several backup repositories called extents. This is a software way to pool storage for backup data management. I have written a detailed guide on my blog “how to Achieve 3-2-1 rule with SOBR on Synology or OOTBI and Wasabi”.We can implement the 3-2-1 backup rule via the SOBR. The 3-2-1 backup rule recommends having three copies of your data, stored on two different types of media, with one copy kept off-site. Here is a great post by Rick below as well.https://www.veeam.com/blog/321-backup-rule.htmlA scale-out backup repository is an architecture th

Recently, I’ve been creating videos to help others get started with Veeam Backup for Microsoft Azure. While I was working on the videos, things got meta because I realized I needed to update my own environment. That evening, I sat down to play Sims and needed to run game and mod updates. As I ran those updates, I thought about how I had just gone through a similar process earlier that day at work. So today I want to talk about software updates and share how to update Veeam Backup for Microsoft Azure, part of the Veeam Data Platform. Why Update?Even though I know they’re important, unmanaged software updates can be inconvenient, especially if you’re in the middle of something. As a general piece of advice, schedule software updates when they’re convenient to you rather than letting the software decide for you. Just remember that the longer you push off a software update, the more risks you run. In addition to missing features, outdated software is

 I recently helped a partner integrate their Veeam solution with Sophos so I thought I would provide some details and information around these processes.Sophos is a global cybersecurity company that provides a range of solutions to protect organizations from various digital threats. Their offerings include:Endpoint Protection: Safeguards individual devices such as computers and smartphones from malware, ransomware, and other threats. Network Security: Includes firewalls and intrusion prevention systems to protect network traffic and prevent unauthorized access. Cloud Security: Protects data and applications in cloud environments from security breaches and data loss.