Community

This is the description of an unusual scenario where Backup Job Files (.vbk and .vib Files) are backed up with a File-to-Tape Job instead a Backup-to-Tape Job. This has several disadvantages, e.g., you must know on which tape your files you want to restore are residing. You cannot find your tape backups under the backups section in the “Home” view of console and many more…OK, now have a look how we get these files back from tape.See the results of the File-to-Tape job and find the tape number the files reside on. If you don’t know the tape, read further, and use the search function ( Note: the warning in the screenshot can be ignored. The filesystem is too big for VSS Snapshots, I have forgotten to switch the VSS snapshots off for this test backup job.).Then go in the Veeam Console to the “Tape Infrastructure” section. Either go to the media pool where the affected tape is in or look for it in the Media section of your tape library.Right click on the tape and select “Restore Content”.

SPOILER Warning if you’re awaiting your swag, don’t watch the video!I was lucky enough to be selected as a Veeam Legend this year and luckier still to be one of the first to receive the swag by the amazing @Kseniya & @Rick Vanover  (and of course Alfred).Check out my unboxing video below to see all the goodies  If you’re still on the fence about the Veeam Legend programme, it’s been an amazing experience so far, I whole heartedly recommend it!

Hey Everyone, As I understand it Veeam is fully vMotion aware. That includes storage vMotion. So if someone storage vMotions a VM the replication job should not have any issues? However, if someone moves the replica to a different datastore, based on @MicoolPaul best answer then you would need to remove from the configuration database and seed and  map in the replication jobs to the replicas on the new location.  

Hi Veeam,We are taking oracle database backup through Application-Aware backup job in Veeam.It happing seccessfully. Now, we are trying to restore Oracle database to another server (Same OS and Oracle version installed). But it showing some error that “Failed to get database files from mounted backup”.Please help me on this. I dont know how to mount backup in Veeam.Thanks.The error snapshot is showing blow.  

Phenomenal Strategy to Defend the Ransomware Attacks and Protect Data from Cyber Attacks is the Flagship Feature of Veeam VeeamON Forum back to India! Take part in an action-packed experience with hours of technical content that will help you adapt and thrive in today’s challenging IT landscape. Explore Key Topics The most awaited and passionately curious to see how Veeam is addressing the complex, everchanging issues of the modern IT landscape with cutting-edge solutions that will help you go above and beyond in your Modern Data Protection strategy. New V12 Ransomware Kubernetes AWS/Azure/Google Microsoft 365 For more details logon to Transform your Modern Data Protection strategy (veeam.com)

I’m trying to do Instant Recovery of a large server from a VeeamSourceSnapshot to a different volume. There is no option of doing this, what’s the workaround? We are using NetApp and it has a 100TB limitation on the volume size so this is the reason why I would like to restore to a volume that has more free space. Appreciate your input!

Hello How to Install VBR v12 to remote SQL with customized port instead of 1433?

Check out our introduction to Containers, Kubernetes and Kasten K10. Look after your pets (services) and ensure fast recovery times.Introduction to Containers and Kasten - Veeam looking after your animals (services) Part 2 -  Vets for your pets - Speedy Recovery of your pets (key containerised services) coming soon!

