WiscWeb - Data Backup Policy
The following document outlines WiscWeb’s various modes of backing up website content and details who is responsible for each one.
WordPress-Specific Backups
AKA WordPress Revision History
Responsible Party: Website Admins and Editors
This revision history for pages and posts can be accessed by an editor or admin of the site at any time by following the instructions listed in WiscWeb - Revert a Page or Post to a Previous Revision.
Database Backups
Responsible Party: WiscWeb Team
As these are full multisite snapshots, this content is not separated based on website. Therefore, ability to restore data for an individual site can be a time-consuming and arduous process that must be handled by a member of the WiscWeb team (in other words, this is not something that a user has access to, by default). If possible, it is recommended that users utilize the default WordPress revision history to restore pages and posts of their site.
If a catastrophic disaster occurs on your site that cannot be fixed by accessing the WordPress page/post revisions, WiscWeb can provide access to your sites' database files once, upon request. Multiple/repeat requests for backups will not be accommodated.
File System Backups
Responsible Party: WiscWeb Team
The WiscWeb File System is set up to take an entire multisite snapshot once per night, which is copied to a separate EFS volume and also held for 14 days.
As these are full multisite snapshots, this content is not separated based on website. Therefore, ability to restore data for an individual site can be a time-consuming and arduous process that must be handled by a member of the WiscWeb team (in other words, this is not something that a user has access to, by default). If possible, it is recommended that users utilize the default WordPress revision history to restore pages and posts of their site.
If a catastrophic disaster occurs on your site that cannot be fixed by accessing the WordPress page/post revisions, WiscWeb can provide access to your sites' file system backups once, upon request. Multiple/repeat requests for backups will not be accommodated.