nbhypervtool.exe
Dear Veritas Enthusiasts, i would like to ask if anybody has additional information about the nbhypervtool.exe. i need to know what nbhypervtool.exe does in the back, does it only delete the snapshot, is it the same as using the powershell cmdlet remove-vmsnapshot or there is slightly different functionality. i am asking for these details in the context of some left snapshots of hyper-v virtual machines and the possible supported steps to remove old snapshots that netbackup left after the backup. thank you in advance!hyper-v backups are failing with status code 13 or 25 if the hyper-v virtual machines has a snapshot
any ideas are welcome on the following as the case we have with veritas is almost 2 months old without any progress: if the hyper-v virtual machine has a snapshot which was created from hyper-v or failover console, the backup of the vm fails with status code 13 or 25: 28.09.2020 18:57:27 - Error bpbrm (pid=145214) socket read failed: errno = 104 - Connection reset by peer 28.09.2020 18:57:27 - Error bptm (pid=147427) system call failed - Connection reset by peer (at ../child.c.1289) 28.09.2020 18:57:27 - Error bptm (pid=147427) unable to perform read from client socket, connection may have been broken 28.09.2020 18:57:28 - Error bptm (pid=147293) media manager terminated by parent process 28.09.2020 18:57:33 - Info xxxxx (pid=147293) StorageServer=PureDisk:xxxxxx; Report=PDDO Stats (multi-threaded stream used) for (xxxxx): scanned: 3 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled 28.09.2020 18:57:35 - Error bpbrm (pid=145214) could not send server status message to client 28.09.2020 18:57:37 - Critical bpbrm (pid=145214) unexpected termination of client xxxxxx 28.09.2020 18:57:38 - Info bpbkar (pid=0) done. status: 13: file read failed 28.09.2020 19:00:15 - connecting 28.09.2020 19:00:16 - connected; connect time: 0:00:00 28.09.2020 19:00:22 - begin writing 28.09.2020 19:00:35 - end writing; write time: 0:00:13 file read failed (13) a workaround is to disable exclude deleted block and swap and paging files but this is not appropriate for us due to negative performance impact thank you all!
Protecting Hyper-V Virtual Machines on SMB using Backup Exec 20.4
Starting from Windows Server 2012, virtual machines in Hyper-V can be configured to use Server Message Block (SMB) 3.0 file shares as storage just like local volumes. By using SMB shares, storages for Hyper-V can be converged and operating costs can be reduced. Additional advantages of Scale-out file servers include continuously available file services, automatic load balancing and easy management of servers. Deploying Hyper-V over SMB shares from Scale-out file servers is an ideal solution for Hyper-V.
How to Back up Linux VMs on Hyper-V
Backing up VMs through Hyper-V is using either VSS or WMI, and neither is working for Linux VMs. So, it seems to turn out there is no way to back up Linux VMs over Hyper-V. However, on the NetBackup Hyper-V backup document, it talks about backing up Linux VMs in saved mode or non-consistant way. I don't know why it could work at all. No matter what kind option I choose when creating a policy for backing up Linux VM, it always gets snapshot Error 156 which is very normal. Why does not Veritas simply claim that it is imporssbile to back up Linux VMs over Hyper-V? Anyway, what's the best practice to back up Linux VMs on Hyper-V? Thanks in advance, RossEnhancing resiliency for Instant Recovery
Now not just instant, but also resilient. The Enhanced Resiliency for Instant Recovery increases the data and application availability of virtual machines that are instantly recovered. This improves business continuity in case the Backup Exec server or the Hyper-V server must be restarted.
