Altaro Backup Error "BASEBACKUPCONTROLLER_18"

We use Altaro Backup exclusively. We swear by the product and the support has been awesome when needed.

There are times we need to learn to resolve issues ourselves as it give us a bit of satisfaction that we can accomplish solving issues on our own without hand holding at times.

We moved a VM from one host to another over the weekend. New Server hardware.
Everything was running well from the Altaro backups to the running of the VM on the temp server we installed to get the server off a failing Dell server. So failing server to temp server: all good.
Temp server to new server hardware: failed backups.

We built and brought in a new INTEL server system with 2016 Server.
E3-1230v6, 32GB Ram, 3.7TB usable storage.
We use a Buffalo TeraStation 3410DN for backups.
We use the latest Altaro software release for backup.
We team  2 Host nic's and 2 VM nic's - vm queues off, jumbo frames on.
Copied the VM back to the new server.

After the VM copy we had to reestablish the VM static IP and booted the server. All was well.

When we went to do our first Altaro backup we had a failure of the backup.
The backup started.
Backup preparing.
Then the error happened right at the creating shadow copy.


STARTED WITH THIS ERROR:

On Fri, 18 Aug 2017 00:18 A Warning occurred during a backup for SERVER-VM

Hide Details
The backup snapshot for this VM is not application consistent. The backup will proceed in crash-consistent mode. (Error code 'RCTCONTROLLER_011')
Please make sure that backup integration services are enabled for the VM. Otherwise check the event logs within the VM. If the issue persists please contact Altaro Support.




WHICH LEAD TO THIS ERROR:


The operation encountered an error. (Error code 'BASEBACKUPCONTROLLER_018')

An error occurred while opening a virtual disk (Error code 'VIRTUALDISKSTREAM_002')

The backup snapshot for this VM is not application consistent. The backup will proceed in crash-consistent mode. (Error code 'RCTCONTROLLER_011')
Please make sure that backup integration services are enabled for the VM. Otherwise check the event logs within the VM. If the issue persists please contact Altaro Support

We did some searching and found a few that said RESTART COM and DCOM and VSS Service.
No luck there

We found another from Altaro that basically covered all the possible issues Alot in ther "Gulp". We did not try all the options in this support post. We did try ADD SCSI CINTROLLER TO VM. This did not work.

We checked VSS writers - All looked good. No errors there.

We checked our event log and found a few cryptic NTDS and a VSS error. Unable to access.

Ahh, might be a permission error.

Which after searching, led us to this smart fella:

Igor Puhalo who runs the site: IP Loging

And this did the trick:

If you have this error you probably installed DHCP server role on your server. Very detailed explanation and solution you can find on Microsoft link https://support.microsoft.com/en-us/kb/2298620 It is the same for Windows Server 2012/2012 R2 version.

If you want to keep things simple all you need to do is add Network Service account on this registry key HKLM\System\CurrentControlSet\Services\VSS\Diag . After you give it full permission this error will be gone.

And his comment confirms our exact VM setup:
If you dont see this error in Event log after some time it is fine. If you want to see it again just take network service full permission in the same registry key. This error usually happens on DC with DHCP installed. I hope I helped. Just ask. If I have an answer I will post it


Thanks to Igor for posting this great find !