The backup server ran out of space, so I've just cleared out some older Mediawiki backups (especially since we're moving off Mediawiki).
Normally, I go and kill off some random older backups every two weeks or so when this happens. That's not a good long term approach though. Something scripted would be better. Anyone have thoughts on the best approach for this? I'm happy to give remote ssh access to the server (uses public key only). + Justin Begin forwarded message: > From: r...@gluster.org (Cron Daemon) > Subject: Cron <jclift@supercolony> /home/jclift/bin/transfer_backups.sh > Date: 26 June 2015 01:20:22 BST > To: jcl...@gluster.org > > rsync: open "/storage/mediawiki/glusterfs-mediawiki-db_20150626.sql.gz" > failed: No space left on device (28) > rsync: open "/storage/mediawiki/glusterfs-mediawiki-files_20150626.tar.bz2" > failed: No space left on device (28) > rsync error: some files/attrs were not transferred (see previous errors) > (code 23) at main.c(1039) [sender=3.0.6] > rsync: open "/storage/wordpress/glusterfs-wordpress-db_20150626.sql.gz" > failed: No space left on device (28) > rsync: open "/storage/wordpress/glusterfs-wordpress-files_20150626.tar.bz2" > failed: No space left on device (28) > rsync error: some files/attrs were not transferred (see previous errors) > (code 23) at main.c(1039) [sender=3.0.6] -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
