Community

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!!

So I’m am basically a day or two away from taking the time and going through and disabling the backup cache across all of my customers, it causes way too many problems. But thought I’d try asking here as a last resort since Veeam’s support seems useless as usual and my R&D forum posts aren’t getting any responses. I have had various cache related issues, especially since the ridiculously buggy V12 update, but here this past week it’s been especially bad. I have about 20 computers, that I know of right now, which are failing to upload the backup cache to the VCC server. As such these computers have not been backing up. At first I thought maybe they just needed some time to catch up or something, but it’s been over a week now and they’re not even modifying the files in the VCC repository. (Side note, yes, I did go look at the files, because it’s useful, even though Veeam says there’s no reason I should ever need to look at the files.)Seems there’s numerous

veeam agent for linux run very slow on ubuntu 22.04 ltsbackup client is running virtual on virtualbox linux hostbackup client has installed zammad and elastcsearch      Duration:           13:13:00         Processed:          12.2 GB (100%)     Processing rate:    311.6 KB/s       Read:               12.2 GB     Bottleneck:         Target           Transferred:        3.2 GB (3.9x)      Time             Action                                  Duration      16:30:05         Starting full backup to Repository_1               ↑      16:30:05         Active full is forced                              │      16:30:07         Backing up BIOS bootloader on /dev/sda  00:00:51   │      16:30:58         Backed up sda 12.2 GB at 270.6 KB/s     13:10:36   │      05:41:34 (+1)    Backing up summary.xml                  00:00:30   │      05:42:07 (+1)    Releasing snapshot                      00:00:01   ▒

Hello Team, Can anyone help, am trying to upgrade VeeamOne env from 12.0.0.2498 to VeeamONE_12.0.1.2591_20230314, am unable to upgrade as it shows license is invalid. Could you please help path to download trial license for VeeamONE_12.0.1.2591_20230314.  

for a customer I have Veeam 12 installed and as primary Repository an Ubuntu Server with the possibility to configure immutability, as secondary I have a Gen4 HPE StoreOnce with also the possibility to configure immutability, where do you advise me to make immutability backups, on the Primary or Secondary Repository or on both ? (the two Repositories are in two different locations)

Hello, Thanks,For the linux hardened repository, Windows Agent Backups (volume and file) complete successfully.However, Hyper-V fails.Windows.Server.DataCenter.Evaluation.Edition.2022.21H2VBR server - 12.0.0.1420 P20230178The backup repository is linux hardened, located over the internet, not local.Note: for this linux machine, I made sure ping from repo -> VBR work ;winkThe backup repository location is a mounted SMB share.Given the error is `Failed to make the backup file immutable: Inappropriate ioctl for device`,my small brain thinks ALL immutable backups would fail, not just Hyper-V?Please advise? Queued for processing at 11/5/2023 12:25:15 PM  Required backup infrastructure resources have been assigned  VM processing started at 11/5/2023 12:25:20 PM  VM size: 127 GB (5.4 GB used)  VM is now in the requi

As announced in VeeamON 2023, the release 12a (or 12.1) of the Veeam Data Platform is coming soon. In addition to bringing new cybersecurity features, one of the focuses is improving the ability to protect data stored in Object Storage.It is a critical demand for organizations to store data related to modern applications or any unstructured data related to the business.It will be possible to take data from object storage and store it in backup repositories of any type: block, file, object storage, or even tape.There will be flexible recoveries in restoring the entire buckets, including permissions, attributes, and tags.

I’m using VEEAM 12.0.0.1420.I’ve created a backup on a RDX drive with the option ‘This repository is backed by rotated drives’.Then i created a bootable recovery media → USB stickStarting machine from USB stick and open wizard ‘Volume Level Restore’Backup location is fine, full backupStarting progress will show the following lines:OK Loading backup filesOK Restore process started …BAD Restore failed: The requested security package does not existBAD Saving restore logs Error: Unable to save recovery logs to target repository. To do …Please advise.THX Reinhard

