I woke up to my site being down this morning. I called the tech guys and they told me my system partition was full, here is what they said.
There were symlinks for /usr and /var that were pointing to themselves, which I deleted, but your / directory if still showing to be 100% full. You need to log into your machine via ssh and this data that has been generated and filled this directory. For us to perform any further work, it will incur administrative charges.
I understand that these things are going to happen and I will have to pay but I haven't the slightest idea of what a symlink is and why they are pointing to themselves. They are currently working on it but I am wondering if there is something in my threads that may be causing that, I would like to prevent it in the future.
They found my problem, it turns out I am saving my backups to my /home which doesn't sound like a good idea I can't find an option to just overwrite nightly, this seems like it would be ideal. So I am forced to change the location of it, just not sure where to. Any ideas of a good place off of /home for this? Here is what the current setup is.
I always run a second drive, and mount it as /backup and then dump all the backups to that. You need to have a fairly large amount of space to be able to hold the backups as things like your log files and such grow as well.
So there is no way to just have a nightly backup that overwrites the previous nights? Which is cool I will just have to RTFM Also, I take it I will have to command line in there to create and mount a partition is that correct? Thanks for the help guys
well seeing as each backup comes in the way of backup-couch-tomatoe.cc-2-21-2004.tar.gz or such it wouldn't overwrite it because of the date part. What you would have to do is remove the old one once a ne one is made. OR a better solution is to get a second drive.
DESCRIPTION This manual page documents the GNU version of tar , an archiving program designed to store and extract files from an archive file known as a tarfile. A tarfile may be made on a tape drive, however, it is also common to write a tarfile to a normal file. The first argument to tar must be one of the options: Acdrtux, followed by any optional functions. The final arguments to tar are the names of the files or directories which should be archived. The use of a directory name always implies that the subdirectories below should be included in the archive.
FUNCTION LETTERS One of the following options must be used: -A, --catenate, --concatenate append tar files to an archive -c, --create create a new archive
-d, --diff, --compare find differences between archive and file system --delete delete from the archive (not for use on mag tapes!)
-r, --append append files to the end of an archive
-t, --list list the contents of an archive
-u, --update only append files that are newer than copy in archive
-x, --extract, --get extract files from an archive
OTHER OPTIONS --atime-preserve don't change access times on dumped files
-b, --block-size N block size of Nx512 bytes (default N=20)
-B, --read-full-blocks reblock as we read (for reading 4.2BSD pipes)
-C, --directory DIR change to directory DIR
--checkpoint print directory names while reading the archive
-f, --file [HOSTNAME:]F use archive file or device F (default /dev/rmt0)
--force-local archive file is local even if has a colon
-F, --info-script F --new-volume-script F run script at end of each tape (implies -M) -G, --incremental create/list/extract old GNU-format incremental backup
-g, --listed-incremental F create/list/extract new GNU-format incremental backup -h, --dereference don't dump symlinks; dump the files they point to
-i, --ignore-zeros ignore blocks of zeros in archive (normally mean EOF)
-j, -I, --bzip filter the archive through bzip2. Note: -I is deprecated and may get a different meaning in the near future. --ignore-failed-read don't exit with non-zero status on unreadable files
-k, --keep-old-files keep existing files; don't overwrite them from archive
-K, --starting-file F begin at file F in the archive
-l, --one-file-system stay in local file system when creating an archive
-L, --tape-length N change tapes after writing N*1024 bytes
-m, --modification-time don't extract file modified time
Create a /backups directory off the server root and things should be fine. If you backup to the home directory - you are backing up the backup every night. And using the normal Cpanel backups (daily) you'll have 3 copies - monthly, weekly and daily. You just don't want this anywhere inside your /home directory.
If you use the "Incrimental Backup" then rather than tarring and gzipping all the accounts in the home directory nightly, it'll just make one backup in use rsynch to update nightly ONLY what has changed.
I have one server with a HUGE account on it - and the nightly tar and gzip really send server load through the roof as they have lots of photo and video files. So I use the incrimental backup function. That sounds like what you are looking for. Just create a new directory off the web root called /backup or something.
Got it Josh, once again you come through and saved the day Thanks to all for the help here. I am getting pretty used to command lining my way around in there, funny thing is that once you log in as root you still have to cd .. up a level. I also installed Pico Josh, I wasn't liking that VI much
Donate to UBBDev today to help aid in Operational, Server and Script Maintenance, and Development costs.
Please also see our parent organization VNC Web Services if you're in the need of a new UBB.threads Install or Upgrade, Site/Server Migrations, or Security and Coding Services.
I can't find an option to just overwrite nightly, this seems like it would be ideal. So I am forced to change the location of it, just not sure where to. Any ideas of a good place off of /home for this? Here is what the current setup is.
Also, I take it I will have to command line in there to create and mount a partition is that correct? Thanks for the help guys 
Thanks to all for the help here. I am getting pretty used to command lining my way around in there, funny thing is that once you log in as root you still have to cd .. up a level. I also installed Pico Josh, I wasn't liking that VI much 
