Automatic backups can be configured to run daily and/or weekly in the background on the system at a time of your choosing. The automatic backups are compatible with our restoration utility process.
Backing up of Media Contents and Historical Data can be a disk intensive operation. If the backup process is too intensive then you might consider using rsync to keep Media Content files in sync on a different hard disk or server. Consult the Backup Package & Structure documentation also.
- Email Report – Enter an email address to deliver backup reports or leave the field blank to disable emailed reports. Email must be configured correctly for this to work.
- Backup System Path – The location to store backups in, this location will also be used for staging the new backup as well.
- I/O Priority Level – Since the backup process can be intensive, it is recommended to run backups in the background at a low priority in order to not disrupt other services. The backup process will use ionice to control the priority of the entire backup processes disk and cpu resources.
- Backup Hour – Select an hour according to your systems default timezone (not the MediaCP default timezone) to run the backup. We recommend that you set it to run during off-peak hours, early enough to allow your server to finish backups before peak traffic resumes. Default 2am Server Time.
Daily / Weekly Backup
The purpose of a Daily and Weekly backup is to configure different retention strategies, since the Media Contents and Historical Data is often very large in size.
- Backup Schedule – Daily backup can run on multiple days, every day if desired.
- Historical Data – Determines if Historical Data should be included in the backup. For large databases, this may take a long time to complete.
- Media Content – Determines if Media Content should be included in the backup. For large amounts of Media Content, this may take a long time to complete and a lot of storage may also be required.
- Retention – How many backups to keep on the system.