Hi all.reference Upgrading Veeam Service Provider Console - Veeam Service Provider Console Deployment GuideI share the procedure step by step for upgrading VSPC v6 to v7.Backup database before proceeding. Backup of the VM dedicated to the VSPC service before proceeding. Cold snapshot of the VM VSCP if there is database Download ISOCheck your versiontip:

Hello, I have a small vm, 5.4GiB in size.Non-instant restore works fine, after restore completes, can boot into the vm and use it.Whereas, instant restore fails, can boot into vm but it, not able to use it.Host:windows.server.datacenter.evaluation.edition.2022.21H2VBAR server - 12.0.0.1420 P20230178The repository is linux non-hardened, located over the internet, not local.Looks like instant restore creates the required files including the .vhdxLooks correct from hyperv manager.but the vm will not boot correctly [ 6903075986]  /├── [ 1086624914]  gparted│   ├── [    4292475]  Snapshots│   │   ├── [          0]  31D5C4AB-9443-43F4-8088-740728378880│   │   ├── [      45092]  31D5C4AB-9443-43F4-8088-740728378880.VMRS│   │   ├── [      52567]  31D5C4AB-9443-43F4-8088-740728378880.vmcx│   │   └── [    4194816]  31D5C4AB-9443-43F4-8088-740728378880.vmgs│   └── [ 1082332439]  Vi

Helloour NAS had a problem and the content was wipe out.  So I need to start over with the first full backup.What should be the correct actions to be done? I did a new full backup with success but the Veeam database still show old entries (and I understand that) need you advise thanks

 And the Veeam 100 Summit 2023 has now come to a close. I myself made it home yesterday, and I know others have stayed on a bit longer but the numbers are starting to dwindle as this becomes just a fond memory.For my final piece of Veeam 100 content here, I want to share with you the heart of what makes this event such a success. The people! And I welcome the other Veeam 100 attendees to share any green content photos and stories!For me, whether it’s been getting lost in the beautiful architecture of Prague, or having a cheeky pint after hours, the friends I’ve shared it with have made it unforgettable!Photobooth FunThe Vanny Pa

Hi, I’m trying to back up a VM running on a standalone ESXi v8 host using Veeam B&R v12 Community edition.  When I set the job up it ran successfully but all subsequent (scheduled) backups fail with “Failed to create processing task for VM Sophos Firewall Error: No proxy available”.If I edit the job without changing anything (just applying the same settings) it will run.  Also, if I do the same with the VMWare Proxy object or the veeam server object (in Backup Infrastructure > Managed Servers) it will also run.  In all cases it will only run the first time after applying the settings. Again, all subsequent runs fail.The veeam ‘server’ is an i3 8GB Windows 10 22H2 x64 PC.  What looks to be the root cause is an entry in the job backup log that says:[ProxyDetector] VMware host API version is V800. Skipping not x64 proxies[ProxyDetector] VMware host API version is V800 and all available proxies are not x64 so we can not use it with

Hello, at my home lab, i have a home server running VBAR community edition with the BR(Backup Repository) on the same windows server.I have a storagebox account with hetzner, which allows smb over internet.I have created a BR using that smb share and it works great.Not sure if I am violating the community license?and that bring up another issue, I could rent a cheap vm from hetzner and install a linux hardened repository?

Hello I would like to know if the Veeam installation process enable xp_cmdshell under MSSQL

 Hey! Microsoft SQL Server backends some of the organizations' most critical applications. Any loss of data or even the inability to fully recover this environment can cause catastrophic damage to the business.Veeam offers several options to simultaneously protect the most business-critical applications and Microsoft SQL Server environments.Starting with version 12 of Veeam Backup & Replication, the Veeam Plug-in for Microsoft SQL Server was made available.This pl

