In this scenario access to the server is restricted to Secure FTP(SFTP) and interfaces, such as CPanel.
*Backups of all site content and data should be taken on a regularly scheduled basis. It may be impossible to automate these backups depending on the web interface used, so reminders in calendars etc should be set to ensure that staff are aware of the need to make a backup copy.
*This data should be treated appropriately and stored either on a local backup disk in an encrypted volume or on a separate server also using an encrypted disk
There are a number of tools available for scheduled secure backup of site content and data where the user has access to the server directly.
These include Rsync, Bacula and [https://labs.riseup.net/code/projects/backupninja | Backup NinjaBackupNinja], for this guide we are going to recommend Backup Ninja in comparison with Duplicity, as it this allows for incremental backups which are encrypted using GPG. This means that if the server that the data is being backed up to is compromised, the backed up information is still encrypted. However, this means that the GPG key used to encrypt the data should be stored both on the server being backed up and also offsite in order for its use in case of the need for the retrieval of backups. Additionally, it Duplicity allows for differential backups - meaning that only changed data is updated reducing the time and foot print of each backup.
===Example configs===
==Data Recovery==