Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Status code 1

Created: 25 Oct 2012 • Updated: 05 Nov 2012 | 2 comments
This issue has been solved. See solution.

HI,

I am facing status code 1 on one of our clients.

10/23/2012 07:26:05 - Error bpbrm (pid=28260) from client xxxxx: ERR - File /etc/bizimp/stats/20110826-stats.db shrunk by 8613888 bytes, padding with zeros
10/23/2012 07:37:26 - end writing; write time: 0:20:01
10/23/2012 07:37:35 - Error bpbrm (pid=28260) from client xxxxx: ERR - File /home/cbinder/upgradebadstatsfiles/20110219-stats.db shrunk by 2199552 bytes, padding with zeros
the requested operation was partially successful  (1)

This is a RedHat Linux 2.6 Client NBU 6.5.6, media server 6.5.6 , master 7.0.1 . I did some research and found these errors occur if there is change in file size before and while running the backup .

I am not clear on what padding with zeros is reffering to.

This client serves as a  temporary staging area for in & out going messages between our mailbox servers and customers.

What is the best approach to troubleshoot this .

thanks ,

rajesh

Comments 2 CommentsJump to latest comment

Mark_Solutions's picture

This tech note covers some ideas : http://www.symantec.com/docs/TECH57850  but you may have already seen that one

In effect you cannot rely on that file being of any use if you needed to restore it.

It it always happens with the same file then it may be corrupt so a disk check may be in order

If it happens with a variety of files then you may need to see what your system is doing - on Sun Solaris there was actually a patch to fix this behavoir so it is not considered as normal

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
Nicolai's picture

Addition to Mark's fine post. I agree with Mark - this type of message usally mean somthing is wrong. But if files do live very short on the server (minutes or seconds) then consider to exclude the staging area from the file system backup. 

Technote 3060 contain instruction for setting up a exclude list.

http://www.symantec.com/docs/TECH3060

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.