You have a problem there, your root filesystem is full and since its a production server that needs to be up 24/7 you better clean it up.
Look in /var/adm for old log files that you might be able to remove. Check for any core dumps in /var/crash aswell. syslogs can also get big.
If you want to flare the root partition you can not use /tmp as it is only 7GB and you root partition is 10GB.
Use absdata5 or absdata6 as you have 51GB available there.
I just had a look at your first post again..
You were using /var/tmp which is on your root partition, I guess thats why your root partition is full.
If I was you I would cleanup /var/tmp ASAP and in future before trying something like this on a 24/7 production server make sure you know what it is you are doing..
I agree with the others. Root (/) is full and you must clean it up. Check /var/tmp and make sure you clear out old flarcreate files, unneeded temp files (it is a temporary directory; anything not reasonably current should be able to be deleted). Obvious additional choices are /var/adm and /var/log. Check your logs. Make sure they're being rolled (moved daily to something like syslog.0 or syslog.20061227) then make sure they're compressed (looking like syslog.0.gz or syslog.20061227.gz). If they are not being rolled and compressed, check your scripts to get that automatically taken care of. Also remove old log files. That'll depend on company policy. Generally 45 to 90 days is what's used. Next are home directories. Run a du -ks * | sort -n in /export/home or /home depending on your setup. That'll give you the largest directories at the bottom and you can address them for cleanup.
Another issue is your planning on flarcreate. In my location, we use flarcreate to create a bare-metal OS level backup, not a backup of the entire system. So we'll exclude all the oracle file systems for instance. In looking at your setup, you have about 230 GB of data on this system and you're trying to put it all into a filesystem that can have about 8 GB free at best. Regular backups need to be done on the production data and not by using flarcreate. An external tape drive for instance.
Another piece of advice. When posting to the forums, please enclose your output in a code tag (that's the # tag in the bar above your message). It takes the fixed font screen output you have and leaves it fixed font rather than proporational. For example, I whipped up a quick perl script to massage your df -k output:
As you can see, it's a lot more readable this way.
I finished backup of my server only internal disk.
some question is why external disk has error message during backup?
and other message is "too large to archive in current mode" how to avoid this?
This is my log of flarcreate and flar info.
absapp@nepalabs1 # sh volumebackup.sh
WARNING: hash generation disabled when using tape (-t)
Determining which filesystems will be included in the archive...
Creating the archive...
cpio: cpio: absdata1/nccbs_ref.dbf: too large to archive in current mode
cpio: cpio: absdata2/nccbs_app.dbf: too large to archive in current mode
cpio: cpio: absdata2/nccbs_app6.dbf: too large to archive in current mode
cpio: cpio: absdata4/expdat.dmp: too large to archive in current mode
cpio: cpio: absdata6/vol072017.flar: too large to archive in current mode
cpio: cpio: absdata7/nccbs_app_temp.dbf: too large to archive in current mode
cpio: cpio: absindex1/nccbs_idx3.dbf: too large to archive in current mode
cpio: Error with lstat() of "oper1/absopr/cpm/ST_TFD/UTL_cef988_cefb3f_20070226_235004.TXT", errno 2, No such file or directory
cpio: Error with lstat() of "oper1/absopr/cpm/ST_TFD/UTL_cef5a0_cef793_20070226_221148.TXT", errno 2, No such file or directory
errno 2, No such file or directory
of "oper1/absopr/cpm/ST_TFD/UTL_cdf389_cdf57c_20070226_100108.TXT", errno 2, No such file or directory
cpio: cpio: oper1/temp/utlapp_0209.dmp: too large to archive in current mode
cpio: cpio: operdata1/nccbs/log/cpm/cpm_up_20631010_104709.log: too large to archive in current mode
cpio: cpio: operdata1/nccbs/log/cpm/cpm_up_20631011_124141.log: too large to archive in current mode
cpio: cpio: operdata2/orabackup/export/expdat.dmp: too large to archive in current mode
cpio: File size of "oracle/ora9i/920/network/log/listener.log" has increased by 183
cpio: cpio: oracle/ora9i/seo/nepal/20040209/utlapp_0209.dmp: too large to archive in current mode
cpio: cpio: oradata2/ORA9/undotbs01.dbf: too large to archive in current mode
155845519 blocks
199 error(s)
Archive creation complete
Got a solaris 10 server that I want to take a flar of in order to use to build a new server. Works fine.
Only trouble is there is software on the original server that is not needed on the new server - it will be uninstalled.
I was thinking of creating the flar from the original server and... (0 Replies)
hi,
i would like to know if it is posible to create the flash archive and in the same line add another command to save it in another server through SCP.
flarcreate -n "sv756flash" -c -X excludefilelist |...
i appreciate your help.
thanks a lot. (4 Replies)
Hello Forum,
I'd like to clone a Solaris 10 System. Well, I read a lot about flarcreate.
Anyway I only read how to _create a flash archive by using flarcreate. But I don't know how to copy the data back to another harddisk from an ar:confused:chive to get a second runing system.
... (4 Replies)
Hi, I have to clone a system and i would like to use flarcreate. My question is regarding excluding some NFS mounts and some directories under /. If somebody have done this earlier please advice on the following procedure.
Create a file like /exclude_list and put the following lines in it
... (1 Reply)
I am trying to take Solaris OS backup with the following command
"flarcreate -S -n / /server11/inblr.flar", but this is taking complete root / (which includes my othe mount points also),
Can any one suggest how to take only solaris OS backup and restore proceedure
Thanks in advance (4 Replies)
Hi, i'm trying to make a system copy from one server to another (solaris 9), they have the same configuration. I've tried to create a flash archive using the flarcreate but the flash file size is 5.06 approx. and the method the flarcreate is using is CPIO and he cannot handle sizes over 4 GB.
Is... (2 Replies)
found my notes got it
flarcreate -n jumpstart -x /jumpstart/flash /jumpstart/flash/jumpstart.flar
i think this will omit that directory and save it there correct? (3 Replies)
Hi there
I have created a flash archive using flarcreate and rolled out via jumpstart and everything seems fine, however when I roll out the archive to another box, everything is fine apart from the /etc/hosts file which is the same as the masters hosts file (i.e. it still has the original... (1 Reply)
Hi,
Someone knows hot to create a flash archive to a remote tape device?
Here is my try:
$flarcreate -n nereus -S -t lisdev:/dev/rmt/1n
WARNING: hash generation disabled when using tape (-t)
current filter settings
Creating the archive...
ERROR: Unable to work archive.
Regards (4 Replies)
Hi,
I have a solaris 5.6 box, and i need to create a Flash Archive for DRP porposes. When i execute the falarcreate commnad the system returns "flarcreate: command not found" . I search the entire system (find . -name *flar*) for that comand and i can find it. Solaris 5.6 donīt have this... (1 Reply)