Catalog Backup says disk is full.....it's not
Updated: 21 May 2010 | 5 comments
This issue has been solved. See solution.
I have a hot catalog backup policy that is set to do a full once per week and cumulative incrementals the remaining days. The retention is (was) 7 days. The policy backs up to a disk storage unit. I received a disk full error so i changed the retention to 3 days and expired all the catalog backups that i can find. There is virtually nothing on the disk (lots of space) and I continue to get status 129 errors when trying to manually run the full catalog backup.
software version 6.0 MP4 on Windows.
discussion Filed Under:
Comments
Catalog size and the highwater mark on the DSU
What's the catalog size, and how much free space do you have in the DSU?
Also check the highwater mark set on the DSU.
Restarting NBU services is also a good idea, sometimes deleted files still hold the space until they are flushed out.
bpdm/bptm debug log are also useful to find out why it's saying disk is full - with the maximum verbosity set for the logging ... together with admin debug log it'll be even more helpful
*Edit*
Would you like to post the output of "bppllist policyname -L" command and "bpstulist -L" command?
They are both under <install_path>\NetBackup\bin\admincmd
Abe
Anger Management
Check free disk space where Netbackup is installed
Check free space on the drive where Netbackup is installed. When a catalog backup is performed Netbackup copy the databse from directory "data" to directory "stage" (Sorry Can't be path specific, I have only UNIX master servers). If the drive run out of space during that process I guess you will get a 129 as well.
Regards
Nicolai
Assumption is the mother of all mess ups.
If this post solved you’re questions please send a gratitude by marking it as a solution.
Double check the Path under Disaster Recovery
Dustin-
You also may want to double-check if you have a Disaster Recovery path defined. The job may throw a 129 if this location is full as well.
I was seeing this same behavior, and this turned out to be the problem.
-Cory
Thanks for all the replies.
Thanks for all the replies. i'm going to try turning up the logging. There is currently 132gb of free space on the directory that stores the catalog backups as well as the disaster recovery files. There is also 80gb of free space on the volume that hosts the catalog/database files. I have restarted the services and also tried a reboot. If anyone has any more suggestions....feel free. in the meantime i'll try the logging.
I was able to resolve this by
I was able to resolve this by deleting the disk storage unit and recreating it with a slightly different name (just in case). thanks to all who put in suggestions
Would you like to reply?
Login or Register to post your comment.