Community

With v12 you can add VMs to a global exclusion list. These VMs will not be backed up. Even if explicitly added to a job.  Nice new feature for all those VMs that aren't worth backing up.

Hey guys, in this link it says veeam cannot backup failover cluster with CSV and CSV will be excluded if you are backing up that cluster. https://helpcenter.veeam.com/docs/backup/agents/cluster_support.html?ver=110Is there recommended way to backup those volumes? Can volume or file level backup solve this?

IntroductionIn a previous post, I covered the SOBR Capacity tier Calculations and Considerations. Today, I will be exploring the Archive tier and discuss how to estimate Archive storage requirements, expected API calls and Proxy Appliance uptime. Before we jump into more details, remember that the Archive tier only works with “Amazon S3 Glacier”, “Amazon S3 Glacier Deep Archive” and “Microsoft Azure Archive Storage” in Veeam v11. In the SOBR configuration, under Archive Tier, you define after how many days (1) you want to free up space from your more expensive capacity tier by offloading to the typically** less expensive Archive Tier.**Keep in mind that the Archive tier is meant to store data for a long time (i.e. more than 1 year, up to 7 or more years). It is not meant for active day-to-day restore operations.You will find that storing data in the Archive Tier for less than 1 year won’t make much economic sense (at least at the time of this write-up!). It is also very important to re

I would like to revive my old “what else is new” series I did for VBR v11 some time ago. This time, it is about v12 - what else?First part is about the new integration of Linux Hardened Repository. This was one of the greatest new features in v11. To bring the repository to VBR it was necessary to create a Linux repository and enable immutability. With v12, Hardened Repository is added by a new option: But there is more! With this, you can just add the repository with single-use credential. That was highly recommended in v11 recommended. Furthermore, after adding a Hardened Repository, immutability is enabled and cannot be disabled.  … even with PowerShell. I like it! Also because this increases security. If a hacker enters the VBR server, it is not possible to disable immutability any more. Check my post about how to monitor these settings with Veeam ONE.

We currently have a situation where we need to copy backed up files on a different subnet from the Veeam server.The backup files are on the proxy server in a different subnet and I need to copy them to a different server on the same subnet.  Veeam is across a VPN so copying 1 TB of files from Veeam across the VPN would take too long.When I mount the files to restore it would be great if they were available in the VeeamFLR folder on the proxy server.   Then I could copy them directly on the same subnet.  Right now the files to restore are only available on the Veeam server.As a workaround I’m going to install Veeam on the Proxy server so I can access the backed up files without using the VPN.

Hi Folks, Here is a recording of the live session of Kubernetes Korner. We discussed the origins and the future.  https://transcripts.gotomeeting.com/#/s/bcaad2c15ac882a1e59c5bd40a870edd0fb3c2e29e7a913edc138c86ecbda04e cheers  

Microsoft have recently released SQL Server 2019 CU16, and in this blog post I’m calling out a very specific bug that Microsoft have addressed, and the implications this has to business-as-usual operations. Transparent Data Encryption (TDE) & Compressed BackupsMicrosoft have been tracking a bug related to using TDE and compressing backups, impacting both database, and log backup types. Should you attempt to restore a compressed backup of a TDE database, you’ll likely receive a message similar to the below:Msg 3241, Level 16, State 18, LineThe media family on device 'BackupFileName' is incorrectly formed. SQL Server cannot process this media family.Oh dear. This isn’t good! Prior to CU16, Microsoft’s workaround was to simply not compress your backups. Before we proceed any further, I also want to call out that I’ve not yet heard of any examples of Microsoft retrospectively fixing these backups, so if you’re currently in this dangerous scenario, mitigate ASAP. SQL Server 2019 CU16 Re

Hey guys,A customer of mine has asked whether I could create recovery media for failover cluster but in this linkhttps://helpcenter.veeam.com/docs/backup/agents/image_create_before.html?ver=110 tells that I cannot create a recovery media and I should enable creation of a Veeam Recovery Media for such clusters with a registry value. Has anyone faced this situation and enabled recovery media with registry value. Also I referred this link https://forums.veeam.com/servers-workstations-f49/unable-to-create-recovery-media-for-server-t73845.html

Hi Community, For automated disaster recovery process. Need help to develop PowerShell scripts.Add backup repository Decrypt backup Import backupsCode up to now as bellow$account = Get-VBRAmazonAccount -AccessKey "XXXXXXXXXXXX"$connect = Connect-VBRAmazonS3Service -Account $account -RegionType Global -ServiceType CapacityTier$bucket = Get-VBRAmazonS3Bucket -Connection $connect -Name "veeam-backup"$folder = Get-VBRAmazonS3Folder -Name "S3-Folder" -Bucket $bucket -Connection $connect$securepassword = Read-Host -Prompt "Enter password" -AsSecureString$key = Add-VBREncryptionKey -Password $securepasswordAdd-VBRAmazonS3Repository -Name "AmazonS3Repository" -Connection $connect -AmazonS3Folder $folder -DecryptBackups -DecryptionKey $keyBut <-DecryptBackups -DecryptionKey $key> option doesnt work, error prompt as belowAdd-VBRAmazonS3Repository : A parameter cannot be found that matches parameter name 'DecryptBackups'.At line:1 char:99+ ...  -Connection $connect -AmazonS3Folder $folder -

I just installed the latest available version of Veeam agent for Windows on Windows 11 and it doesn't work.The service does not start 

