Welcome to your hub for enterprise data protection discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
Image Cleanup - error 2027
Hello! At the moment, we periodically receive a massive error - (2027) The media server is not active. Image Cleanup performs correctly in the vast majority of tasks. Job Type - Image Cleanup ...... Apr 26, 2025 6:13:10 AM - Info nbdelete (pid=9992) deleting expired images. Media Server: media4003 Media: @aaaeE Apr 26, 2025 6:13:10 AM - Error nbdelete (pid=9992) Cannot obtain resources for this job : error [2027] Apr 26, 2025 6:13:10 AM - requesting resource @aaaeE Apr 26, 2025 6:13:10 AM - Error nbjm (pid=8046) NBU status: 2027, EMM status: Media server is not active Apr 26, 2025 6:13:10 AM - Error nbjm (pid=8046) NBU status: 2027, EMM status: Media server is not active Media server is not active (2027) .............. Apr 26, 2025 2:12:31 AM - Info nbdelete (pid=10762) deleting expired images. Media Server: media4003 Media: @aaaeM Apr 26, 2025 2:12:31 AM - Error nbdelete (pid=10762) Cannot obtain resources for this job : error [2027] Apr 26, 2025 2:12:31 AM - requesting resource @aaaeM Apr 26, 2025 2:12:31 AM - Error nbjm (pid=8046) NBU status: 2027, EMM status: Media server is not active Apr 26, 2025 2:12:31 AM - Error nbjm (pid=8046) NBU status: 2027, EMM status: Media server is not active Media server is not active (2027) .............. Please tell me what to do, I haven't really found any information on this error, only special cases that don't fit my case.
Netbackup CDP problem
Hi I have Netbackup 10.5.0.1 on RHEL 8.10 my media server is msdp and cdp gateway with same version of netbackup and os I installed io-filter on esxis, vcenter is 8.0.3 and esxi is 7.0.3 I created vtstap storage policy, but it's incompatible with san datastores (vmfs 5 and 6) and compatible with local datastore I tried with 2 vm, one is stored on local and other in san attached these vm with vtstap storage policy and shows both of them are compliant in storage policy then I created a protection plan for these assets and attached cdp gateway, when finish it, it says for 2 vm: List of trusted Certificate Authorities could not be fetched operation failed for VM id ... of CDP host ...
Malware Scanning Configuration | Windows Server
Dear all, I`m somewhat confused from the documentation about this and to this date, I was not able to get malware scanning working. Our environment: - Master+Media server windows 2019 (same physical machine, BYO device) - local storage for disk backups - Attached Tape Library for tape backups - NBU 11.0 Desired functionality: Backup to Disk -> Scan if certain anomaly score is detected (e.g. medium) -> stage to tape -> expire Image on disk As a first step, I wanted to setup malware scanning to scan images manually without luck. In some way, all routes seems to end up in a "you need Linux or an appliance" way. Unfortunately, I`m forced to use only windows machines at this moment. What I did: - setup MSDP for local storage (storage server, storage pool, storage disk) - created a 2nd VM as Scan Host (windows server 2022), deployed NBU malware scanner and poweshell script "setting up windows server as scan host" as described in the documentation + netbackup client - configured a scanpool using "Netbackup client communication", nbu scanner and SMB - created a SMB share on a random folder on master/storage server Where I struggle: Where/how do I configure the share on netbackup webUI? Is this even possible? My current understanding is, that "Universal Share" feature is needed, which is reserved for Linux. Is there a way to use Malware Scanning Feature on a fully windows server environment with BYO devices? Thank you in advance! Marco
(69) invalid filelist specification
Buenos días. Me sale el siguiente error cuando se ejecuta una política tipo VMware Apr 22, 2025 6:00:26 PM - begin Application Resolver:Policy Execution Manager Preprocessed Apr 22, 2025 6:00:27 PM - Error nbpem (pid=140959) Two or more backup components with the name masteropenshift were found with conflicting information Apr 22, 2025 6:00:27 PM - Error nbpem (pid=140959) backup of client masterbk02 exited with status 69 (invalid filelist specification) Apr 22, 2025 6:00:27 PM - Error nbpem (pid=140959) Two or more backup components with the name masteropenshift were found with conflicting information Operation Status: 69 Apr 22, 2025 6:00:27 PM - end Application Resolver:Policy Execution Manager Preprocessed; elapsed time 0:00:01 Apr 22, 2025 6:00:27 PM - begin Application Resolver:Stop On Error Operation Status: 0 Apr 22, 2025 6:00:27 PM - end Application Resolver:Stop On Error; elapsed time 0:00:00 Operation Status: 69 Apr 22, 2025 6:00:27 PM - end Parent Job; elapsed time 0:00:04 invalid filelist specification (69) Que validaciones puedo realizar puesto que reviso en Vcenter y no encuentro alguna anomalidad. Muchas gracias, quedo atentaLocal account vs Service account for DNAS protection
Hi, I was interested to hear from the community as to if people tend to use local accounts or service accounts when it comes to configuring snapshot style protection for DNAS backups? Previously when we used ndmp we obviously had to use local accounts that were local to the storage array but we want to test moving away from NDMP to DNAS and as such it seems you can give it either local or domain based user so long as it has sufficient rights on the storage array. So what do people tend to use and for what reasons? Thanks in advance for any opinions/info
DR server for production master server.
We have netbackup 10.1 physical master server and we want to create a DR server for it. Can some one suggest how to create a DR physical server for our master server and it is also acting as media server too. can we restore the catalog using different server name or we need to keep the DR server name also same as production server. if same name should we bring down the prod and then do restore to bring up the DR and then shutdown DR. and use only for DR purpose and currently no backups are running in it and it is kept only for old legacy restores.
