I'm trying to get SureBackup report to verify backups.
But i stumbled upon many problems in the way.
I want to know if i'm doing something wrong, because the process of creating virtual lab was more complex than i imagined. If it's not me, i'll contact the support with logs.
I created Virtual Lab, set-up proxy with unused IP address from our production network and used "Basic (single-host Automatic configuration)". But after SureBackup failed the VM was orphaned in vCenter, i found here an old thread that you have to add vCenter server, not ESXi servers directly to Veeam (didn't know that, backups worked fine like that). I've done that, re-created everything, re-launched SureBackup job, it fails and now VM is not orphaned, but it's totally gone, though i always put a tick on "Keep the application group running after the job completes".
1) Why VM in Virtual Lab disappears after job is done? I cannot try to test it further manually if it's deleted.
The heartbeat test passes, but ping test fails. The IP of the VM is 192.168.100.104, but ping test tries to ping 192.168.255.104, which obviously shouldn't exist. There's something with masquerading IPs, but i don't really understand why it's needed, i don't need connection from Lab to Production network.
- Code: Select all
[13.04.2017 14:25:27] <01> Info [SureBackup] [HQ5] [PingTest] Begin 'Network adapter 1: IP address 192.168.100.104, pinging...'
[13.04.2017 14:25:27] <01> Info [SureBackup] [HQ5] [PingTest] [Simulation] Pinging 192.168.255.104 with 32 bytes of data:
[13.04.2017 14:25:32] <01> Info [SureBackup] [HQ5] [PingTest] [Simulation] Request timed out.
[13.04.2017 14:26:02] <01> Info [SureBackup] [HQ5] [PingTest] [Simulation] Ping statistics for 192.168.255.104:
[13.04.2017 14:26:02] <01> Info [SureBackup] [HQ5] [PingTest] [Simulation] Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
[13.04.2017 14:26:02] <01> Warning [SureBackup] [HQ5] [PingTest] End 'Network adapter 1: IP address 192.168.100.104, failed - request timed out'
[13.04.2017 14:26:02] <01> Info [SureBackup] [HQ5] [PingTest] | # | IP | Masquerade IP | Ping State | Fail Reason |
[13.04.2017 14:26:02] <01> Info [SureBackup] [HQ5] [PingTest] | 2 | 192.168.100.104 | 192.168.255.104 | Failed | Request timed out. |
2) Why does it ping masquerade IP but not real machine IP?
Subsequent tests fail, because they're also trying to use wrong IP address.
- Code: Select all
[SureBackup] [ScriptTests] [Console] Error 10060, A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.255.104:389
2017-04-13 14:34:39 Error Predefined script 1: name DNS Server, error code 10060
2017-04-13 14:35:00 Error Predefined script 2: name Domain Controller, error code 10060
2017-04-13 14:35:22 Error Predefined script 3: name Global Catalog, error code 10060
2017-04-13 14:35:22 Error Results: 0/3 test(s) passed, 3 failed, 0 skipped
3) Also i couldn't login to Virtual Lab Proxy appliance, the VM created by Virtual Lab. I thought maybe i could try to test ping manually from this machine to the restored VM, but i cannot login there, and VM is also deleted. This article didn't help, there are no options mentioned in the article (https://www.veeam.com/kb1447)
I can restore VMs manually to isolated network on our system, everything works fine, i have tested it before. But i would like to get some Veeam generated SureBackup report to present to my authorities.