Hi Everyone I was thinking to test hourly backup option with append-only backup option. Can we tweak the backup script to make hourly backup with daily, weekly and monthly backups? Hourly backup - Retention = 24 Hours (nHours) Daily backup - Retention = 7 Days or 30 Days (nDays) Weekly backup - Retention = 4 Weeks (nWeeks) I don't mean to use any one of them, I mean to use all above backup option. We should be able to configure each type of backup option for each site. And some extra fields where we can add remote backup storage services like Wasabi, paired with Restic Append-only backup option. What's your take guys? PS: I have this idea but I don't have programming knowledge, I think it can be possible using shell scripting and PHP coding in ISPConfig. Thanks
Does your backup run in less than an hour? Can your disk system handle the constant traffic from backups? When you need backups hourly, a file system that supports snapshots seems called for. https://en.wikipedia.org/wiki/Snapshot_(computer_storage)#File_systems
Hi Thanks for response, Taleman. For CMS sites like WordPress, some sites update their content many times a day, for example publishing more than 10 posts a day. Here this kind of backup can really help. Also, I'm not talking about to store them on local storage, let upload them to backblaze b2, or an S3 compliant storages like aws, wasabi, or digitalocean storage. Once uploaded to remote storage they will be deleted from local storage. Also, backup type is incremental so when a change is made only those files will be backed-up not all everytime. and hourly is not always needed by all sites, so there should be an option to choose from backup option, we can use daily for other sites which less updates their sites. Thanks
well with cms's like wordpress, these updates (apart from any images, embedded docs etc) would mostly be stored in the database. AFAIK ispconfig will only do full database backups at the moment, not incremental backups. you could use something like automysqlbackup and MySQL-incremental to do that part. not sure how you'd integrate it with ispconfig, you can't allow the users the option to delete any of the backups between the last full backup and the latest incremental, that'll break any restore ability beyond that point. and the restore option will have to restore the last full backup and a varying number of incremental backups in sequence. it can definitely be done, outside of ispconfig, but it looks like it'll be quite a bit more work that just tweaking the backup script. I imagine putting incremental backups into ispconfig would require some quite substantial changes in the backend code and database tables.
You can use any kind of remote storage which can be mounted with ispconfig already, e.g. all services that can be mounted by SSH, FTP, SMB/CIFS or that provide a FUSE driver can be used. ISPConfig provides a script hook to mount and unmount your backup drive automatically when needed. So all you have to do is to create the mount- and unmount bash script which have to contain the code to make your backup drive available locally and to unmount it.
