Restore Fails After Veeam Server Renamed

[rboynton]

We are in the process of hardening our Veeam server. Pulled if off of the domain and into a workgroup, changed the local admin account, enabled firewall... all according to the Infrastructure Hardening document. Backups, replication, and Backup Copy Jobs are working fine. Tried restoring a test backup made before the server was renamed and it failed "unable to publish VM". The error says

Code: Select all

"3/6/2019 9:44:55 AM Error    Failed to publish VM test Error: The RPC server is unavailable.
RPC function call failed. Function name: [InvokerTestConnection]. Target machine: [Veeam.OldDomain.com:6161].

Anyone else see this? If the Veeam server is renamed, how can a restore be made of the existing backups?

[ejenner]

My first instinct would be that your non-domained backup server has no access?

[rboynton]

Another clue. We reloaded our Veeam server and restored the database. The only issue was we did not recreate a volume called D:\. From this logfile, looks like that is what is failing. How do you change the datastore to look at a different drive letter?

Code: Select all

[06.03.2019 08:11:11] <  2380> nfs| ERR |Failed to start NFS service.
[06.03.2019 08:11:11] <  2380> nfs| >>  |boost::filesystem::create_directory: The system cannot find the path specified: "D:\"

[PTide]

Hi,

How do you change the datastore to look at a different drive letter?

Have you checked this KB already?

Thanks

[rboynton]

Thanks, PTide! I missed that KB, but changing that registry entry and restarting the Veeam services resolved the problem! Yay!