Skip to main content
  • EN

Hello, I have a small vm, 5.4GiB in size.

Non-instant restore works fine, after restore completes, can boot into the vm and use it.
Whereas, instant restore fails, can boot into vm but it, not able to use it.

Host:
windows.server.datacenter.evaluation.edition.2022.21H2
VBAR server - 12.0.0.1420 P20230178

The repository is linux non-hardened, located over the internet, not local.

Looks like instant restore creates the required files including the .vhdx
Looks correct from hyperv manager.
but the vm will not boot correctly

 

> 6903075986]  /
├── 1086624914]  gparted
│   ├── >    4292475]  Snapshots
│   │   ├── s          0]  31D5C4AB-9443-43F4-8088-740728378880
│   │   ├── B      45092]  31D5C4AB-9443-43F4-8088-740728378880.VMRS
│   │   ├── 5      52567]  31D5C4AB-9443-43F4-8088-740728378880.vmcx
│   │   └──     4194816]  31D5C4AB-9443-43F4-8088-740728378880.vmgs
│   └── b 1082332439]  Virtual Machines
│       ├──           0]  41bdd5db-8ed7-4108-a2b7-daa85ee08bda
│       ├── 0      60197]  41bdd5db-8ed7-4108-a2b7-daa85ee08bda.vmcx
│       ├──     4194816]  41bdd5db-8ed7-4108-a2b7-daa85ee08bda.vmgs
│       ├──       45092]  41bdd5db-8ed7-4108-a2b7-daa85ee08bda.vmrs
│       ├──           0]  5C979542-5C33-4176-88F5-EBC8D69A9414
│       ├── d 1073778688]  5C979542-5C33-4176-88F5-EBC8D69A9414.VMRS
│       ├── d      58830]  5C979542-5C33-4176-88F5-EBC8D69A9414.vmcx
│       └──     4194816]  5C979542-5C33-4176-88F5-EBC8D69A9414.vmgs
└── 5816451072]  vhd
    ├── 8 5809111040]  gparted.vhdx
    └── 4    7340032]  gparted_9B7F3504-8940-4886-B39C-0FC343BBE9DF.avhdx

 

 

 

Not sure why veeam has an issue with name resolution?
Not sure why veeam has an issue with `Connection with repository restore agent was lost`

The local server name is `vserver03`, only a single network adapter, ipv6 is disabled and ping returns the correct ip address `192.168.62.233`
The linux repository uses ip address, not name

 

11/4/2023 3:13:40 PM          Restoring VM gparted_instant_restored...
11/4/2023 3:10:38 PM          Restoring from BR_NONHARD
11/4/2023 3:10:46 PM          Restoring WMI config
11/4/2023 3:11:04 PM          Restoring VM configuration file
11/4/2023 3:11:07 PM          Disk v:\VIS\instant\vhd\gparted.vhdx has been preallocated successfully
11/4/2023 3:11:09 PM          All VHDs were mounted successfully
11/4/2023 3:11:19 PM          VM configuration has been updated successfully
11/4/2023 3:11:27 PM          Snapshot created successfully
11/4/2023 3:11:29 PM          VM was started successfully
11/4/2023 3:11:30 PM          VM has been published successfully
11/4/2023 3:11:51 PM Warning    Failed to start restore agents
11/4/2023 3:11:55 PM          VM was stopped successfully
11/4/2023 3:11:55 PM Warning    Restore failed
11/4/2023 3:11:58 PM Warning    Connection with repository restore agent was lost

                                
11/4/2023 3:11:59 PM          Retry count: 2
11/4/2023 3:13:40 PM          Restoring VM gparted_instant_restored...
11/4/2023 3:12:00 PM          Restoring from BR_NONHARD
11/4/2023 3:12:14 PM          All VHDs were mounted successfully
11/4/2023 3:12:16 PM          VM was started successfully
11/4/2023 3:12:16 PM          VM has been published successfully
11/4/2023 3:12:42 PM Warning    Failed to start restore agents
11/4/2023 3:12:46 PM          VM was stopped successfully
11/4/2023 3:12:46 PM Warning    Restore failed
11/4/2023 3:12:49 PM Warning    Failed to resolve name: vserver03. Error: Temporary failure in name resolution

                                
11/4/2023 3:12:50 PM          Retry count: 3
11/4/2023 3:13:40 PM          Restoring VM gparted_instant_restored...
11/4/2023 3:12:50 PM          Restoring from BR_NONHARD
11/4/2023 3:13:04 PM          All VHDs were mounted successfully
11/4/2023 3:13:07 PM          VM was started successfully
11/4/2023 3:13:07 PM          VM has been published successfully
11/4/2023 3:13:32 PM Error    Failed to start restore agents
11/4/2023 3:13:36 PM          VM was stopped successfully
11/4/2023 3:13:36 PM Error    Restore failed
11/4/2023 3:13:40 PM Error    Failed to resolve name: vserver03. Error: Temporary failure in name resolution

