|
8:13 pm February 13, 2012
| David
| | |
| New Member | posts 1 | |
|
|
If you put nothing in the Backup name, it will generate something like this:
Archive Name: backup_2012-02-13_13-32_www.sherrypeeljackson.org-sql-drop.tar
If you put "backup_database" in the Backup name, it will generate this: "backup_database.tar
What I would like to see is:
- Append "backup_2012-02-13_13-32_" in front of the name "backup_database".
Of course I'm expecting the date-time to adjust to the correct date-time of execution
and Backup name to be whatever was used.
- If you backup with a Backup name, the prior backup gets written over. Would
like to have generational backups.
- In the Delete Old Backups parameter, delete ONLY the backups that match the
Backup name.
- I can see setting up a cron to do a full backup once a week, and
set up a cron to do a daily database backup.
- Althought I haven't tested this thoroughly, as it currently stands, the delete
older than x days deletes everything that qualifies regardless of archive name.
And this would apply accross all cron jobs. Example:
- The full backup cron is set for delete older than 30 days and
set to run every 7 days.
- The database backup cron is set for delete older than 7 days
and set to run every day.
- On the 8th day of the database backup cron, it would delete
the 1st day of the database backup and also delete the 1st
full backup.
- In the above example I would want to have a retention of the
last 4 full backups and the last 7 database backups.
|
|