We are moving to the Cohesity Community! The Cohesity Community is a private space where members come together to connect, learn, and solve problems. Learn more about the transition here.
Forum Widgets
Recent Discussions
How to backup MySQL using NBU 11
Hi everyone, I am trying to configure the protection for one MySQL instance, but I am getting stuck. I have followed the NetBackup™ for MySQL Administrator's Guide, but it doesn't help at all. The backup job still results in status code (6) The backup failed to back up the requested files. Here are all the configuration I have made: - In /etc/my.cnf, I added theses line [mysqld] port=3306 datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock log-error=/var/log/mysql/mysqld.log pid-file=/run/mysqld/mysqld.pid - I created symbolic link: ln -s /usr/bin/mysql /usr/libexec/mysql - I successfully created a credential for mysql instance and a protection plan. I also discovered all the databases in the instance The log indicates that ERR - MySQL library path is not present, but I don't know to how make the NetBackup Agent where to find the MySQL library path. Did I miss any configuration steps ? Can you help me debug this problem ?
Problems with backup VM
Hi! We have NetBackup 7.6.1.1. The specialists reassembled the VM VMware vCenter Server 6.0.0 as a result of the crash of the latter. To work with NetBackup, I created an account in VMware and gave it Administrators rights in vCenter and local administrators rights. I made the appropriate settings in NetBackup. However, the jobs that previously worked successfully now end with an error.: the backup failed to back up the requested files (6) When completing tasks, I observe that the task of creating a snapshot is being started. I see that a snapshot is being created. But then an error is issued. I see it in the backup task log: Error bpbrm(pid=6624) from client VM name: ERR - Error opening the snapshot disks using given transport mode: san:hotadd:nbd:nbdssl Status 23 the backup failed to back up the requested files (6) I tried with other modes of transport, but I get the same error.: Error bpbrm(pid=9256) from client VM name: ERR - Error opening the snapshot disks using given transport mode: nbd:san:hotadd:nbdssl Status 23 Error bpbrm(pid=7304) from client VM name: ERR - Error opening the snapshot disks using given transport mode: hotadd:nbd:san:nbdssl Status 23 What is the reason for the error? What am I missing?PostgreSQL and NBU11.1
Hello, i'm trying to configure the PostgreSQL workload protection using a protection plan and pgbackrest in a 11.1 domain but i can't find any guide about this. Also the PostgreSQL guide doesn't help, it mentions an universal share but doesn't tell anything about its configuration in the client. I've created the share, exported it to the db host, installed the agent, discovered the databases and validated the credentials. What am i missing? Thank you, regards,
Seeking NetBackup Developer for Paid Engagement
Hello and thank you for reading, community. I am in the early stages of a strategic development project and need to engage a skilled NetBackup developer. We are actively looking for a proficient NetBackup professional to assist with enterprise-grade development work. We are seeking a long-term professional relationship with the right candidate. Please respond below or reach out directly if you know someone interested.
Issues restoring old Symantec Backup Exec 2014 server config onto new Backup Exec server.
Hello Symantec/Veritas tech community, I've been searching for an answer to this issue for over 3 weeks now.... Are there any specific steps, aka checking for old Backup Exec server references, or other tips/tricks you can send along please? I'm looking for a checklist or order of steps that works. From our old Symantec Backup Exec 2014 server --- Restore of BEDB SQL Full/Incr backups successful, with no issues, and service account from Backup Exec is a sysadmin and DB owner in SQL Db. -- No media, associated sets, clients, or jobs configs show from old server config. I do see old clients that were part of backups. Does the new Backup Exec server need to be exactly the same name and version to restore the media attributes/config? Any help would be greatly appreciated! Thank you,
How to restore data by inserting existing LTO5 media into an LTO7 drive.
Hello. I'm curious about the process, so I'm posting this to ask for some help. I have a NetBackup appliance connected to two tape libraries: TLD(0): SL150 with four LTO-5 drives TLD(1): TS4300 with LTO-7 and LTO-8 drives In the NetBackup GUI → Device Monitor, the following drives are shown as UP: 4 × LTO-5 drives 1 × LTO-7 drive 3 × LTO-8 drives both LTO5 and LTO7 are HCART2 types. LTO8 are HCART3 types. As far as I understand, data backed up on LTO-5 media should be readable/restorable using an LTO-7 drive I want to restore data backed up on SL150 LTO5 drives to TS4300 LTO7 drives. What is the restore process?
Duplication of small images into MSDP-C takes longer time as usual
Hello, I have a serious performace issue with duplication of many images to an MSDP-C pool. NetBackup 10.5.0.1 is duplicating images to the MSDP-C pool at an on-premise S3. There are about 600 backup images created per hour. The duplication jobs cannot process this number at the same rate, although several dozen of them are running simultaneously. The problem is not in the volume of data - the vast majority of images are database log backups of tens of kB to several MB in size. The problem is that the duplication of even the smallest image takes several minutes. An example: duplicating one image of 670 kB took an incredible 14 minutes. I see large delays between individual actions in the job details. Please see details of the duplication of this image below. The media server's HW resources are under-loaded. As long as a small number of images were duplicated per hour, duplicating individual images took an average of 2 minutes - that was fine. What is the cause of the slowdown and how can I eliminate the cause? Thank you, Lubos Example of a duplication job details with long delays: 26. 6. 2025 10:02:53 - Info bpduplicate (pid=125788) The data-in-transit encryption (DTE) is disabled, as the global DTE mode is set to 'Preferred Off' 26. 6. 2025 10:02:53 - Info bpdm (pid=3633773) started 26. 6. 2025 10:02:53 - started process bpdm (pid=3633773) 26. 6. 2025 10:02:53 - requesting resource @aaaaw 26. 6. 2025 10:02:53 - granted resource MediaID=@aaaaw;DiskVolume=PureDiskVolume;DiskPool=Pool4;Path=PureDiskVolume;StorageServer=MediaServer1.x.y;MediaServer=MediaServer1.x.y 26. 6. 2025 10:02:54 - Info bpdm (pid=3633773) requesting nbjm for media 26. 6. 2025 10:03:37 - begin writing 26. 6. 2025 10:03:37- end writing; write time: 0:00:00 26. 6. 2025 10:06:08- begin writing 26. 6. 2025 10:06:08 - Info bpdm (pid=3633773) Waiting for storage server MediaServer1.x.y, disk volume PureDiskVolume 26. 6. 2025 10:07:08 - Info bpdm (pid=3633773) Transferred 688937 bytes, to storage server MediaServer1.x.y, disk volume PureDiskVolume 26. 6. 2025 10:08:08 - end writing; write time: 0:02:00 26. 6. 2025 10:08:44- Info MediaServer1.x.y (pid=3633773) StorageServer=PureDisk:MediaServer1.x.y; Report=PDDO Stats for (MediaServer1.x.y:PureDiskVolume): scanned: 672 KB, CR sent: 25 KB, CR sent over FC: 0 KB, dedup: 96.3%, cache disabled, where dedup space saving:0.0%, compression space saving:96.3%, new transferred data unencrypted 26. 6. 2025 10:17:08- Info bpdm (pid=3633773) EXITING with status 0A New Chapter for the VOX Community
For years, Veritas Open Exchange (VOX) has been a place where members exchanged knowledge, solved problems, and shared expertise. We’re deeply grateful for all of you and the contributions you’ve made that helped make VOX a trusted resource for NetBackup and all Veritas products. Starting January 29, VOX will move to read-only mode. Cohesity-related content from the past decade will be migrated into the new Cohesity Community, a dedicated space to connect, learn, and solve problems together. The Cohesity Community will be available beginning mid-February. To access the Cohesity Community, you can login by going directly to https://community.cohesity.com and using your MyCohesity credentials or by visiting your MyCohesity dashboard and selecting the “Cohesity Community” tile. Please note that this community will only be accessible for Cohesity customers, partners, and the Cohesity Team. About the Cohesity Community The Cohesity Community includes enhanced capabilities to make collaboration easier and more rewarding. Enhanced features include AI-powered search, modern UI, customized notification and engagement prompts, cleaner content organization, and more! This new community is designed to be collaborative, dynamic, and aligned with how you want to connect. To preserve the knowledge created on VOX, Cohesity-related VOX content will be available in the new community. This content will appear as an anonymous archive to support fresh discussions and ongoing engagement. Looking Ahead We’re proud of what VOX has been and even more excited about what’s ahead. The Cohesity Community represents the next evolution of our shared commitment to knowledge, connection, and innovation. We can’t wait to see you in the Cohesity Community! If you have any questions regarding the transition, please reach out to the Cohesity Community team at community@cohesity.com
NetBackup Windows Compatibility
Hi All - long time since I popped onto here! I have a customer who needs to upgrade their hardware to Windows 2025 from Windows 2016. They are currently running NetBackup 10.5.0.1 Primary and Media Server, all on Windows 2016. SORT and the compatibility lists all just say 11 is the minimum version for every OS which I know is not the case so I just need to be sure that I can happily upgrade the Windows 2016 servers to NetBackup 11 before upgrading their OS to 2025 as I believe they have to be at NBU 11 to go to Windows 2025. If there are any "Got-YAs" with NBU 11 it would be good to know too as we don't want anything to stop working after the upgrade. Thanks All Mark
