VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Log-shipping with VBR involves your SQL or Oracle server (VM or agent), optionally a log-shipping server and of course a repo to store the VLBs.With Hyper-V underneath one might even log-ship through the hypervisor by using PowerShell direct. This is nice, as it allows to isolate your DB workloads from the backup network and still leverage log-shipping.During the process Veeam creates temp files of the logs to be shipped first on the DB server and then the log-shipping server. Finally, after a LZ4 compression, those are driven to the repo and deleted on those temp locations.On the DB server the temp path for logs is defined in the registry and defaults to the largest disk the server has (since 9.5U4a). The path can be changed: https://www.veeam.com/kb2642On the log-shipping server the process is always using the %TEMP% path to store the data.Problem is, VBR does not seem to check both pathes before it copies the raw transaction logs during each cycle. So, a large transaction log to be
I was able to solve this challenge in a project and would like to share the findings. The challengeConsider you want to restore Exchange items (e.g. mails, calendar objects, etc.) using Veeam Explorer for Exchange as well as Veeam Enterprise Manager.Consider also, that you have a larger multi-domain infrastructure with the VI and backup infrastructure in a sub-domain (infra.mydomain.com). For security reasons, we are not able to reach the GC of the root domain. The mail addresses are derived from the root domain though (myuser@mydomain.com).This might lead to the situation that neither Veeam Explorer for Exchange nor Veeam Enterprise Manager can determine the CAS server of your Exchange environment, as they want to contact the GC in charge first. This is even if they can easily reach the CAS itself. You can observe this in the corresponding logs (%programdata%\Veeam\Backup\ExchangeExplorer\Logs): 13.04.2023 15:35:39 15 (17156) Looking for mailbox 'myuser@mydomain.com' in Global Cata
In a customer project I just stumbled across the requirement to do SQL log-shipping with VMs. A simple task, I thought at first. But this time the request included a so-called division by zero - at least from a VBR perspective. With VBR (at least until V12), it is not possible to restrict log-shipping to certain days of the week. You can only set the overall frequency of log backups: Microsoft SQL Server Transaction Log Settings - User Guide for VMware vSphere (veeam.com)You can set a schedule for image-level backups of course. But in between, log backups are performed continuously as defined by the above setting.It came in very handy that @SteveHeart recently published another script that can determine which VBR backup job a PS script was started out of. The code in mention to actually determine the process ID of the VBR job above goes back to @tsightler. So the script can be used flexibly as you don’t have to hard code job names etc. So I “borrowed” this code and enriched it with tog
I just updated my deep dive series on the plugin.The most important new feature is the support for DataCore's CDP. This allows to lower your RPO for your full stack to a few seconds with just a few clicks.Find more details here: https://www.elasticsky.de/en/2022/02/veeam-storage-plugin-for-datacore-v1-2-0-improvements/
Just a heads up for a hotfix to VB365.We recently faced multiple errors within our MSP stack for VB365:Processing mailbox xyz failed with error: There is an error in XML document (1, 5332).. The specified type was not recognized: name='SharingMessage' Turned out to be a problem introduced by some changes Microsoft applied to M365.Veeam published a hotfix just a few days later: https://www.veeam.com/kb4527It’s applicable to the most recent version of 7 (7.0.0.4388) as well as 7a (7.1.0.1301) and I can confirm it to solve the issue.You have to stop all services and replace Veeam.Ews.dll in 4 different locations.Make sure to rename or copy the files to be replaced beforehand and have or create a backup of the VB365 system.
This is part three of the blogpost. If you want to read it from the beginning, head here: SOBR Archive Tier – Explained and Configured – Part 1 of 4 | Veeam Community Resource HubIn this part 3 of 4, I will walk you through all the things to set up for the archive tier in Azure. How to setup the archive tier for your SOBR in Microsoft AzureLet’s assume we already have a SOBR using a capacity tier to offload data to Azure in a specific schema. Could be either copy or move or even a combination of both to fulfill the 3-2-1 rule. A nice walkthrough of the capacity tier setup could be found e.g. here: https://jorgedelacruz.uk/2019/05/14/veeam-cloud-tier-capacity-tier-in-microsoft-azure-blob-how-to-configure-a-veeam-backup-replication-scale-out-backup-repository/This would be our starting point to enable another shift of the already offloaded data into the cheaper archive tier.Therefore, first of all we have to define another storage account in the correct tier level. In our example for Azu
IntroAn often overlooked feature we can leverage since V11 is the archive tier for the Scale-Out-Backup-Repository (SOBR).SOBR: Tiers against fears… 😉While we find quite some good guidelines for the Veeam side of the functionality (e.g. Archiving Backup with Microsoft Azure Blob | Veeam Community Resource Hub), I’d consider it helpful to have some more insights to the technology and a guideline to also set up the hyperscalers side of the archive tier. I’ll choose Microsoft Azure here as an example. In the following blogpost with four parts (TLDR), I’ll walk you through some background and the complete setup. A short history of the SOBRA scalable storage layer for backups is crucial for larger environments. This is why Veeam brought us the Scale-Out-Backup-Repository with VBR version 9.0 already. First it only consisted of the so called “performance tier” – that is the on-premises storage devices being pooled together as so called “extents” in a very flexible way.With Version 9.5 U4 t
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.