Community

The new year starts very well...with a new problem in regards to Office 365 backup.Since 01/01/2022 teams backup could fail with the following error:Failed to process team: XYZ Organization (ID: XYZ) which the team (ID: XYZ) belongs to not found.Veeam is aware of this problem and currently preparing a hotfix for this issue. If you want to be among the first to receive the fix, then open a support case. If you can wait, I will update this post as soon as the fix is publicly available.For further information see the following R&D forums post:https://forums.veeam.com/veeam-backup-for-office-365-f47/o365-backups-fail-since-1-1-2022-01-00-t78479.html#p439853 Update #1:The Hotfix is now

Hello, I have a customer who has agents deployed using service provider console. They’re requesting to know what there compression ratio is for their backup jobs. Is there a way to pull this from Service Provider Console. 

Where do I see the warning logs? There are no errors but need correct warning messages.

Doc Veeam validatorKB2086: How to Use the Veeam Backup ValidatorVeeam Backup Validator - Veeam Backup Guide for vSphere It is essential to verify the status of the backups at the CRC level on the storage and the possibility of restoring them via Surebackup.During the wizard for creating a backup job you can enable "Storage backup files healt check (detect and auto-heals corruption.

Hi, We’re going to upgrade our vCenter to 8.0U1 and the process as far as we can tell involves creating a new vCenter with the same IP but different hostname (i.e. I can’t find an upgrade process that retains the same name for the vCenter). Just wondering what the impact of that name change would be to our existing Veeam backup jobs if they are all set to contact the vCenter on the old name. I’ve tried searching the community for “VCSA name change” and “vCenter name change” but have come up empty. Has no one else found this to be a problem? Or did we miss something and there is a way to retain the old vCenter hostname?

Morning, Just to copy this sentence directly from the latest “Word from Gostev”:“So I do expect the on-prem object storage adoption to go through the roof after V12 comes out with its support for backing up directly to object storage.” There’s been talk of it before, but it’s great to see this as near to a commitment from Veeam as possible, prior to seeing it in the final product. This will do wonders for efficiency and scalability, I’ll be interested to see how this changes the dynamic of ReFS/XFS volumes vs just deploying object storage. V12 is going to change the game!

Hi all,today I checked and solved a Veeam One issue during Veeam M365 data collection.This is the scenario:1 Veeam M365 in AWS cloud with its DNS_HOSTNAME 1 Veeam One customer on-premIn Task and Events tab I see the error:Fired by event: VeeamEventCollectionFailedEventEvent description: Failed to collect events data for object AWS_HOSTNAME. The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)Initiated by: Veeam ONE Monitor (ONESERVER-NAME)The RPC service is running on both hosts.From the ONE server I can ping the DNS_HOSTNAME and telnet on needed ports are ok (Firewall is ok).Why I’ve bolded DNS_Hostname?Because it’s different from AWS_HOSTNAME. This difference cannot permit to use RPC connection and start collection data.What’s my solution?Added 

Hello,I want to share with you the last script I make to get hardening configuration of the VBR server and then remediate some of them.The script need to be executed on the VBR server itself.It's built with Veeam 12.1 beta. That means some checks can break on GA version.I seperate it into 4 choices when you execute it :choice 1 = Apply Level 1 security (security check done by veeam product itself when you execute security and compliance on the VBR console)choice 2 = Apply Level 2 security (best practice about hardening Veeam product)choice 3 = Remove VBR console (Carreful, you can't use anymore Veeam powershell after this action)choice 4 = Get HTML security report That means choice 1 or 2 or 3 will performs modifications on the system.Choice 4 will not do any modifications, it just make the HTML report.

Continuing with my Linux theme this year, I thought I'd share how easy it is to implement Linux OS as Veeam Repositories in your environment. Instituting immutability with the Veeam Hardened Repository has certainly gained traction, and for good reason. There are several good posts out there on how to do so, including a couple of my favorites from @HannesK and Paolo Valsecchi here and here, respectively. But maybe you're not quite ready to go all in that route yet. Or maybe there's some organizational

