VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Veeam released V7a of VB365 just recently (Dec 5th, 2023).https://forums.veeam.com/veeam-backup-for-microsoft-365-f47/current-version-is-1-0-0-860-ga-t39185.htmlThe KB for the patches to 7.0 has all the changes of 7.0.x: https://www.veeam.com/kb4425With a new major release (e.g. V7) we get the changes within the “what’s new” document: https://www.veeam.com/veeam_backup_m365_7_0_whats_new_wn.pdfThere does not seem to be a “what’s new” document for 7a (7.1.x). Here I can only find the full release notes which makes it kind of hard to determine changes.Did anyone find the specific changes within 7a already?
A Veeam storage plugin needs to control your storage device in a way. Therefore you need a user account inside your storage system. The same of course is true for the DataCore plugin.From a security standpoint one always wants to have only the least amount of permissions to be allowed to the user. Avoid using a global admin here to minimize your attack surface!Here I will describe how to achieve that with the Veeam storage plugin for DataCore:First create a new role inside your DataCore console. In the screenshot the permissions to attach to the role are shown:Veeam storage plugin for DataCore - Role permissionsOnce the role is setup, you can create the user inside DataCore and select the role to assign it to:Veeam storage plugin for DataCore - Create the user for Veeam accessFinally you will have to create a local user of the exact same name inside all Windows servers involved in your DataCore cluster. Usually one has two nodes in a mirrored cluster. As the nodes are not supposed to b
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
In an agent job for a WSFC (fileserver role) we see a warning after having switched over to the secondary node. Each job run now finishes with a warning that CBT table has changed.As with VM backups I expected the warning to disappear in the next cycle - but it didn’t. How can I reset the CBT for an agent backup (not hypervisor based CBT but Veeam CBT driver here)?
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
In a customer environment today we faced the issue that all HANA plugin backups all of a sudden stopped backing up:Session failed: Unable to process the workload: your license has been exceeded In VBR’s license dialog I found the plugins to consume VUL licenses all of a sudden - which there are only the 6 complimentary ones. The plugins run on VMs already under socket licensing and that worked for years.Has anyone seen this already? How does VBR actually determine if the plugin resides on a VM? This process seems to be impaired here.Case is open. Support is digging through plugin logs. ThanksMichael
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/
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.