Hello,One of our customers uses VBRv12 on premise with Azure an Repository. They have about 2TB of data backed up locally and via backup copy jobs to an Azure Blob Repo.We were very baffled to notice that at the end of the month, the cost with transactions was matching the cost of the storage.I am looking for an advice on how to optimize the number of transactions other then reducing backup frequency.For a fact we checked his environment and he has 1server per job and 1 backup copy job per production job. I wonder if aggregating all in a single backup copy job towards Azure would address maybe this issue?We are also testing this scenario but to be relevant we need to run it for at least on week so if anyone ran into this please let me know.

We start the day with @kirststoner12, Roman Kuksov, and @jorge.delacruz   First up is Jorge talking us through the Veeam ONE Threat centre.Jorge talks us through the data platform scorecard, made up of the following four contributing components:Platform Security Compliance - This is driven by the VBR Security & Compliance Analyser (Formerly known as the best practice analyser) Data Recovery Health - This score looks at backups marked as suspicious/infected, you should hopefully see a 100% health when you first deploy this Data Protection Status - This score is based on the percentage of protected workloads vs unprotected Backup Immutability Status - This score is based on the number of workloads

hi team,hope everyone’s ok. just wanted to ask and get some ideas/suggestions regarding retention policy on a backup copy job.first of all, i have on-site a Qnap for local backups and on a remote site another one for copy jobs. local backups have their own retention policy while on remote i have different ones.from my understanding, backup copy works with forever forward incremental backups and when the retention policy kicks in, i get a full backup of the backup job.so my question is: shall i add on the retention policy i have set on each backup copy job the “keep certain full backups longer for archival purposes” with a different duration?many thanks

Not really a Question, just sharing and curious if anyone else has thoughts on it. In my experience Veeam’s Support asks for incredibly excessive data, asking for the same logs over and over, asking for logs that don’t seem at all related, and asking for copies of databases on VBR servers.Some other people have shared privacy concerns with me about the behavior. Personally, I’m not fond of it, but accept it as a cost of using Veeam. From my perspective none of this should be necessary if the software itself was:A, less buggy to begin with.B, had actual useful error messages so I could tell what the problem was without involving support.C, had actual useful error messages so that Veeam’s support could tell what was wrong.Noting B and C are different because I can accept that Veeam’s support may know more than me about what an error message means. Though if B and C are different, then it’s a good time for me to mention

Good day Community -With Linux being more prevalant in environments, including Veeam supporting Linux within its deployment components, it is a bit cumbersome to manage all these devices individually. So my question for the Community today is → what centralized management tool(s) do you use to manage your Linux server footprint?..to update, push scripts, monitor, etc? I’m needing to update & even push a script (change) out to our Linux servers and don’t want to touch all of them individually. Any info you can provide is greatly appreciated.I did a little bit of searching before posting and saw a tool called Landscape which looks promising, but don’t know anything about it & open to hear anyone’s experience with it...or again..any tool. Thanks in advance!

Today kicks off with another all-star cast! @Julia F Morgado, Lyudmila, Vitaly, and Alec all on stage to talk the shared features of all Veeam Backup for Public Cloud, and individual product updates! Shared FeaturesFirst up, we’ll see Veeam enabling us to leverage more granular permissions for service accounts, with a built-in validation check to confirm the permissions are assigned.We’ll also see updates to the workers, with the ability to assign tags automatically to all worker nodes for their lifecycle.The biggest announcement from this however is that we’re going to see future Veeam Backup for Public Cloud updates only become available to Veeam Backup for Public Cloud instances integrated into Veeam Backup & Replication. This will make the Veeam Backup for Publ

Hello, I am looking for a method or script to run backup jobs on a custom schedule.The built-in scheduler seems very basic, and as a result, I have to run all jobs as incremental and then manually trigger a full every two weeks.I have searched the veeam scripts and forum, could not find an solution.so does anyone have a script or technique to run backups on a custom schedule?perhaps using windows task scheduler, powershell, python or any such way?Thanks much,David

Dear Support,    We have encountered a backup problem and cannot perform any backup operation at present. Please see the attachment for details. Could you please help us?