Community

Forgive me for this new discussion and please do delete if it is not the right place to ask. I am trying to do a bit of studying around my job currently and wanted to clarify a few points with Veeam (in the process of doing a small course). I'm getting very confused with the differences between forward incremental and reverse incremental backups and wondered if you could clarify.  Am i correct in thinking when choosing forever forward incremental backup, that if there is no synthetic backup scheduled, then the first full backup is completed followed by incremental the days thereafter. Therefore, if you wanted to complete a full restore, you would need to restore that original full backup followed by every single incremental up to the date of the full restore?And if a full backup is done, the retention period is approx 6 months and there are no synthetic backups scheduled.. then if there is a day mid way through that the backup job fails, then this runs the risk o

Hello,Regarding Forever Forward backups, is it necessary to create period full backups (either Active or Synthentic), or can you just go with the initial full backup and everything else is incremental? (I know it is probably at least RECOMMENDED to do periodic full backups, but let’s not worry about that for purposes of this post/question) If you were to go with just the initial full backup then leave the rest as incrementals, what happens if you have a corrupt/failed incremental backup in the chain, but need to do a restore of a file?  Is Veeam able (and smart enough) to work around it? (i.e., if it has a failed or corrupt incremental backup, is Veeam smart enough to start the next backup based on the last good incremental and basically ignore the failed/corrupt one?) Thanks! :-)

hello, i would like to know, if I create CDP Policy on my veeam server, with RPO 10 Minutes, Short-term 36 Hours and long-term 24 Hours keep for 7 days. so it means that i will have  216 restore for short-term, with one full and rest are incremental and for the long-term, i will have 7 incremental.is it right ? 

Build: 12.0.0.1420 We are unable to run a restore from a backup due to this error message.  Restore type: Windows guest file restore.  VM size is about 5TB.   

We have an onpremise Veeam server that runs the following jobs:1. Backup to local storage (weekly full, daily incrementals)2. Copy job to Linux hardened repository (immutable)3. Copy job to Azure Blob cool storage (immutable)Now i would like to have the Azure monthly backups moved to archive tier. I'm assuming i have to use SOBR for this. The following question arise:i create a second immutable repository with longer immutability, say 1 year. After moving the full backup, will it calculate ‘initial backup date + 1 year’, or ‘SOBR copy date + 1 year’? do i need a new container for this or can i just create a folder within a container? if a backup is still immutable can it be moved to the archive tier? copying backups obviously generates a large amount of traffic. Download backup from one repository, upload to another. Is there something i can do to limit the amount of traffic and costs? what's the ris

Hi there.Need to review my backup configuration after adding a linux immutable box and a 10 TB vcc cloud space. 20 vms ( 15 windows server and 5 linux ). About 6 TB storage space (compressed). One backup a day at night. veeam server is a physical windows 2022 server box with local storage. Here is my idea:First backup job on the veeam server itself. Backup copy on a scale out repository based on the local linux immutable storage and vcc cloud storage.Any suggestion?thanks in advance,Max ( Italy)

hi, I would like to know that, can we directly restore to on-prem from S3 glacier (archiving tier) using SOBR ? 

Is there a way to replicate VMware virtual machines to Azure?

hi, I have veeam server with perpetual enterprise socket base on VM and I would like to migrate my veeam server from VM to bare metal, so can I still use my perpetual enterprise socket base ?

Hi, I was working with older version of veeam long ago and I remember I never had any issues with it, currently I am trying to set a backup and restore solution and I’m evaluating veeam with our Ovirt Node 4.5.4 infrastructure.I did the setup step by step and later installed the RHV plugin and connected to the engine and got the proxy vm up and running I can setup backup jobs and all is good until this point, I do get a warning during backup but it finishes anyway, here is the error I get :{VM-Name}: Image transfer URL is inaccessible: CURL error 6: Couldn't resolve host name, switching to the proxy URLI tried to restore an VM and I am now getting this error and task fails:10/18/2023 2:18:16 PM Error    {VM-Name}: Unable to write data block. Offset=0, Size=1048576 : CURL error 6: Couldn't resolve host name10/18/2023 2:18:12 PM Error    {VM-Name}: Data transfer error10/18/2023 2:18:12 PM Error    {VM-Name}: Unable to w

Many of you saw the hotfix that came out for Veeam ONE that takes care of some pretty high CVEs (yesterday).I checked with Support on my custom hotfixes and was given the go ahead to do the hotfix.  So I implemented it this morning and now I am running in to problems with the data collection and a persistent warning message -11/7/2023 1:00:04 PM [warning]: servername: Method not found: 'System.String Veeam.Reporter.GrpcService.GrpcServices.GrpcAuthInterceptor.get_CurrentAccessJwt()'.This is an example of one line but happening for all my VBK/VEM servers added in Veeam ONE.I am working through with Support on my case for data collection to see if I need to revert the hotfix for now to allow RnD time to fix the hotfix.  😋

Morning all. Hoping someone can help identify the best method available to us for migrating to new hardware. Overview of current setup:All in one VBR server (physical)  Currently on v11 Local storage (ReFS volume)  SOBR using Wasabi S3 for the capacity extent. Backups are copied to capacity.  1 job (agent managed) backing up 7 physical servers at remote sitesOverview of new setup:All in one VBR server (physical)  Fresh install of v12 Local storage (ReFS volume)How would we best approach moving the data/job from the current setup to the new setup? The approach needs to consider the following: Ideally, we want to use VeeaMover in v12 to move the data between current and new setup so that we maintain the ReFS block cloning savings.  The storage from the new system cannot be directly attached to the current system, b

