12-16-2008 07:02 PM
12-17-2008 09:32 AM
Just guessing here I think you are running a solaris backup which stores the swap memory under /tmp if this file system is full then there is no swap, which means that your backups will fail and almost everything, but because there is not much data I can be wrong with this guess
regards
12-17-2008 06:42 PM
I agree with Mr Omar for Solaris, but in this case we use HP-UX.
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1032192 468064 561136 45% /
/dev/vg00/lvol1 298928 109224 159808 41% /stand
/dev/vg00/lvol8 4718592 1460760 3234208 31% /var
/dev/vg00/lvol6 2048000 1328408 714520 65% /usr
/dev/vg04/lvol1 614400000 298236592 313693640 49% /usr/openv
/dev/vg00/lvol5 212992 101992 110344 48% /tmp
/dev/vg05/lvol2 30720000 6387360 23952512 21% /report
/dev/vg00/lvol7 5242880 1709800 3506560 33% /opt
/dev/vg00/lvol4 212992 58872 152968 28% /home
Any solution?.
Thanks
Zainal
12-18-2008 05:30 PM
what else are u getting? not enough space is not much info, we can start with the bpcd and bpbkar logs in the client side, also the bptm on the media server, change the verbose to 5 on client and media then we can see where is failing and why.
regards
12-18-2008 06:21 PM
Sorry the 1st question was edit.
I want patch my master server (the pacth I hope will be resolve the daemon down).
From file pack.history:
tar failed unpacking client_bin.tar.Z on master server.
Cannot complete the client install.
Installation of pack NB_CLT_60_7_M FAILED Wed Oct 10 08:22:43 wib 2008 Rev. 1.33.10.18.
Failed because /tmp is 100% the source patch file in the another mount point / directory . Would I changes working directory another /tmp.
Regards
Zainal