Support

CRON jobs are not complicated, it's the standard way to schedule tasks which take more than a couple of seconds to execute. Remember that WordPress' pseudo-CRON is only executed when there is traffic on your site and is only good for tasks which take 2–3 seconds tops. A backup, by definition, needs to run for several seconds to several hours depending the size of your site. The only way to do that is to have something other than traffic on your site run it, something that can run for a while without stopping. That's the definition of what CRON does.

I cannot write the CRON lines for you for the simple reason that you need two pieces of information. One thing, the path to the CLI backup script, is in your Akeeba Backup interface (Schedule Automatic Backups). The other thing, the path to the PHP CLI executable, is something your host knows. I am neither you nor your host. All I can do without these two pieces of information is what I have already written in the documentation.Even if you give me access to your site I still don't know the path to the PHP CLI executable, you'd have to get that from your host.

The best way to do this is to show the contents of the Schedule Automatic Backups to your host and ask them to make a CRON job for you which replaces /path/to/php with the correct path to the PHP CLI executable for the same version of PHP you are using on your site and have it run every day, once a day at XX:00 where XX is the time of the day you want it to run. For example, tell them to run it at 21:00 GMT for midnight your time — Israel, like Cyprus, is GMT+3 during the summer. They will know what to do.

Regarding the deletion of old backups, this is easy.

Go to Akeeba Backup, Configuration, scroll down to Quota Management. Set “Enable count quota” to Yes, set the next option “Count quota”  to 7. This keeps the last 7 backups. If you're running the backup daily this keeps a week of backups, like you described.