As Z-Man mentioned, doing this on an active/online site is not such a great idea because of the potential for the database to be out of sync with backed up files. However, I will admit that I am guilty of doing this simply to make sure I always had daily backups of my sites, and for convenience did not want to announce maintenance/pull the site(s) offline every single day. The way most people deal with that is to run a cron job at a time when you expect no activity on your site (this applies to any site using a database along with some kind of data directory, not just OSSN btw), for example, 3:00 AM. You can then write a short shell script which uses the "tar" command to create an archive of all your site's data and the "mysqldump" command to create a backup of your database. You can look at the unix man pages for these commands or google how to use them. Then just create a new entry in your crontab to run your shell script as often as you would like (again, google is your friend here)... but please don't ignore the issues brought up by Z-Man - depending on how active your site is, you may well run into the issue he described with your db and files being out of sync.