Hi,I have been facing an issue while trying to login with Veeam Backup & Replicaiton v10.  The error is “failed to connect to Veeam Backup & Replicaiton server: No connection could be made because the target machine actively refused it 127.0.0.1:9392. Application Event log : Service cannot be started. System.OperationCanceledException: The operation was canceled.   at Veeam.Backup.DBCreator.BackupDatabaseDeployer.CanDeploy(IDatabaseVersion databaseVersion)   at Veeam.Backup.DBCreator.BackupDatabaseDeployer.DatabaseDeploy(List`1 inDeployChangedOptions)   at Veeam.Backup.DBCreator.BackupDatabaseDeployer.Deploy()   at Veeam.Backup.DBManager.SqlRetryableInitializer.Init()   at Veeam.Backup.Service.CVbServiceImpl..ctor(CVbEnvironment env, CTerminationMediator terminator)   at Veeam.Backup.Service.CVeeamBackupSvc.OnStart(String[] args)   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state) Please support anyone to resolve issue!  Regards,

I am looking for recommendation on how to design a server that can run VBR and that can be a storage repository for critical VMs. I am thinking about using this new server for instant restores or other Veeam tools that can bring a work load up quickly. This server would have high speed storage to improve the performance of the restores.  Currently I run VBR on the VMware cluster that I am backing up and I want to move VBR to stand-alone server that would stay up if the VMware cluster went down.  We currently use a Linux server with spinning disks and immutable storage as our primary backup target.  Thank you for your suggestions and recommendations.  

Hello All, Could someone help me with adding servers to agent-based backup jobs via powershell/commandline. In the below command i get error while mentioning Job  and backupobject.Set-VBRComputerBackupJob -Job <VBRComputerBackupJob> [-Name <string>] [-Description <string>] [-BackupObject <Object[]>]. Where RKTest is an existing Job, I’m trying to add objects or servers to the backup job RKTest.  Error:cmdlet Set-VBRComputerBackupJob at command pipeline position 1Supply values for the following parameters:Job: "RKTest"Set-VBRComputerBackupJob : Cannot bind parameter 'Job'. Cannot convert the ""RKTest"" value of type "System.String" to type "Veeam.Backup.PowerShell.Infos.VBRComputerBackupJob".At line:1 char:1+ set-vbrcomputerbackupjob+ ~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : InvalidArgument: (:) [Set-VBRComputerBackupJob], ParameterBindingException    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Veeam.Backup.PowerShell.Cmdlets.SetVBRCompu

Hi Veeam communityI would like to hear your thoughts about pros and cons regarding GFS and Standard Mediapools.

Hi Veeam Community,I have just started in a new company and was going through their Veeam backups solution, and here I found that the consultant company had 2 backup jobs running at the same time against all servers - 1 to the harded repo. and 1 to a cloud repo. (7 days immutability. My question goes on - what would be the best practice:2 Backup jobs of all servers ( 1 to local repository and 1 to Cloud repository)   1 Backup job of all servers to local repository and then setup a Scale-Oout Repository to move the backup onto a cloud provider.  Just wanted to know your opinion before I go in dialog with the consultant.Looking forward to hear your recommendation… /Peter

Hi! In this video, I show how to install Veeam Backup for Google Cloud and integrate it with Google Cloud Plug-In for Veeam Backup & Replication. I hope it's helpful. 

Ran across an interesting quick issue post v12 upgrade.  I had a client who I upgraded to v12 (via our Service Provider Console).  I had some clients where after the upgrade, some copy jobs were not reenabled.  NOTE:  The upgrade shows as a success, but if you view the upgrade job details, it does note that the jobs weren’t reenabled.  Anyhow, I was poking that clients machine this morning and realized the copy jobs were disabled but also decided to convert them from per-job chains to per-machine chains.  I changed the backup repositories to per-machine, but when I attempted to detach the backup job from the restore points, I received the below error message. Veeam error dialog stating “Disable the primary job and all dependent secondary jobs before detaching the backup.” The strange part about this was that I had already disabled the backup jobs, and the secondary copy jobs were already disabled.  Thinking that perhaps it was tied to the replication jobs (metadata), I tried disabling

In this demo I illustrate how you too can utilize the Pure Storage platform to provide rapid recovery and near-zero replication for your Veeam repositories.This lab consists of 2 Pure arrays, 2 vSphere clusters and a single VCenter. Though in this lab we could use other means to provide recovery, say through vSphere, this setup up was used to simply illustrate an easy to use and efficient DR strategy from Production to a DR cluster. Utilizing, Veeam.In this lab I built 2 Veeam servers. The first holds the Veeam Backup Server, proxy, and primary repository. The second runs the Veeam Disaster Recovery (VDRO) server and is the remote repository. In this lab – I do not utilize VDRO for recovery – that will come in a later post.Normally, in a Veeam scenario like this there would be 2 Veeam jobs providing restores and the local and remote sites. The first would be the primary backup job to the repository local to the production site. The second, would be what is called a backup copy job from

I have been thinking a little more about how best customers can best utilize their technology to build in fool-proof data protection. Data protection which helps eliminates risk normally associated with managing a data protection solution.I have spent a long time dealing in this space, and I have found, that it’s common for organizations to put data protection solutions on the back burner. Utilizing cheaper, and sometimes older technology that lacks features and tools that reduce management risks. Because it isn’t viewed production data.This is only true, until it is. When your production is offline, you need a reliable solution to get you back to work, as fast as possible.Now, my approach has always been to match the best technology. Careful not to overcomplicate, but enough to allow best in breed, or match technology that is first class in their space to build the solution. So, in this demo I will show how features in Pure can help support those in Veeam. So, what does this demonstra

Hi, we have 3 backup copy jobs for one backup job. All backup copy jobs for a specific vm fail with the following error: 9-8-2023 22:31:45 Error: Failed to decompress LZ4 block: Bad crc (original crc: 5a73d881, current crc: 3fa0f4bc). Failed to upload disk '65505BFB' Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Failed to decompress LZ4 block: Bad crc (original crc: 5a73d881, current crc: 3fa0f4bc). Unable to retrieve next block transmission command. Number of already processed blocks: [132]. Failed to download disk '65505BFB'. The only way to solve this, was doing an active full on both the backup job and the copy jobs. I'm puzzled why this CRC error occurs. There is corruption on the source backup files (Backup validator also reports this). The backup files are located on a ReFS raid 6 volume. Integrity streams are enabled, so if there's corruption shouldn't refs detect that also? I can copy the file from windows explorer fine. If ReFS detects an inte

I'm running Server 2022 Definitely in 64 bit (Do they make 32 bit even????) and whenever I try to create a VMWare proxy or any other proxy I get the error "VMware backup proxy requires 64-bit operating system" I have no idea why, and I haven't found anywhere leading me to anyone else having this exact issue either. Any idea what might cause it?

Hi Guy’s The path to success is rarely linear; it often winds through setbacks, challenges, and moments of doubt. My journey through the VMCA (Veeam Certified Architect) exam epitomizes this truth, culminating in a well-earned victory with a score of 79%. It's a story of resilience, growth, and the satisfaction that comes from persevering against the odds.Adding a unique layer to my journey is the fact that I have spent the last seven years dedicated to working with Veeam, a prominent player in the realm of data protection and management. This experience has given me an extensive and intimate understanding of the intricacies of data backup, recovery, and virtualization management.The VMCA exam was no small feat during my first two attempts, with scores of 55% and 64% respectively. Yet, each outcome held within it a lesson, a piece of the puzzle that would eventually lead me to success. These results could have deterred me, leading to discouragement and abandonment, but they had the opp

Hi  have currently this warning for 3 consecutive days. the backup jobs ara all success but I getthis warning message . can any one help me resolve thisWarning message:>>>>>>>>>>>>>>>>>>>>>>>8/31/2023 10:00:51 AM Warning Failed to connect to GCP plug-in: Failed to login to platform service: No connection could be made because the target machine actively refused it xx.xx.xx.10x:9xxThnanks in advance>>>>>>>>>>>>>>>»  

I want to share my experience of an Active directory migration through the VB Replication software related to an Active directory environment 2012 R2 - forest and domain functional level 2012 R2.The customer asked me to migrate 3 Domain controllers from an old  VMware 5.5 to the new VMware 6.5 infrastructure for a technological refresh.Given that the best solution from Microsoft is to create new VMs and promote them Domain Controllers and transfer FSMO roles.That said, there are scenarios like mine, where this type of approach was not possible as it was mandatory to maintain the same FQDN and IP address due to application configuration problems.Microsoft advised against demoting and promoting a DC with a different OS but with the same FQDN and IP, even if my environment was relatively small 3 DC one forest \ domain and not complex it could be done with the metadata cleanup procedure but the customer did not give the approval. So I have adopted the solution of VM replica. Scenario -----

We have six backup copy jobs that are failing with the following error;Error: Violation of PRIMARY KEY constraint 'PK_Storages'. Cannot insert duplicate key in object 'dbo.Backup.Model.Storages'. We have rescanned the repositories and reran the backup copy jobs, but still experiencing this error.A case has been opened with Veeam support and we are anxiously awaiting their response.Thanks