Restore VM Hyper-v error 2821 "Hyper-V policy restore error"
Good morning everyone. This is my first post here.
I have a problem with the restore of a VM that is in Hyper-V.
I had installed Netbackup version 8.2 and updated to version 9.1. I don't know if that was what caused my problem with the restore today.
Master = Windows 2012 R2 with Netbackup 9.1
Media Server = Windows 2016 Datacenter with Netbackup 9.1
Hyper-v version 2012 R2
If I restore the VM to Hyper-V when it reaches the time of 2:01 hours, the restore stops and issues the following error log below:
24/03/2025 09:01:29 - begin Restore 24/03/2025 09:01:31 - restoring from image EDC0-SIEM002_1742159784 24/03/2025 09:01:31 - requesting resource aaaa_ 24/03/2025 09:01:31 - granted resource MediaID=@aaaa_;DiskVolume=N:\;DiskPool=DP_ADVANCED_PRODUCAO_NOVO_BKS002;Path=N:\;StorageServer=edc0-bks002.icnavais.net;MediaServer=edc0-bks002.icnavais.net 24/03/2025 09:01:32 - Info bprd (pid=8736) Found (1.380.260) files in (5) images for Restore Job ID 1058605.xxx 24/03/2025 09:01:32 - Info bprd (pid=8736) Restoring from copy 1 of image created Sun Mar 16 18:16:24 2025 from policy HYPER-V_ESC_SEMANAL 24/03/2025 09:01:32 - Info bprd.sfr (pid=8736) Checking OS on destination. Operation may take CLIENT_CONNECT_TIMEOUT=14400 seconds 24/03/2025 09:01:56 - Info bpdm (pid=1052) started 24/03/2025 09:01:56 - started process bpdm (pid=1052) 24/03/2025 09:01:56 - Info bpdm (pid=1052) reading backup image 24/03/2025 09:01:56 - Info bpdm (pid=1052) requesting nbjm for media 24/03/2025 09:01:57 - Info bpdm (pid=1052) using 30 data buffers 24/03/2025 09:01:57 - Info bpdm (pid=1052) spawning a child process 24/03/2025 09:01:57 - Info bpbrm (pid=1052) child pid: 7032 24/03/2025 09:01:57 - Info bpdm (pid=7032) started 24/03/2025 09:01:57 - started process bpdm (pid=7032) 24/03/2025 09:01:57 - begin reading 24/03/2025 09:01:57 - requesting resource aaaa_ 24/03/2025 09:01:57 - granted resource MediaID=@aaaa_;DiskVolume=N:\;DiskPool=DP_ADVANCED_PRODUCAO_NOVO_BKS002;Path=N:\;StorageServer=edc0-bks002.icnavais.net;MediaServer=edc0-bks002.icnavais.net 24/03/2025 09:01:58 - end reading; read time: 0:00:01 24/03/2025 09:01:58 - Info bpdm (pid=1052) completed reading backup image 24/03/2025 09:01:58 - Info bpdm (pid=1052) EXITING with status 0 24/03/2025 09:02:04 - Info bpbrm (pid=4940) EDC0-VSH007 is the host to restore to 24/03/2025 09:02:04 - Info bpbrm (pid=4940) reading file list for client 24/03/2025 09:02:06 - connecting 24/03/2025 09:02:06 - Info bpbrm (pid=4940) starting bptm 24/03/2025 09:02:10 - Info tar32 (pid=147004) Restore started 24/03/2025 09:02:10 - connected; connect time: 0:00:00 24/03/2025 09:02:10 - Info bptm (pid=1012) start 24/03/2025 09:02:10 - started process bptm (pid=1012) 24/03/2025 09:02:11 - Info bptm (pid=1012) reading backup image 24/03/2025 09:02:11 - Info bptm (pid=1012) using 30 data buffers 24/03/2025 09:02:11 - Info bptm (pid=1012) spawning a child process 24/03/2025 09:02:11 - Info bptm (pid=1012) child pid: 4772 24/03/2025 09:02:11 - Info bptm (pid=4772) start 24/03/2025 09:02:11 - started process bptm (pid=4772) 24/03/2025 09:02:11 - begin reading 24/03/2025 09:12:21 - Info bptm (pid=1012) waited for empty buffer 12623 times, delayed 17339 times 24/03/2025 09:12:21 - end reading; read time: 0:10:10 24/03/2025 09:12:22 - begin reading 24/03/2025 09:21:22 - Info bptm (pid=1012) waited for empty buffer 13829 times, delayed 14225 times 24/03/2025 09:21:22 - end reading; read time: 0:09:00 24/03/2025 09:21:23 - begin reading 24/03/2025 09:30:28 - Info bptm (pid=1012) waited for empty buffer 14008 times, delayed 14402 times 24/03/2025 09:30:28 - end reading; read time: 0:09:05 24/03/2025 09:30:28 - begin reading 24/03/2025 09:39:29 - Info bptm (pid=1012) waited for empty buffer 13317 times, delayed 13743 times 24/03/2025 09:39:29 - end reading; read time: 0:09:01 24/03/2025 09:39:34 - begin reading 24/03/2025 09:48:28 - Info bptm (pid=1012) waited for empty buffer 14718 times, delayed 15138 times 24/03/2025 09:48:28 - end reading; read time: 0:08:54 24/03/2025 09:48:29 - begin reading 24/03/2025 09:57:17 - Info bptm (pid=1012) waited for empty buffer 14059 times, delayed 14138 times 24/03/2025 09:57:17 - end reading; read time: 0:08:48 24/03/2025 09:57:17 - begin reading 24/03/2025 10:06:01 - Info bptm (pid=1012) waited for empty buffer 13947 times, delayed 14282 times 24/03/2025 10:06:01 - end reading; read time: 0:08:44 24/03/2025 10:06:01 - begin reading 24/03/2025 10:15:03 - Info bptm (pid=1012) waited for empty buffer 15836 times, delayed 16235 times 24/03/2025 10:15:03 - end reading; read time: 0:09:02 24/03/2025 10:15:03 - begin reading 24/03/2025 10:23:55 - Info bptm (pid=1012) waited for empty buffer 15037 times, delayed 15469 times 24/03/2025 10:23:55 - end reading; read time: 0:08:52 24/03/2025 10:23:55 - begin reading 24/03/2025 10:32:42 - Info bptm (pid=1012) waited for empty buffer 14824 times, delayed 15255 times 24/03/2025 10:32:42 - end reading; read time: 0:08:47 24/03/2025 10:32:43 - begin reading 24/03/2025 10:41:37 - Info bptm (pid=1012) waited for empty buffer 16263 times, delayed 16693 times 24/03/2025 10:41:37 - end reading; read time: 0:08:54 24/03/2025 10:41:38 - begin reading 24/03/2025 10:50:38 - Info bptm (pid=1012) waited for empty buffer 14657 times, delayed 15071 times 24/03/2025 10:50:38 - end reading; read time: 0:09:00 24/03/2025 10:50:38 - begin reading 24/03/2025 10:59:37 - Info bptm (pid=1012) waited for empty buffer 13599 times, delayed 13978 times
24/03/2025 10:59:37 - end reading; read time: 0:08:59 24/03/2025 10:59:38 - begin reading
24/03/2025 11:02:33 - Error bptm (pid=4772) get_string() failed reading file list from bprd, (10054), network read error 24/03/2025 11:02:33 - Info bptm (pid=1012) EXITING with status 23 <----------
24/03/2025 11:02:34 - restored from image EDC0-SIEM002_1742159784; restore time: 2:01:03
24/03/2025 11:02:34 - Info tar32 (pid=147004) done. status: 23: socket read failed 2
4/03/2025 11:02:34 - Error bpbrm (pid=4940) client restore EXIT STATUS 23: socket read failed
24/03/2025 11:02:34 - end Restore; elapsed time 2:01:05
24/03/2025 11:03:29 - Error bpbrm (pid=4940) could not close progress file /E/ProgramÀ Files/Veritas/NetBackup/Logs/user_ops/ICNAVAIS/ntbkp/logs/jbp56D6.tmp.log on udc0-bks05.icnavais.net
24/03/2025 11:03:29 - Error bpbrm (pid=4940) client close errno = 1
Hyper-V policy restore error (2821)
I have Media disks being presented to the Master as Advanced Disk, where backups are made correctly without errors. These disks are taken from the 3par storage.
I've already tried to revert to version 8.2 on the media server and on the hosts involved in the VM and it didn't work.
I've already tried increasing the timeout for the media involved in the location Host Properties -> Media Servers -> My Media Server -> Timeouts
I set the value to 14400 in Client connect timeout, Client read timeout, Backup start notify timeout and Backup end notify timeout
Does anyone have any tips?
