Seems it's working in that the new backups are beings placed in files that are still in /Production-Site-Backup/database.
I think we can delete all the backups in /Production-Site-Backup, and lots of the ones in /Production-Site-Backup/database as we probably only need to keep 1-2 months worth of backups.
From searching it would seem that likely the backups that were continuously added to the old location (/Production-Site-Backup) were probably coming from the staging server, as it looks like it was setup with backups as well.
So if you like I'll:
Have only production generate backups on Agnes
Remove old backups
Change backup system to keep a rolling 30 day backup rather than keeping every backup indefinitely.
Excellent, good to know on the above points. Here's what I'd like based on what you've written:
Have only production generate backups on Agnes
Remove old backups
Change backup system to keep a rolling 90 day backup rather than keeping every backup indefinitely.
In the future, I'll probably want to change how far the backups go, but for now since we're still fairly heavily developing the site, I'd like to have more backups.
There you can trigger backups, I wouldn't recommend triggering the file back up all too often as theres 11GB of file data on the server so that's not really practical to download. Either way the backups run every day. Also to note there are two destinations "Agnes" and "Agnes Files" the first is the location of the database, the second is the location of the files directory please select the appropriate one for the type of backup you wish to perform.
Currently when the Drupal database is backed up to our server it goes to: /Production-Site-Backup
However, I'd like it to go to a subfolder there: /Production-Site-Backup/database
I tried to configure backups to that location myself, but it doesn't work. Can you double-check the configuration when you have a moment.
Seems it's working in that the new backups are beings placed in files that are still in /Production-Site-Backup/database.
I think we can delete all the backups in /Production-Site-Backup, and lots of the ones in /Production-Site-Backup/database as we probably only need to keep 1-2 months worth of backups.
From searching it would seem that likely the backups that were continuously added to the old location (/Production-Site-Backup) were probably coming from the staging server, as it looks like it was setup with backups as well.
So if you like I'll:
Excellent, good to know on the above points. Here's what I'd like based on what you've written:
This is setup in a "Drupal Feature", but is currently awaiting on deployment to production.
OK, thanks for letting me know. We can close this once we go to prod.
I believe this is set up and we can close this ticket. Before we do, could you tell me how I trigger a manual backup?
Log in as the administrator and go to the page:
http://livingstoneonline.org/admin/config/system/backup_migrate
There you can trigger backups, I wouldn't recommend triggering the file back up all too often as theres 11GB of file data on the server so that's not really practical to download. Either way the backups run every day. Also to note there are two destinations "Agnes" and "Agnes Files" the first is the location of the database, the second is the location of the files directory please select the appropriate one for the type of backup you wish to perform.
OK, perfect. Thank you!