-
☆ A M B ☆
- 24,524 Posts
Unless the client wants full control of the site as soon as it’s finished; in that case we do need to provide them with a usable backup system.
I have to agree with Susan here, for those clients that want complete control their should be a simple process which they can perform - 80% of my clients want total control and do not pay a retainer to cover costs for me to perform these backups for them, its part of the CMS process I train them to perform is a monthly backup...
Yeah Susan, you are right... as always...
I tell my clients that we will do a daily backup for them
and store them in separate servers with redundancy and
they usually do not want to do anything with backups...
but... there are all kinds of clients...
Website: www.mercologia.com
MODX Revo Tutorials: www.modxperience.com
MODX Professional Partner
UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
The best use I could see for a backup tool built into modx (or indeed provided as an extra component) is that clients could back up and download a site backup themselves just before making a change that they may want to roll-back later.
Susan,
That’s a very nice plan, as usual, you rule!
And yes, cron is certainly a great option, but geeks required, and may not even be available on many hosting accounts.
I also like the fact that hosts do regular backups, but that varies a lot from host to host. For instance, many people host with Godummy, er, Godaddy. Godummy makes regular backups, but I have heard about an indeterminate time lag that can occur when you request a restore. It almost depends on who you happen to get in tech support... their skill and intelligence levels vary a whole lot.