I’m planning on making a better writeup with my settings and some photos, but for now this is on my mind after helping someone today.  I often see Veeam setups with 1 large datastore / volume in Windows for their repository. Other times quite often it will be multiple disks spanned into a single logical Volume, lets call it D:\. You can still get good performance like this, and the simplicity is quite nice, but can it be better? If you have some spare storage kicking around I encourage you to try this in your lab. Run your benchmarks on this single volume (D:\) record your results and then then delete the logical and physical volume. Create 3 new equal sized volumes with matching logical volumes. Lets call them E:\ F:\ and G:\. Next run IOMeter or your favorite benchmarking tool.  Make sure you are pushing the queues to see the benefits of multiple physical/logical volumes.  The next thing you can do is check and modify queue d

Hi, built a new home server just in time to test the new 12.1 Community Edition.  Everything seems to work fine except I can’t seem to create a usb recovery stick.  When I click on Recovery Media, I get an error message that says “Cannot find backup file for <Server Name>”. I’ve created a backup on this server and it finished successfully.  Anyone else run into this issue?Thanks!

I’m happy to announce that the storage report script, by @Jim Jones, has been updated for Veeam Service Provider Console v8 and is now available on VeeamHub.This script will return usage and metadata for all backup repositories for the specified VSPC server. It will also provide the name and UID of the provider/reseller/company to whom the repository belongs.Be on the lookout for the BackupSizeGB metric which was added in Veeam Service Provider Console v8. This metric is the total size of all restore points and is a useful chargeback metric for service providers.On top of that, this report could be used by operations to see the current status of all backup repositories in their environment.For more detailed information, please follow the Veea

Hi, I'm a new user trying the Veeam Backup and Replication Community Edition v12.1 for the first time. I’ve installed Veeam on a Windows 10 computer, and was able to make a backup of all the drives from a client computer also running Windows 10. But when I tried to restore a file from the backup, I got the error message shown below. I am initiating the restore via the Veeam console running on the same computer as the Veeam Backup and Replication Community Edition. Restore failed Error: Neither Installer service nor Admin$ file share are available Does anyone have an idea on how to fix this?

Hello Everyone,If the backup at SP is deleted, it should go to recycle bin, however restoration options is to restore it backup or copy it to removable disk to the tenent without meta data. how could copy it to removable disk and restore it without meta data? 

VeeaMover is a cool new feature available in the next Veeam Backup & Replication v12 that allows to move or copy backups to different locations.If you need to change the target repository for a Backup Job containing existing backups, a warning message is displayed and the procedure cannot be finalized until the backups have moved to the new repository.With current versions of Veeam this is a manual, time-consuming operation. Here is where VeeaMover come into play. Use casesCommon VeeaMover use cases are the following:

In the ever-evolving landscape of information technology, the safeguarding of critical data remains paramount. Among the crucial elements ensuring data integrity and recovery, versioning and retention policies stand tall, forming the bedrock of robust data protection solutions. This article, "Versioning and Retention Policies," aims to delve deep into these foundational components, offering insights and strategies crucial for IT experts aiming to build comprehensive data protection frameworks.Understanding the Essence of Versioning in Data BackupsAt the heart of any effective backup strategy lies versioning—a mechanism that enables the preservation of multiple iterations of data over time. The importance of versioning cannot be overstated; it serves as a safeguard against data corruption, accidental deletions, and the ever-looming threat of cyberattacks.Data Recovery and Resilience Versioning within backups se

Hey! There are many new features in the Veeam Data Platform 23H2 release. Discover some of them in the video below and at the following links: https://www.veeam.com/whats-new-backup-replication.htmlhttps://www.veeam.com/veeam_backup_12_1_whats_new_wn.pdfhttps://www.veeam.com/veeam_console_8_0_whats_new_wn.pdf Download the trial version here:

Hi, is it possible to backup an entire disk or clone a disk?  I would like to make a duplicate copy of my boot drive.  Thank you.

