by RoderikdW » Fri May 08, 2015 9:41 am people like this post
Support Case ID: 00913359
I am attempting to restore a Windows 2012 R2 Server to VMWare vCloud DIrector 5.6 using VEEAM Endpoint Backup Free Recovery Media. I created a Recovery Media which includes hardware drivers, and made a backup which was sent to the B&R server.
Now I made a clean machine and inserted the ISO of the Recovery Media. I selected Bare Metal Restore and am attempting to connect to my B&R Server. But for some reason I receive the following error: cannot connect to a backup server.
I have tried it on a VM which had windows server 2012 R2 already installed and a completely new VM. I have tried using the login credentials of the VM's current OS, the backupped server's credentials, and finally my B&R account's credentials. But nothing works and I keep receiving the same error message.
by Mike Resseler » Fri May 08, 2015 3:42 pm people like this post
In that case, can you rerun the entire procedure. When it fails, and you are back on the main window of the recovery media, do not restart but go to the tools. There is an option to save the logs. Save those somewhere and PM Dima.P from the forums here so support can do an investigation to figure out why it is not connecting
by RoderikdW » Mon May 18, 2015 11:56 am people like this post
My apologies for the delay, I have sent the Exported Logs as requested to Dima P. However the error I am getting is slightly different now. The reason for this is because a collegue deleted the VM's I was using to test Veeam Endpoint. So after setting up a new environment to test the Bare Metal Restore in, I tried to execute a Bare Metal Restore and got the following error:
Unable to make a connection to VBR. Either host is unreachable or VBR is down or VBR Version is not supported. Endpoint supports connection to VBR patch2 or greater.
I am quite confident in the fact patch2 is installed as I have done this myself, and this error did not occur last time. The only change that has taken place in between these 2 attempts to execute a Bare Metal Restore is the upgrade of our Cloud Provider rental license from standard to enterprise plus, however I am not sure how this impacts my Veeam Recovery Media and the connection to the server with this media.
by Mike Resseler » Mon May 18, 2015 3:16 pm people like this post
The reason it is out of your portal is because this is a support case for VEBF (Sorry, didn't realize that you were talking about the portal... should have known that...) Because our support for free tools is a bit different than our support for paid versions (no SLA's given, everything on best effort) we converted it to a VEBF case and therefore it is gone. However, the case still exists and the email conversation will continue as normal but as said, it is on best effort.
by Dima P. » Fri Jun 05, 2015 3:51 pm people like this post
Hi Roderik, We’ve detected from the logs that the Recovery Media iso was created in the RC code. May I ask to recreate it then boot and configure the network in the wizard and if the repository is reachable. Once configured, check if you can properly ping the repository server via cmd. Thanks in advance.
by RoderikdW » Tue Jun 09, 2015 2:33 pm people like this post
I am not able to ping it because the firewall does not allow it, but I can telnet it over port 10001 and 6180, yet I cannot connect to the server on the bare metal restore wizard. I am slightly confused as to which credentials must be given when trying to access it too. Should it be the credentials given during the configuration of the actual backup ,or should it be the credentials of the account you received from your cloud provider?