Site backup - best practices

I am nearing the end of the development phase of the Hikashop site that I've been working on. The last product shots should be done next week.

But I am concerned about best practices for backup and restore.

Last weekend the development site was caught in that very large incident on the InMotion data centres where over 300,000 site were hacked by tiger-m@ate. I had been backing up using akeeba, but using the restore point did not work. So I had to unzip an older full backup and restore the damaged file that way.

It was an easy enough fix, but it had me wondering about best practices for backup for Hikashop and how others are addressing this problem.

I'm not totally comfortable with Akeeba simply because I don't have a full understanding of the way it works. So I have been considering manual methods by downloading the entire site to my computer using Dreamweaver or other FTP methods and backing up the database using PHPmyadmin.

I plan to make a complete copy of the site into another folder before going into production mode in 3 weeks time, but that's something I'll have to learn, especially in regard to moving the database to a different database.

Any suggestions, advice or experiences would be very welcome.

Thanks

Jim

Many thanks, Nicolas. Aren't bash scripts the UNIX equivalent of DOS batch programming - I've written plenty of DOS scripts given that I bought my first IBMPC in 1982. Do you run your scripts as a CRON job?

The host company does offer some options in Cpanel, but their server backups overwrite the previous backup every night and for many of their sites, the backup was done after the attack started. So I'm not going to rely on that, even though I expect there will be many changes to their SOP after this attack!

I'm just wondering how others schedule their backups and how many daily backups they keep before overwriting the earliest and if anyone does manual backups?

Thanks

Jim

Thanks, Nicolas,

Jim