“The repository is linux non-hardened, located over the internet, not local.”


what is the bandwidth between locations?

Sorry and also, on second review I would be suspicious to whether it is Veeam struggling to resolve your backup repository or the target hyper-v host failing to resolve to it.

 

Apologies if you’re already experienced with the concept but Veeam leverages a data mover on the backup repository, and a proprietary driver on the Hyper-V host to enable Hyper-V to read the data from the backup repository. So the successful resolution of the backup repository will be mandatory when using FQDN’s or hostnames

 

For more info: https://helpcenter.veeam.com/docs/backup/hyperv/instant_recovery_to_hv.html?ver=120

Hi @asdffdsa6132 

Consider some items during instant recover:

1. During recovery, Veeam Backup & Replication runs workloads directly from repository

2. Veeam creates dummy VMs and mounts the disks directly from backups tha are stored on your backup repository. 

3. Veeam create 2 stream channel to connect repo and VM.

4. Instant restore isn't the same that classic restore.

I think your issue is the communication from repository to VBR server. Has your repo same DNS configuration that VBR? 

Can you try a ping from Linux to VBR checking if DNS solve VBR hostname?

What's the internet connection from two sites?

Thanks 

 

Thanks,

I realize now `non-instant` is not correct terminology, I should call it `Full VM Restore`

On linux machine, not sure what to do about data mover, what do you suggest?

the linux server is very limited, 1vCPU, 2GiB memory, but again, works for Full VM Restore.

As for speed, the docs mention for backup repository the following, and for sure, the internet on both ends is approximately 1000 faster. note: Full VM restore works no problem.
“1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.“

I tried to run iperf on both machines, but so far, could not get it to work.

For the Full VM Restore, from the log, getting “19MB MB/s which is equal to 152Mbit/s”

`11/4/2023 2:51:49 PM          Restoring gparted.vhdx (127 GB) : 2.9 GB restored at 19 MB/s`

 

the windows server, using speedtest cli:
Latency:     3.57 ms   (0.03 ms jitter)
Download:   930.24 Mbps (data used: 433.5 MB)
Upload:   939.09 Mbps (data used: 979.6 MB)
Packet Loss:     0.0%

the linux server, using speedtest cli:
Download: 1235.93 Mbit/s
Upload: 899.28 Mbit/s

 

Each time the Window server was trying to do the instant restore,
I watched the linux vm using htop, looks like it is not being stressed.
Never went above 10% cpu
Never went above 300MiB memory.

 

 

df -h
Filesystem                    Size  Used Avail Use% Mounted on
tmpfs                         192M  780K  191M   1% /run
/dev/sda1                      19G  2.7G   16G  15% /
tmpfs                         959M     0  959M   0% /dev/shm
tmpfs                         5.0M     0  5.0M   0% /run/lock
/dev/sda15                    253M  142K  252M   1% /boot/efi
tmpfs                         192M     0  192M   0% /run/user/0
//65.108.23.xxx/u375044-sub1  1.0T  1.1G 1023G   1% /nonhard

Hi thanks for your explanation but you have not replied to our question about DNS.

As I told previously Instant recover use a link from VHD disk and repository to start the VM. Instead in  full VM restore the VHD disks are copied on the host. 

For this your full restore work regularly. 

@Andanet Thanks much, based for your comments, I made the required changes.
Instant restore is working now.

 

Perfect. I am pleased for you.

Comment


Terms & Conditions