Today, I received some warning notification emails from Veeam Backup Jobs, they are showing warning as follow:
“Failed to create change tracking time stamp for virtual disk file C:\ClusterStorage\Volume1\PRODVMS\SQL2\SQL2\disk-0_EB28E537-B0D9-4F9B-80CC-065D6A5E142C.avhdx
Failed to create change tracking time stamp for virtual disk file C:\ClusterStorage\Volume1\PRODVMS\SQL2\SQL2\disk-1_4291495F-31FD-48D8-8621-64516CB1CE6D.avhdx”
I think I can try to clone the old backup jobs and recreate a new backup job and it should fix the issues, unfortunately, the issues still happened. After did some research, we can use Veeam PowerShell cmdlet to clears and resets change tracking data for a VM or specific virtual disk (VHD), the detail steps as follow:
- Login to your Veeam management server.
- Open PowerShell command promote as administrator.
Veeam Backup & Replication PowerShell is available as a snap-in, not as a module, so we need to install it locally, run follow cmdlet to get start with Veeam PowerShell Snap-in.
Run follow PowerShell cmdlet to reset change tracking data for a VM or specific virtual disk (VHDX).
Reset-HvVmChangeTracking [-Server] <CHost> [-VMName <String>] [-WarningAction <ActionPreference>] [-WarningVariable <String>] [<CommonParameters>]
Reset-HvVmChangeTracking [-Server] <CHost> [-VhdPath <String>] [-WarningAction <ActionPreference>] [-WarningVariable <String>] [<CommonParameters>]
In my case, I run PowerShell cmdlet as follow:
Reset-HvVmChangeTracking -Server GS-N2-ADM -VhdPath " C:\ClusterStorage\Volume1\PRODVMS\SQL2\SQL2\disk-0_EB28E537-B0D9-4F9B-80CC-065D6A5E142C.avhdx " Reset-HvVmChangeTracking -Server GS-N2-ADM -VhdPath " C:\ClusterStorage\Volume1\PRODVMS\SQL2\SQL2\disk-1_4291495F-31FD-48D8-8621-64516CB1CE6D.avhdx "
Re-start backup job again and you will see the issues are gone.
Happy Canada Day! Hope you enjoy this post.
I found it likes the -Server to match what is in the inventory of Veeam. e.g if you add via IP address, use IP in the command, great guide though thanks.
Still having the same warning even though PowerShell did not report any error after running the command