Use cpbackup for backups every 6 hours

cpbackup actually runs the underlying pkgacct command, so you could just run "pkgacct accountname /backup/special" periodically and then move the generated backup file into a time-based filename (use $(date +%xx)).

There might be smarter/faster/more effective ways to do this with mysql commands and tar or rsync; pkgacct is really slow.

 

I would like to have my backups run every 6 hours as well. But I use the incremental system for back ups. If I try to rerun it then it just says daily backups are up to date.

 

You can set a cron to run this command and it will update as much as you set the cron to run: /scripts/cpbackup --force

I am not sure how good this is for the server.

 

To force cpbackups to run I believe you can pass the --force parameter:

/scripts/cpbackup --force



dawa, by default the pkgacct script will create a cpmove file. I am not sure if there are any differences between the "types" of backups, but you can resolve this by using:

/scripts/pkgacct <user> </backup/path> userbackup

which will create a backup file in the format of backup-m.d.Y_H:m:s_user.tar.gz

Other options, instead of userbackup, are cpmove and backup. I do know that using userbackup will prevent the backup from storing any other userbackups that exist i your home directory. But as far as a difference between a cpmove file and a backup file, I'm not aware of any structural differences.