Welcome to your hub for enterprise data protection discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
Community Event: A conversation with Aditya Vasudevan, leader of Cohesity’s Cyber Event Response Team
When a cyber incident strikes, knowing who to call—and what to expect—can make all the difference. Join us on June 4 from 8:30–9:30 AM PDT for an exclusive session with Aditya Vasudevan, leader of Cohesity’s Cyber Event Response Team (CERT). Aditya will walk through how CERT operates during a cyber incident, share real-world examples, highlight key trends, and answer your questions live. We’ll then close with a community roundtable to discuss what’s next for Cohesity’s community programs. Hope to see you there! Learn more and register now: https://cohesity.co/3GYA9GU
Catalog Backup - disk capacity
Hello, I started receiving errors in the NetBackup program because there isn’t enough space on the CatalogBackup (F:) drive on my server (Windows Server 2016). Before performing the following steps, I will stop the services related to the NetBackup program! What I want to do is create a new 2 TB partition from the 8 TB disk on the server, name this partition CatalogBackup, and assign it the drive letter F:. After that, I will move the 558 GB of data from the old F: drive to the new one. I believe NetBackup won’t have any issues as long as it detects a drive named CatalogBackup with the letter F:. ! I will free up space LOCAL DISK E:
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.New NetBackup 10.5 Plug-In Gives DNAS Protection to Azure Files
A new plug-in allows NetBackup 10.5 to protect Azure Files as if it was a NAS filer. It does this through the new NetBackup Snapshot Manager (NBSM) NAS plug-in for Azure Files. NBSM uses Azure’s Software Developer Kit (SDK) storage API to connect with and move data to/from Azure Files. You can select this plug-in like all the other NetBackup plug-ins as shown below. The new plug-in can use Network File System (NFS) and Server Message Block (SMB) protocols to access Azure Files data. This lets you select the protocol(s) that meet your organization’s transport and security requirements. As of SMB version 4.X, NFS has a slight performance advantage over older SMB versions. See the NetBackup™ Snapshot Manager Install and Upgrade Guide version 10.5 for detailed plug-in installation and configuration instructions. NetBackup Snapshot Manager (NBSM) establishes a connection with Azure Files Storage using the REST client. It then discovers whatever resource groups, storage accounts, file shares, and file share snapshots are available. This discovery gives NetBackup 10.5+ the following Azure File snapshot operations: Creating file share snapshots Exporting snapshots Restoring snapshots Deporting snapshots Deleting snapshots A NetBackup Storage Lifecycle Policy (SLP) is required to run the snapshot and call a NAS-Data-Protection policy to coordinate the backup. The new Azure Files plug-in also offers the same great DNAS features available in previous versions. See these links for more information on these features: My DNAS backup tech paper: NetBackup Dynamic Network Attached Storage (DNAS) Filer Protection Version 10.4 Update: NetBackup 10.4+ DNAS Multi-Mount Capability Greatly Improves Snapshot Backup Performance
Storage unit media server option
I have flex appliance 5260 2EA and each appliance has a storage shelf connected to it. I created a master/media server on appliance A and only configured a media server on appliance B and connected them to each other with a fiber cable. I created a storage unit with msdp and checked "Use any available media server" and "only use the following media server" among the options. I created msdp1 on media server A and msdp2 on media server B. I checked the "Use any available media server" option in the msdp1 storage unit settings and found that both A/B media servers work when backing up and the data goes to msdp1. Is it okay to use the use any media server setting like this? How do you use it in normal cases?(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 atenta
