A new feature introduced in NetBackup 7.1 can cause NDMP backup failures. The Append-Only Mode described in this Symantec Tech Note causes the drive to prevent the overwrite of data on a cartridge unless the writing application performs a pre-authorization for the overwrite. This feature is supported on IBM LTO-5 drives with LTO-4 or LTO-5 media. The feature is enabled by default and does not normally cause any issues if all systems accessing the tape device are NetBackup 7.1 Media Servers.
In an NDMP environment, however, the storage device (filer, data mover) writes directly to the tape drives and may not be aware of the pre-authorization requirement. If these drives are shared between the NDMP device and the Netbackup Media Server, write errors occur, represented by a write protect message issued by the NDMP device. This has been observed with an EMC VNX array and EMC support was previously unaware of the Append-Mode feature.
The solution to the problem is to disable Append-Only mode by touching the <InstallPath>NetbackupdbconfigDISABLE_APPEND_MODE on the Netbackup Master Server and restarting the NetBackup Services.
Recently I got this message while trying to install the NetBackup MSEO Security Server on a Redhat Enterprise 5 x64 server:
error: Failed dependencies: libXp.so.6 is needed by mseo-server-6.1.3-rhel5.x86_64
After multiple troubleshooting attempts, we finally we able to get past it by performing an install of the “libXp.so.6” 32 bit binary. We already installed the 64 bit binary (as that is what the operating system was) however we would get the same error during installation of MSEO.
yum install libXp.so.6
And then the install proceeded!
If you get this error when running jobs with NetBackup 7 with deduplication pools and backups fail with status 213, please see this post on the Symantec Connect forum, which I’ve commented on (I post under “squirrelking” 🙂 )
Thanks to the original post on Symantec Connect here:
Are you looking for an easier way to get logs uploaded so you can get your issue resolved as fast as possible? We understand that transferring logs to Technical Support Engineers has been a customer pain point in the past and we’ve addressed this with a new utility called nbcplogs. Nbcplogs will handle the copying, compression, and transferring of logs – all with one easy command.
Using the Titan ID assigned to your support case run the following commands (we’ll use 123-123-123 in place of the actual one you would get from support):
On UNIX-like systems:
% cd /usr/openv/netbackup/bin/support
% nbcplogs -f 123-123-123
Start->Run->Type “cmd”->Press Enter
C:> cd C:Program FilesVERITASNetBackupbinsupport
C:> nbcplogs -f 123-123-123
It’s just that simple!
That command will gather all log files it can find for the last 24 hours on the system it is run on and FTP them to Technical Support.
Just want a specific time frame? Try this (where -s is the start time and -e is the end time) for January 15th at 11:00 pm to January 16th at 4:00 am:
% nbcplogs -s 01/15/2010-23:00 -e 01/16/2010-04:00 -f 123-123-123
For anyone that wants even more fine tuning, start here:
% nbcplogs –help
So that’s easy, but what logs does it actually get? Here’s a list:
* NetBackup Legacy Logs
* NetBackup VxUL (Unified) Logs
* NetBackup OpsCenter Logs
* NetBackup Puredisk Logs
* Windows Event Logs (Application, System, Security)
* PBX Logs
* NetBackup Database Logs
* NetBackup Database Error Logs
* NetBackup Database Trylogs
* Vault Session Logs
* Volume Manager Debug Logs
* VxMS Logs
You can get nbcplogs from the following TechNote:
I ran across this bug onsite at a customer and after some searching, I found out it is a bug that has a hotfix that fixes the issue. It will also be included in NetBackup v7.0.1 which is due out anytime.
Problem: The disk pools available space isn’t being reported correctly, so NetBackup thinks that the disk pool is full and backups to that disk pool results in “Status 129” errors (Disk pool full, insufficent disk space). Even after expiring images, the disk capacity is still full.
Steps Taken: I thought at first that perhaps NetBackup wasn’t “cleaning up” the images appropriately or that perhaps NetBackup was flagging the images to be cleaned but the Puredisk Deduplication Engine (PDDE) wasn’t cleaning up the data correctly, since I’ve seen that issue with standalone Puredisk nodes before. So I performed an expiration and cleanup manually by following the steps below:
Here’s how to manually force the clean up of NetBackup images after expiring them from the catalog:
install_pathNetBackupbinadmincmdnbdelete -allvolumes -force
install_pathNetBackupbinadmincmdbpimage -cleanup -allclient
In Media Server Deduplication Pool environments, wait for PDDE to run its maintenance tasks for cleanup to see the disk space get cleaned.
Or you can run them manually;
install_pathVeritaspddecrcollect -v -m +1,+2 –noreport
Resolution: In my case, manually executing the cleanup didn’t result in additional disk space available. This is a known bug which has a patch that can be downloaded and applied to your Master and Media servers. Please see this technote article: http://seer.entsupport.symantec.com/docs/350190.htm
After applying the patch, the disk pools now show the correct available space and backups are working again!
Here’s a great post which discusses pricing with Backup Exec 2010 and Netbackup 7.
Note, Backup Exec 2010 Trialware is out now. Netbackup 7 First Availability (FA) program is available now, which is the same as the General Availability (GA) code.
Netbackup 7 is now on the Symantec site, with the announcement that General Availability (GA) is: February 1st!
Backup Exec 2010 is also available February 1st! and it’s on the Symantec site as well:
Update – Ready to start upgrading or testing Backup Exec 2010? Symantec has released trialware as of yesterday so you can start before the actual release on 2/1/10.
Symantec’s blog post copied below for your reference, as it has some additional links on it:
Good news! Backup Exec 2010 has launched today with the Trailware available for download from February 1, 2010. The new product encompasses great new features like Deduplication and Unified Archiving. To read the complete list of new features key benefits and to download the trailware, please visit the Backup Exec website.
Have questions on how to upgrade? Please refer to this document that walks you through the upgrade process.
Getting back to Connect, we have created some great information in regards to the new product launch. Here is a video that explains the product’s deduplication feature. Check this Group page for finding all the BE 2010 and BESR 2010 information in one place. Don’t forget to add it to your favourites.
In the process of your upgrade, with any questions, comments, suggestions and great information you are sharing with the community regarding the new product, we encourage you to please make sure to tag the content with the appropriate Version (2010), the Topics (Installation, Upgrade etc) and the public group “BE 2010 and BESR 2010 Launch”. It helps us track the common issues and escalate it to support as needed. (end of symantec blog article)
Here are some great screenshots of some slides discussing some of the new features and enhancements to Backup Exec 2010.