We are planning to replicate from DC to DR. which ports need to be open for this? we just replicate and recover from replication we also plane deploy the Backup proxy at DR. Thanks 

Hi, my customer has centOS 8 installed on bare metal, i have already installed agent on centOS8 but it showed not supported. any solution ? 

hi veeam communityI want to turn on the firewall of the backup server and configure the firewallI have veeam backup and enterprise manager on my serverThe servers that are backed up are mostly on hyper-v cluster.There are several physical servers, including SQL Server, which is also a cluster.My question is how can I do this very accurately and professionallyIs there a tool for this?How can I test whether I have considered all the desired ports or not?Thank you for sharing all your experiences with me 

I have a Hyper-V VM in TN. Our VBR is in TX. I set the backup job for said Hyper-V VM to use on-host proxy and store data to a repo local to the Hyper-V VM in TN.  Started the job ~1940 CST and let it run, it was stuck on 50% completion, and stuck on hard disk 1 processing (like below) for almost two hours. I ended up stopping the job, not gracefully, but immediately. 7:41:16 PM    Hard disk 1 (931 GB) 1024 KB read at 1 MB/s    01:49:24 I’m using an NFR to test this because we have a Hyper-V VM in TN that we want to bring to TX but to VMware using Instant Recovery (Instant Recovery to VMware vSphere - User Guide for VMware vSphere (veeam.com)) I was directed here for possible help. I have logs here h

As of now I know that Veeam VBR is not supported the Cluster solutions.Is there any plan for Veeam VBR clustering in future any body know that?Couple of my client asking for Veeam VBR cluster solution,

Hi all, I’m working to understand more about question in object. In specific I start from @regnor blog using StoreOnce. If I set an immutability ends in 3 years but a customer want to exit from this service after 2 years what are the correct ways to remove all backup data after export? I know good start is to have xx days (30?) for immutability but if customer wants GFS policy up to 3 years immutable how can I operate? I know this is a MSP based question for this I hope someone can help me.Thanks.   

Can we please have an option to export the configuration of a VBR VLAB. And create a VLAB from this export? Too many times the VLAB gets broken and support just states recreate the VLAB but its like 50kazillions configuration option to reconfigure. I have 6 VBR VLABs to manage and its rough keeping up with this.  

Worked with 5 different Veeam support resources and implementation specialist with my problem. DRO backup testing restores to a stack and creates mass migrations because of vCenters DRS. Tried forcing it to use the required VLAB and its reservation that VBR restore test uses. But for some reason ive been told DRO was designed to not use this existing VLAB reservation. Can this be implemented? 

Hello all,I'm doing backup of client Windows 2022 Standard. Active full backup failed on similar error but different file. Then incremental backup failed as is listed below.my OS backup failing all the time by error message:2/18/2024 8:03:09 PM :: Current file C:\Windows\System32\d3dxof.dll and backed up file D3DSCache.dll are different  2/18/2024 8:04:52 PM :: Task C:\Windows\System32\d3dxof.dll failed: Current file C:\Windows\System32\d3dxof.dll and backed up file D3DSCache.dll are different  2/18/2024 8:04:54 PM :: Incremental backup: Current file C:\Windows\System32\d3dxof.dll and backed up file D3DSCache.dll are different   VSS on server is enabled and working properly when I did backup over OSin my log I see only:[17.02.2024 11:42:16.547]

Why Veeam isnt’t able to use the whole capacity of LTO-tapes? E.g.: Why can't Veeam write a new mediaset to the end of another mediaset?Tapes are in the same mediapool. Mediapool setting “Do not create, always continue using current media set” ist active. If i edit some settings on Backup-To-Tape-Job, a new MediaSet-Name is setting. On next run of this job veeam uses a new fresh tape, although the last tape still has enough storage capacity.I’ve got LTO-7 Tapes (12TB mx. capacity). Veeam uses, for example, only 2TB of capacity in case of doubt.

My company have 20 servers location in 4 different locations (Hong Kong, Shanghai, Beijing, Guangzhou), I would like to know how many license pack I needed to purchase for these 20 instances?

Hello,we are just some newbies in Veeam and have following problem.The Veeam Linux Agent 12.1 is correctly installed on an Oracle Linux Machine i have tried both methods, manually and per install service from Veeam Backup and Replication Server, the installation were completed with DKMS and build step what is workig very well. If i try to make ab backup of the machine i receive errors in Serverlog as follows:creating volume snapshot;thanFailed to take snapshot;Broken Pipe;Failed to write data into pipe.the linux log:[29.01.2024 08:01:29.072] vmb | [SessionLog][processing] Creating volume snapshot.[29.01.2024 08:01:29.073] lpbcore | Polling request: [job][UpdateManagedJobXmlLog][29.01.2024 08:01:29.780] lpbcore | Polling request: [job][UpdateManagedJobXmlLog][29.01.2024 08:01:29.780] lpbcore | Created snapshot [b9e92c64-5562-479d-8e2a-625ead940a8f][29.01.2024 08:01:29.783] lpbcore | Finish ora

HI,    A backup job failed since the windows-host been reinstalled. Here is the error message: Cannot connect to 192.168.1.11 Details: The network path was not found. The network path was not found. (ERROR_BAD_NETPATH).The default share of ADMIN$ has been set, and the port 445 is open.Shoud I clear all of the setting and data-file of the host ?What is worng?  Thanks a lot!