1833802 Members
2235 Online
110063 Solutions
New Discussion

Re: Backup failure

 
SOLVED
Go to solution
so_2
Regular Advisor

Backup failure

Hi All

I am taking a backup using the below command
fbackup -0 -I ${logtmp} -v -f /dev/rmt/0m -g ${home}/graph
And
${home}/graph=i /
e /data1
e /data2
e /data3
e /data4
e /ai1
e /bi1
e /bi2
e /progress
e /applfs
e /cdrom
.
The backup starts and progress for a long time and after it fails with the following error.

358743: /zrecovery/data4/markp/fcstuff/patches/N_class/PHCO_21187 42934
358744: /zrecovery/data4/markp/fcstuff/patches/N_class/PHCO_21187.depot 39920
358745: /zrecovery/data4/markp/fcstuff/patches/N_class/PHCO_21187.text 405
358746: /zrecovery/data4/markp/fcstuff/patches/N_class/PHCO_23651 1025
358747: /zrecovery/data4/markp/fcstuff/patches/N_class/PHCO_23651.depot 1020
358748: /zrecovery/data4/markp/fcstuff/patches/N_class/PHCO_23651.text 31
fbackup(3003): normal EOT
fbackup(3310): enter '^[yY]' when volume 2 is ready on /dev/rmt/0m,
or '^[nN]' to discontinue:
fbackup(3004): writer aborting
fbackup(1002): Backup did not complete : Reader or Writer process exit

The same error is happening for last 3 days. I suspect it as a drive problem.
Do any one of you gurus adivise me to confirm the problem?

Thnaks
S.O


5 REPLIES 5
Michael Steele_2
Honored Contributor
Solution

Re: Backup failure

Clean the tape drive.

Check syslog for errors.

Check LOGTOOL for errors. STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > RAW SUMMARY

Check etc/opt/resmon/log for errors
Support Fatherhood - Stop Family Law
Torsten.
Acclaimed Contributor

Re: Backup failure


Consider the tape is simply full.

What kind of tape you are using?

But the reason could also be dirty or bad tape/drive. Have a look into the syslog for I/O errors.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Peter Godron
Honored Contributor

Re: Backup failure

Hi,
looking at the number of files being backed up (> 350000) I would first check how much data you are trying to back up.

cd /
du -sk *
then eliminate your graph exclusions from this list and add up the datasizes.
Compare this to your tape capacity.

If the backup has worked in the past, check for large new files, but also check your tapedrive is still set to compress.
so_2
Regular Advisor

Re: Backup failure

total size from / =58378211
exclude file size is =52682918
total size to be backed up=5695293
Drive using is Quantum DLT 4000

I hope there are no problem with the size of the files backed up.
So I can think of cleaning the drive now or replacing?

Your final advice to conclude?
Thanks for all who replied and points have been assigned.






V. Nyga
Honored Contributor

Re: Backup failure

Hi,

normally, if you get a EOT, then you put in a new tape, type 'y' and the backup continues.
If fbackup has to wait too long for the answer, then it aborts (fbackup(3004): writer aborting) and of course the backup is incomplete.

The messages you see indicates in thefirst step no drive problem, check your logfile, if you backup more than you think.

And which tape do you have in your drive?

HTH
Volkmar
*** Say 'Thanks' with Kudos ***