Website backups are a critical part of the success and longevity for any online business. It is critical to understand who is taking responsibility for maintenance and backups as part of the upfront agreement. Many hosting packages offer some sort of backup plan as part of their service, but relying on only them can lead to catastrophe.
Who is doing backups:
As the developer I only take backup of projects / website that I am actively working on. A larger site I may only be taking backup from files I know my changes will affect. I try to be as clear on this issue as possible as I do not want a client thinking I am maintaining a data center for any website I have ever worked on. The developer should be proactive in letting their clients know the responsibility of backups is not being handed on the developer’s side.
Over 90% of the work I am doing is with marketing and web agencies. At the end of the day the agency has the responsibility to have a plan or agreement in place to ensure the safety of their client’s property.
One issue I have seen more than once is where the service or host is doing backups but the issues is discovered later then the last backup. In many cases a bug on a website might not be noticed right away, so it is critical to have a stable version as well and backups before and after any changes.
BackupBuddy is a paid plugin that works with WordPress. It is one of the more common solution used when the site is built on WordPress. The cost will depend on the amount of sites that are required to backup.
Hosting Backup Solution:
Depending on the host to ensure the site is being backed up will require a bit of thought and research. I have my site www.ShaneWebGuy.com on WPEngine and they have it so I can do a combination of checkpoint backup (prior and after a fix) and automatic backups. These type of solutions are not cheap , but I can pull a backup from a restore point in a matter of minutes.
In some cases, a manual backup stored in a place like DropBox or Google Drive can be a viable solution. I recommend this solution for simple HTML sites that do not have a database or a lot of changes. In any case a manual backup along with another automated solution can ensure the extra layer of protection.