Netbackup Error 155
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Back up error VOX : Backup and Recovery : NetBackup : Back up error Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Back up error kakaluru Level 4 09-11-2014 03:17 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi My friday back is failed. I have run manual back up. I dont know after successful completion of 80% i am getting below error. Error bpbrm(pid=4192) db_FLISTsend failed: disk is full (155) Error bpsched(pid=2608) suspending further backup attempts for client 192.168.30.12, policy tuiodcfull, schedule Weeklyfulllfriday because it has exceeded the configured number of tries Error bpsched(pid=2608) backup of client 192.168.30.12 exited with status 155 (disk is full) I have free tapes in my pool.Kindly help me. Solved! Go to Solution. Labels: 7.1.x and Earlier Backup and Recovery NetBackup Troubleshooting Windows Server (2003-2008) 0 Kudos Reply 2 Solutions Accepted Solutions Accepted Solution! Check the media server and RonCaplinger Level 6 09-11-2014 08:49 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Check the media server and ensure the drive where NetBackup is installed is not full. I'm thinking you have logging enabled and turned up too high on your media server, and the backup job is failing because the media server has no space left to write the next log entry. If the pro
can't find a proper description from support.veritas.com.Only one drive of this server causes the problem. It's a Citrix XP Terminal Server running Windows 2000 SP3. The drives does not contain the OS and is only 50% full.TIR and VSP are enabled in he policy. The initial size of the VSP cache file is 400MB no upper limit. I already checked the access rights of this volume. Everything looks fine.Backup System: Netbackup Datacenter https://vox.veritas.com/t5/NetBackup/Back-up-error/td-p/692440 4.5 FP6 with latest patch running on Windows 200018.02.2004 08:42:30 - mounting NNW26918.02.2004 08:42:31 - started process bpbrm (3200)18.02.2004 08:42:31 - connecting18.02.2004 08:42:31 - connected; connect time: 00:00:0018.02.2004 08:43:09 - mounted; mount time: 00:00:3918.02.2004 08:43:10 - positioning NNW269 to file 26818.02.2004 08:43:35 - positioned; position time: 00:00:2518.02.2004 08:43:35 - begin writing18.02.2004 http://veritas-bu.mailman.eng.auburn.narkive.com/7oP1GjIb/backup-of-client-xxxxxx-exited-with-status-155-disk-is-full 08:56:35 - Error bpbrm(pid=3116) from client XXXXXX: ERR - failure reading file: P:\data\install\1100_W2k_Multi_Language_CD3\EL.MUI\I386\ECONNECT.CN_ (WIN32 5: Access is denied. )18.02.2004 08:56:39 - Error bpbrm(pid=3116) from client XXXXXX: ERR - VSP Error:0x000003e7 (WIN32 999: Error performing inpage operation. )18.02.2004 08:56:39 - Error bpbrm(pid=3116) from client XXXXXX: ERR - VSP Error while reading file: P:\data\install\1100_W2k_Multi_Language_CD3\EL.MUI\I386\ECONNECT.CN_18.02.2004 08:56:39 - Critical bpbrm(pid=3116) from client XXXXXX: FTL - Backup operation aborted!18.02.2004 08:56:41 - end writing; write time: 00:13:0618.02.2004 09:00:52 - Error bptm(pid=3020) read of TIR file failed: the file list is incompletedisk is full(155)18.02.2004 09:00:53 - Error bpsched(pid=2020) suspending further backup attempts for client DE060011, policy PW_W2K_FILE_001_STD_TS, schedule SC_W2K_FILE_STD_FULL_W because it has exceeded the configured number of tries18.02.2004 09:00:53 - Error bpsched(pid=2020) backup of client XXXXXX exited with status 155 (disk is full)Thanks in advanceMartin Falk Coco, Samuel (Cont, ARL/CISD) 2004-02-18 12:56:41 UTC PermalinkRaw Message The disk may not be full - but how about the /tmp or cache area?Sometim
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified http://www.tek-tips.com/viewthread.cfm?qid=944945 Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: netbackup error jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: NetBackup Forum db_FLIST send failed exit 155 disk is full thread776-944945 Forum Search FAQs Links MVPs netbackup error 155 db_FLIST send failed exit 155 disk is full db_FLIST send failed exit 155 disk is full OHWS (TechnicalUser) (OP) 2 Nov 04 15:45 I am currently running Netbackup 4.5fp6 on a HP-UX master/media servers.Client is a NAS device running 4.5fp6.I recieved this error during last nights incremental run.I only recieved this error on F: drive.All of the other drives backed up without issue.Had the admin check the space on F: and there is plenty of space on the drive in question.Is this error due to a logging directory being full?? RE: db_FLIST send failed exit 155 disk is full OHWS (TechnicalUser) (OP) 2 Nov 04 16:05 Additional info:I have checked the logging directories on the master server and media server to make sure they are not full.Also noteworthy is the fact that we are converting all of our images from an optical jukebox over to this drive with a job that runs all the time.Veritas site states that this error could be caused by AntiVirus,Disk Frag,Scandisk, and or a highly