Advertisements

Month: December 2019

The Tale of 3 Veeam Backup Targets with Deduplication on Windows Server 2019 – #Veeam @Veeam #LowDiskSpace

Hey Checkyourlogs Fans, Today I wanted to discuss 3 Veeam Backup Targets at a customer that I’m working with. All three of these backup targets are running Windows Server 2019 with the deduplication feature enabled. We are having constant issues with one of the backup targets running out of space and my team having to manually run garbage collection, scrubbing and optimization to free up space. This backup target, as we found out, is the victim of what I call a non-dedup optimized workload. This means that the Windows Server 2019 Deduplication engine is having a difficult time breaking...

Read More

The Case of VM’s not Showing up in Veeam One Hyper-V Infrastructure Object – #VEEAM #VEEAMONE #HyperV

Hey Checkyourlogs Fans, Today I was working with a client that was having issues with one of their Veeam One Infrastructure Replica Targets not showing any Virtual Machine information. I checked the alerts on the server and noticed that there was an alert about the Hyper-V Management Service not running. Well, this is where it would pull all of these details from. Sure enough it was stopped. Started the Service Within a minute or two I could once again see the Virtual Machine in Veeam One. I hope this help you out. Thanks,...

Read More

The Case of Veeam Error 32768 Failed to revert VM Snapshot – #Veeam @Veeam

Hey Checkyourlogs Fans,   Had a ton of my Veeam Replica jobs fail at a customer site overnight. The issue presented itself with the following error messages:   Failed to process replication task Error: Job failed (“Domain Controller_replica’ failed to apply checkpoint. (Virtual machine ID 6FC739AB-3494-43E1-875F-81442AC2C3CB)’). Error code: ‘32768’. Failed to revert VM snapshot, snapshot path ‘\\<SERVER>\root\virtualization\v2:Msvm_VirtualSystemSettingData.InstanceID=”Microsoft:E48E5F9D-9DF2-4F7F-9700-224604157E69″‘.   It appears that something might be wrong with the services on the Target Hyper-V replica server. When I did some more checking this morning, I found that we ran out of disk space overnight.   This Server has been running as...

Read More

The Case of the missing Service Connection Point in Active Directory for Hyper-V

Hey Checkyourlogs fans, This case occurred today when I was writing a new Hyper-V Reporting Script. The script needed to hunt for all Hyper-V Services in a Domain. Everything seemed fine until I noticed that a couple of the servers were not picking up in the report. Let’s start by looking at the query function Get-HyperVServersInAD { [cmdletbinding()] param( ) try { Import-Module ActiveDirectory -ErrorAction Stop } catch { Write-Warning "Failed to import Active Directory module. Exiting" return } try { $Hypervs = Get-ADObject -Filter 'ObjectClass -eq "serviceConnectionPoint" -and Name -eq "Microsoft Hyper-V"' -ErrorAction Stop } catch { Write-Error...

Read More
  • 1
  • 2

Translate our Blog

Subscribe to our Blog

Authors

Microsoft MVP

Cisco Champion

MODE

Veeam Vanguard

Follow me on Twitter

Follow @SuperCristal1 on Twitter