Hi,Whats the best practise evacuate an extent with immutalbe backups?I need to evacuate an extent from an object lock repo with 7 days immutalbe backups.I put the extent in maintenance and started the evacuation. What happens with die immutalbe backups? They will stay on the locked repo?

Where can I find the compatibility information of Domino and Veeam Backup and Replication v11? Please help...

Morning, I’ve noticed that Veeam have slightly amended the end of sale date for existing customers seeking to purchase new socket licenses. Previously, Veeam Availability Suite, Veeam Backup & Replication, Veeam Backup Essentials and Veeam ONE were all due to migrate to support renewal only for socket based licensing on the 1st July 2022. This is changing slightly. Veeam ONE and Veeam Backup Essentials will still be committed to this date, however Veeam Backup & Replication and Veeam Availability Suite additional licenses will still be purchasable for existing socket customers through to the 1st January 2023. If you believe you’ll need additional socket licenses and have no intention of moving to VUL (you really should though if you can), be sure to factor these deadlines into your purchasing timelines!

Hello everyone,We’ve a huge Oracle DB on 3 clustered servers which is backed-up using EMC NetWorker but we’re planning to switch to Veeam.Any ideas on this plan? What to do before starting? What to consider while switching? Leave NetWorker running with Veeam for a while? Thanks, 

I have recently added a standalone Hyper V 2019 host to Veeam infrastructure. It added successfully. SO i created a HWP for my customer, see the host and the network. When the customer creates his job, he see his plan however when he runs the replication job  it fails:“Failed to process replication task Error: Cloud gate has rejected connection. Reason: Unable to establish target connection. All aliases have failed….” My VMware replications are running fine.Please help!!

Hi, I was reading the manual on Instant Disk Recovery Manual and I have a question.When you click “Migrate to Production” does this suspend the VM? The problem is that I have a VM which I restored the disk using Instant Disk Recovery, but on reading online further, it seems that when I click “Migrate to Production” the VM will be stopped until the disk has been completely restored. Is this correct? Thank you,Paul 

Hello guys,Can anyone specify the reasons for choosing veeam’s agent backup- standalone and managed mode?

I’m new to Veeam and I really like how easy it is to create scheduled backups and to retrieve individual files.Does anyone know what kind of compression Veeam uses when they create either increment or full backups?  Thanks, Steve

I hope you can help me with the following problem.I have ubuntu/linux running alongside windows, dual boot system.Veeam Agent for Linux FREE is installed in ubuntu/linux.But now when I arrive at Shared Folder Settings both NFS and SMB I can't fill in anything.See attached photo as an example.Path, Domain etc... I cannot access.Hopefully July can help me further.Kind regards,Koen 

Yesterday I saw the error a second time, so I thought it would be helpful to others to share.Error happens when VBR tries to read vSphere information for the VM to back up. Error says "Error in the application" like you see in the screenshot.After some troubleshooting we found the reason for this. It was because TCP-port 902 was not allowed (in all firewalls) from the Veeam proxy server to the ESXi host that was hosting the VM to back up. After the port was enabled in the firewall(s), backup ran without further issues. Notes:Used ports for VBR see here: https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=110 Vanguard @Cragdoo also shared this error some time ago. In his case the error was caused by a name-resolution problem on a new Linux Veeam proxy server.I hope this post safe others some time when this error appears.  

In v5 it was not possible to restore sharepoint online data to another tenant. After upgrading to v6, is it possible to restore the data created with v5 to another tenant? Or should the backup created with v6? Kind regardsJohn

Curious what y’all are doing in this sort of situation.  I have a client with a rather large VM (95 TB, consisting of VMDK’s at 100GB (OS), 30TB, 19TB, 20TB, 9TB and 17TB).  The repo (Synology NAS) is about 90TB of usable space with a second NAS at 24TB. The volumes are ISCSI presented as RDM’s to the virtual Veeam server running 2012 R2.  Volumes are formatted REFS.The backup job for this server is split into three jobs...one for the OS disk and the 9TB and 30TB disks (active data) to the primary NAS, one for the 19TB and 20TB disks (Archive Data) to the Primary NAS, and one for the 17TB disk (Archive Data from an old location) to the secondary NAS).Current backup jobs are forever forward incrementals keeping 31 days of restore points, but as such, we have defragments and compactions running, but they take a VERY long time (the first mentioned job has been running for almost 16 hours and is at 6%, and that’s with only 3 restore points due to an issue I fixed yesterday where the volume

By default, VBR does a configuration backup every day at 10:00.It is obvious that this backup should also follow the 3-2-1(-1-0) rule. A easy way to do this is to copy these restore points to a machine that is already backed up be Veeam and therefore covered by the 3-2-1(-1-0) rule. This can be done with a Veeam File Copy job. This job can copy files between systems part of Managed Servers.Lets do it and create a File Copy job:and select the path to the configuration backup as sourceFor destination select the server system you want to copy files to. As mentioned, this system should be part of backup job. Finally select your preferred time schedule. I would recommend to run this job just after the configuration backup.Done? Almost! It is important to know, File Copy job copies files respectively a directory, but is does not synchronize. Therefore the amount of files at the destination will increase. So they should also get deleted after some time otherwise partition runs full. A easy wa

SQL Commands for Veeam to be able to link a Backup Job that was done before the Veeam B&R Server was migrated to a new server. and Perform a Backup Copy Job.