Generate Backup default settings

In the files panel, if you are to select all files by default, that would mean excluding them, i am sure you don’t want to do that. Switching the operational mode so only checked files are included in the backup would not be a good procedure and it would create problems with automated backups.

I don’t think there is a need to change the default name, as you would only have to edit it once and if you schedule an automatic backup, the backup name will keep it’s editing. I would rather keep the backup term simple as you can actually backup not just WordPress, but an entire site if the Backup Start Path is changed

As for default comment, not sure what you would want to put there, maybe you can provide more info?

I would rather keep the backup term simple as you can actually backup not just WordPress, but an entire site if the Backup Start Path is changed

One of the main reasons I use this plugin is because I can backup “extra” stuff, including custom tables in MySQL that work alongside WordPress ??

I am backing up about 20 sites every month. Some are Joomla, some are WordPress, and some are html. They all go to S3. When I look at my S3 bucket I’d like to see them sort by website type. I use Akeeba Backup for Joomla and I can save a setup for a backup and make these things part of the automation.

All my Joomla sites begin with “jmla” and then the date/time stamp. So I can quickly look at the file listing in S3 and find a particular backup from a particular date for a specific domain.

As for excluding files I almost always exclude the administrator directory, cgi bin, and one other I forget which. I think it’s something my host puts in there. Anyway, they are not needed to reinstall a website.

I take backups for several reasons. One is a standard monthly backup. Another may be before major changes and not part of a schedule. Another may be prior to adding new plugins and also not part of a schedule. I make notes as to the reason for the backup in the comments.

• This reply was modified 8 years ago by duanemitchell.

You do have a good point regarding backups organisation, I will look into adding default prefix for backups when setting up a schedule, possibly a folder, so when you want to create an automated backup, you can specify a default folder to put the backups in, you could use this naming for easier handling.

The best way to keep them organised on S3 would probably be to create a separate bucket for each site you want to backup, and the configuring that in the Remote Storage Section, is there a reason why this would not work for you?

• This reply was modified 8 years ago by XCloner.

I see where when saving a scheduled backup all the settings are saved. So I can prefix WordPress backups with “wp” rather than “backup”. That solves that problem. I might consider a separate bucket for each website but for now I’m going to have them all go into one. It’s quick and I can quickly scan the listing to find what I’m looking for. I will probably set a rule in S3 to delete files after a certain period of time, 2 or 3 years. Thanks for your help.

Maybe there is a benefit to separate buckets I did not consider. In the Manage Backups window when switching to view remote storage it will show all backups in the bucket. Including the backups for other domains.

Yes, separating buckets for each site would be a good procedure specially for easier handling of the remote Manage backups section