Welcome to your hub for enterprise data protection discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
NetBackup 11 is Here
The latest release of Cohesity NetBackup 11.0 includes quantum-proof encryption, enhances industry-first user behavior monitoring and risk analysis, and adds protection for more PaaS workloads. Click here to learn more about the details of this release from Cohesity VP of Product Management, TimBurlowski. Click here to read the press release. See what's new in NetBackup 11. Have questions or thoughts? Drop them in the comments!
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?
Changing tmpdir on Linux for v10.5
I've tried adding TMPDIR=/var/tmp/netbackup in /etc/init.d/netbackup and adding TMPDIR and TEMPDIR into /usr/openv/var/global/nbdeployutilconfig.txt These do not change the TMPDIR I am looking at the fapolicyd rules and can see that tools like nbutil and nbhealthchecker create /tmp/par-726f6f74/temp-2527638/nbhealthchecker or /tmp/par-726f6f74/temp-3947960/nbutil This par-726f6f74 seems consistent at the moment, but that may change with the next upgrade, I don't know. I'd like to create a future proofed set of policies by taking control of the TMPDIR, and then Veritas is free to do what they want under that. example entries fapolicyd[613787]: rule=103 dec=deny_log perm=open auid=-1 pid=2527638 exe=/tmp/par-726f6f74/temp-2527638/nbhealthchecker : path=/tmp/par-726f6f74/temp-2527638/inc/lib/check_nb_license_validity.pm ftype=text/x-perl trust=0 fapolicyd[613787]: rule=103 dec=deny_log perm=open auid=-1 pid=2527638 exe=/tmp/par-726f6f74/temp-2527638/nbhealthchecker : path=/tmp/par-726f6f74/temp-2527638/inc/lib/check_nb_norestrictions_file_existence.pm ftype=text/x-perl trust=0 fapolicyd[613787]: rule=40 dec=deny_log perm=open auid=-1 pid=2530921 exe=/tmp/par-726f6f74/temp-2530921/nbhealthchecker : path=/tmp/par-726f6f74/temp-2530921/43caee81.so ftype=application/x-sharedlib trust=0 fapolicyd[613787]: rule=40 dec=deny_log perm=open auid=-1 pid=2530921 exe=/tmp/par-726f6f74/temp-2530921/nbhealthchecker : path=/tmp/par-726f6f74/temp-2530921/026f509c.so ftype=application/x-sharedlib trust=0 fapolicyd[613787]: rule=40 dec=deny_log perm=open auid=-1 pid=2530921 exe=/tmp/par-726f6f74/temp-2530921/nbhealthchecker : path=/tmp/par-726f6f74/temp-2530921/556e1d16.so ftype=application/x-sharedlib trust=0 fapolicyd[613787]: rule=40 dec=deny_log perm=open auid=-1 pid=2530921 exe=/tmp/par-726f6f74/temp-2530921/nbhealthchecker : path=/tmp/par-726f6f74/temp-2530921/2e36ee1c.so ftype=application/x-sharedlib trust=0 Thanks in advance Peter
Alta Reovery Vault as AIR target
Hi Can we use Alta recovery vault as AIR target for on-perm Netbackup domain we have a scenario like wants to do to AIR in Azure NetBackup domain with Alta recovery vault configured for long term retention. is it supported configuration? if not what about replication to Azure Blob store and duplicated to Veritas Alta recovery vault what will be the requirement valuable insight is much appreciated Thanks
Storage options for OS upgrade
Hello, we have a NetBackup 10.4 server that we need to upgrade the OS from rhel 7 to rhel 9. Currently the MSDP is on the same disk that the OS will target (/dev/sda) so I need to copy/relocate the backup images during the upgrade. I opened a case with support and they suggested mounting SAN storage. Is this the only option to duplicate the backup data, or can we use DAS/NFS for setting up a new AdvDisk? This particular host has no other drives in it to relocate the data to, so it will need to be off the host during upgrade. Thank youInstall snapshot manager failed
Hi everyone i New in the snapshot manager and i cant install a sm, in the process fail with the following error Waiting for Snapshot Manager configuration to complete (0/21) ... Configuration Failed. Error Details: EXIT STATUS 8500: Connection with the web service was not established. please your help
Windows server 2025 client support?
I had a look in the most recent OS support matrix from the 4th of march and I can't find any information that Netbackup 10.5.0.1 supports Windows server 2025 as a client. I mean, the 2025 version has been around a while, when can we expect a version that supports it? /PerAlta Recovery Vault - Which Documents Should I Use???
Hi Friends, I noticed I've created a bunch of documents to help educate and direct folks on how to use Alta Recovery Vault, but there are a lot of them and I thought it would be good to do a flow of what documents to use, when and what they're all about. So let's begin! After you've had your introduction to Alta Recovery Vault and want to start finding out more about the product and service, take a look here: Start With: Veritas Alta Recovery Vault: Setting up Immutable Storage Part 1 of 2 https://youtu.be/r0emXtBHKMM?si=uBaP6AzEnqmO-IVi Veritas Alta Recovery Vault: Backup, Recovery, and Expiring Immutable Storage Part 2 of 2 https://youtu.be/DaVvfo8qlKs?si=IF2oJlMFoaMTKgGd Alta Recovery Vault Short Lived Token Based Authentication Overview https://www.youtube.com/watch?v=1Oj_Dk5hsF4 1.Overview of Alta Recovery Vault. 2.How to setup your storage. 3.Perform a backup. 4.Attempt to expire the immutable backup that fails. 5.Successful recovery using the offsite storage. 6.How Veritas uses token-based authentication. 7.Creating a credential with the new token. Now comes the security questions that you and your Network team will have. Alta Recovery Vault Security Guide https://www.veritas.com/content/dam/www/en_us/documents/white-papers/WP_veritas_alta_recovery_vault_security_V1537.pdf 1.Overview of Alta Recovery Vault security. 2.What are tokens and why we use them. 3.NetBackup security fundamentals as they pertain to ARV. 4.Data Deletion. 5.Proxies and using connection methods other than HTTPS. After your security questions have been answered, you might want to use something other than HTTPS to connect to your offsite storage so. Alta Recovery Vault Azure ExpressRoute Overview https://www.veritas.com/content/dam/www/en_us/documents/white-papers/WP_recovery_vault_expressroute_overview_guide_V1925.pdf Alta Recovery Vault AWS Direct Connect https://www.veritas.com/content/dam/www/en_us/documents/white-papers/WP_veritas_alta_recovery_vault_aws_direct_connect_overview_guide_V1984.pdf 1.Overview of what the Azure and AWS private connection solutions are. 2.Recommended setup guidelines to reproduce Veritas certification testing. 3.Overview of the Veritas architectures used to connect to the Cloud Service Provider’s private connections. 4.Veritas Alta Recovery Vault backup and test results. Now that you've educated yourself on how Alta Recovery Vault works and your Network and Security team have the answers they need it's time to move to the Deployment Guide. Alta Recovery Vault Pre-Install Checklist https://www.veritas.com/content/dam/www/en_us/documents/technical-documents/TD_alta_recovery_vault_pre-install_checklist_V2120.pdf 1.Questionnaire to prepare for Alta Recovery Vault. 2.Pre-Requisites like patches, ports, etc. Alta Recovery Vault Deployment Guide https://www.veritas.com/support/en_US/doc/VeritasAltaRecoveryVaultGuide 1.Overview of what Alta Recovery Vault is. 2.Pre-Requisites. 3.Patches required. 4.Where to download the software. 5.Covers all supported versions of NetBackup. 6.How to: 1.Create a credential. 2.Connect to the storage. 3.Create a storage unit. 4.Create a policy. 5.Backup data. 6.Restore data. 7.Migrate from access key to token support. 8.Storage reporting on Alta Recovery Vault from Alta View. Alta Recovery Vault is great, but you want to use it for disaster recovery so you can restore your backups from anywhere! Alta Recovery Vault Image Sharing and Disaster Recovery https://www.veritas.com/content/dam/www/en_us/documents/technical-documents/TD_netBackup_recovery_vault_data_recovery_V1573.pdf 1.What is Image Sharing and a Cloud Recovery Server(CRS)? 2.How to setup Image Sharing with Alta Recovery Vault. 1.Using a newly created Primary or CRS. 2.Create a new credential to access the offsite storage. 3.Import the storage. 4.Restore the backup image from the offsite storage. And sometimes things just don't go like they're supposed to and that's when it's time for you to look at the Alta Recovery Vault Troubleshooting Guide: Alta Recovery Vault Troubleshooting Guide https://www.veritas.com/content/dam/www/en_us/documents/technical-documents/TB_alta_recovery_vault_troubleshooting_guide_V2111.pdf 1.Ensure all pre-requisites for connectivity have been met. 1.Ports opened? 2.EEBs applied? 3.Communication to storage and Veritas confirmed? 4.Common errors and where to find logs. And just to make things easier. Here are all of the Alta Recovery Vault Guides: Alta Recovery Vault Deployment Guide https://www.veritas.com/support/en_US/doc/VeritasAltaRecoveryVaultGuide Alta Recovery Vault Security Guide https://www.veritas.com/content/dam/www/en_us/documents/white-papers/WP_veritas_alta_recovery_vault_security_V1537.pdf Alta Recovery Vault Image Sharing and Disaster Recovery https://www.veritas.com/content/dam/www/en_us/documents/technical-documents/TD_netBackup_recovery_vault_data_recovery_V1573.pdf Alta Recovery Vault Azure ExpressRoute Overview https://www.veritas.com/content/dam/www/en_us/documents/white-papers/WP_recovery_vault_expressroute_overview_guide_V1925.pdf Alta Recovery Vault AWS Direct Connect https://www.veritas.com/content/dam/www/en_us/documents/white-papers/WP_veritas_alta_recovery_vault_aws_direct_connect_overview_guide_V1984.pdf Alta Recovery Vault Troubleshooting Guide https://www.veritas.com/content/dam/www/en_us/documents/technical-documents/TB_alta_recovery_vault_troubleshooting_guide_V2111.pdf And here are all of the Alta Recovery Vault videos: Veritas Alta Recovery Vault: Setting up Immutable Storage Part 1 of 2 https://youtu.be/r0emXtBHKMM?si=uBaP6AzEnqmO-IVi Veritas Alta Recovery Vault: Backup, Recovery, and Expiring Immutable Storage Part 2 of 2 https://youtu.be/DaVvfo8qlKs?si=IF2oJlMFoaMTKgGd Alta Recovery Vault Deployment Demo Azure https://www.youtube.com/watch?v=e_cR89y7Drk Alta Recovery Vault Deployment Demo AWS https://www.youtube.com/watch?v=oxMoS1E2xKI Creating an Alta Recovery Vault Storage Bucket on Azure https://www.youtube.com/watch?v=5eRy7f1p6qc Creating an Alta Recovery Vault Storage Bucket on AWS https://www.youtube.com/watch?v=HNr9uWOfRU4 Alta Recovery Vault Short Lived Token Based Authentication Overview https://www.youtube.com/watch?v=1Oj_Dk5hsF4
NetBackup Occupancy per Object
Hello everyone, i have a question, I’m searching for a REST-API endpoint, where I can get the occupancy of backup objects. In the Netbackup Dashboard, I get the current used size group by type (VMWare, Microsoft SQL, Postgres) but I want the information pro vm or database. So i can see the vm docker01 used 4.57GB, file01 use 67GB or the database “app” on sql server sql01 use 4.2GB. Currently i use the Endpoint /catalog/images where i get the information for every backup task, with the expiration of the backup. But if I summarize all images in the expiration date I get different results as if I use the Netbackup dashboard. Thanks