So I have an issue. We backup to disk (a Data Domain, in our case), and from there, copy to tape. So I have 2 jobs - a backup job that writes to the DD, and a tape job (set as secondary target). Backup job is set to make an active full once a week (usually on a Friday), and the other days are incrementals. Pretty standard so far.My issue: on the weekend, we ran out of blank tapes in the library. I had to cancel the running tape job (which was trying to write out the Friday FULL backup). I got some new blanks, and loaded them. But the Monday tape job went to write out the (missed) Friday FULL backup, instead of just doing the Monday incremental. The FULL job is like 4 TB, no way it will finish in time before the next night’s incremental backup will start up. I had to change the scheduled start to “Not scheduled”, just so it would have enough time to finish (else it would have been interrupted by that evening’s incremental job). I don’t want to hold the source backup job

HelloFor testing Inmutable backups using ubunto server LTS 22.04.3 followingPart 1 - Build an immutable backup repository for Veeam Backup & Replication. | Experts Exchange (experts-exchange.com)Great expirience and working very fine on some spare PCs i had lying around.(doing bare Metal recoverys and testing different storage medias from internal HDD to usb 3.x to iscsi)  Now i tryed to replicate it on a Rasbery Pie 4 but when i try to add it as a Hardened respository  in Veeam i get:Only x86_64 (64 bit) Linux servers are suportend. lscpu shows 32bit, 64 bit and i used a 64 bit LTS version. Now im not the firmest on Linux so mayhaps im overlooking something trivial. Anyone got an idia? Sascha Wagner

Hi Everyone, As always after a move I was going through old stuff and found my lucky winner post from 2017. At the time on the Veeam Forums there was a contest to win a trip to VeeamON 2017 in New Orleans.. I was not sure whether to post or not. Fear of being laughed at or ridiculed was strong, but luckily I had managed to make a fool of myself so often during my schooling years the phobia had somewhat lessened! In short folks don’t be shy and get creative! You never know where it may get you.Here is the poem that I wrote about Veeam: A good morning starts with coffee and creamwhile viewing a backup report that is colored in green.There was a time when nothing of the sort would be seenThose were the bad old backup days before the arrival of VeeamBroken restores will break an Admin's spleenBut by using Veeam one's health remains keenNo backup operator wants to face an angry user who turns meanInst

If I’m reading the docs correctly, Object Storages (Direct or SOBR) use one Task per backup chain.These backups create MANY files.  It looks like I can limit the maximum concurrent Tasks for an S3 compatible backup, essentially limiting the number of concurrent backups.I am, however, interested in increasing the speed of one very large backup.  I see many small objects are created.  At least in the case of SOBR, I assume that the data has already been deduped and compressed, and that and some sort of Task parallelism is happening during offloading.  Is this correct, and is there any way to increase the parallelism or number of Tasks used during

In case anyone missed it back on December 7th I was on the Ninja Pod podcast with @DrObject talking all things Veeam related as well as discussing my book.  You can catch it below.  

What and why?The Veeam Hardened Repo (VHR) is definitely in my top 10 list of product features. However, as with any IT system, having it in place means that it needs to be maintained. Veeam's own components are maintained by Veeam during patches or upgrades. With the initial release of 12.1, updating a VHR is still a partly manual task. You will need to enable SSH to do this. Cumulative Update 1 to 12.1 should allow us to update the Veeam services without having to enable SSH: https://forums.veeam.com/veeam-backup-replication-f2/upgrade-of-vbr-to-12-1-with-hardened-repo-t91251.htmlBut there is more to it than that! The Linux underneath also needs to be maintained. Update your Linux underneathFor example, as Ubuntu is one of the recommended distributions to use with a V

In the realm of IT infrastructure and data management, the terms "replication" and "backup" are often used interchangeably, leading to misconceptions about their functionalities. While both processes involve duplicating data, they serve distinct purposes in safeguarding data integrity and availability. Understanding the fundamental disparities between data replication and backup is pivotal for designing a robust data protection strategy. The Essence of ReplicationReplication primarily focuses on mirroring data from one location or system to another in real-time or near-real-time. It ensures data consistency across different environments, enabling high availability and disaster recovery. The goal of replication is to maintain synchronized copies of data to facilitate continuous operations and minimize downtime in case of hardware failure or site disasters.The synchronicity of replication is also its biggest weak point – all errors i