Index: [Article Count Order] [Thread]

Date:  Fri, 11 Sep 2009 10:39:01 -0500
From:  Jim Matysek <matysekj (at mark) usms.org>
Subject:  [coba-e:16021] System backups failing to tar
To:  coba-e (at mark) bluequartz.org
Message-Id:  <4AAA6F15.1060505 (at mark) usms.org>
X-Mail-Count: 16021

I have always run a system backup every night using the old Nuonce 
backup package that uses raqbackup.  For the past few weeks it has been 
failing for each site's backup, but the MySQL backups work as do the 
backup of additional dirs.  In my system backup directory I only find:

server.domain.tld.cmu-xml-files.tar.gz
server.domain.tld.dirs.tar.gz
server.domain.tld.mysqldump.tar.gz

That directory used to have lots of files in it daily covering each 
site.  I suspect the behavior changed right around the time where we had 
hundreds of yum updates associated with the latest kernel.

Looking at my output-cmuexport.log file in the system_backup directory, 
I find the following log with errors reported for each site:

exporting vsite www.hosteddomain.org
building archive for www.hosteddomain.org
public archive uncompressed size: 19 MB
ERROR createTar: Compression not available.
private archive uncompressed size: 61 MB
ERROR createTar: Compression not available.

I don't get similar errors when it tar's up the mysql backup. Any ideas?

And by the way, we'll be moving to a BO box sometime (hopefully) soon 
and will need to export all sites and import to the new box.  Question: 
With this backup package I can backup individual sites, which creates 
one large gzipped tar file per site. Yet the system backup utility 
creates public and private tar files (when it used to work!). For moving 
to a new server, should I use the system backup? Is there any use to the 
vsite backup utility, or is that just wasted space and cycles?

-jim