Backup and Redundancy

Local/VM Instance

Backup Schedule

Both local and hosted instances are provided with a default Scheduler task to perform a MySQL backup every 24 hours, with a 1 month retention policy.


What data is contained in the backup MySQL dump?

The MySQL dump contains an output of the entire ProVision database, with all DNS data and configuration information specific to the ProVision instance. This does not include MySQL configuration or system level configuration data. The MySQL dump also does not contain the globals.php files under ProVision's /data folder, though it may easily be recreated if needed. 


How much space does the backup need?

Database sizing has many factors for both space planning and backup strategies. For larger databases, moving large MySQL databases can be challenging and reduce efficiencies. For a rough idea on how to estimate database sizes and thus backups, here are some conservative metrics that you can use:

If you have specific questions regarding your backup scenario - please contact support at any time.

 

Restoration

Restoration is only a phone call or email away. We can spin up a new instance with your preferred data set, or send you a link to download your database. Optionally, we can even help you set it up and import your data to your new instance or assist with redundant configuration options depending on your RPO/RTO guidelines.


For local customers, you should be backing up the following items:

mysqldump

And system folders off the root directory:

/scans

/zones

/keys

/archive

/data