a:48:{s:11:"DOC_BACKUPS";s:1041:"In this day and age, everyone who uses a computer should know the necessity of taking backups. It is an absolutely crucial chore, and if you do not do it, you risk losing all your data, much of which you could never hope to recreate if you run a community website.

Many events could lead to the destruction of your data, including:
 - hard disk corruption (perhaps 30% of cheap hard disks which are under constant use develop physical corruption problems \[I made the statistic up, but based on my experience, it is about right])
 - fire or other physical disaster
 - accidental damage
 - malicious damage
 - accidental loss of files
 - webhosts going out of business
 - having a hard-disk seized (if for example the site is unfortunately hosted on the same web server as a police suspect)
 - bugs in software (it is possible the software contains bugs which could cause data loss, and we do not accept liability for losses due to this, as users should have adequate backups and it is impossible for us to test all software usage scenarios)";s:13:"DOC_BACKUPS_2";s:362:"Remember [b]don't just take backups, test them too[/b]!

Be aware that [b]the software developers recommend using a proper webhosting control panel backup tool instead of this tool[/b] if at all possible. Webhosting control panel tools have the advantage of running with less restrictions, so are less likely to have problems with timeouts or memory constraints.";s:7:"BACKUPS";s:7:"Backups";s:6:"BACKUP";s:11:"Make backup";s:11:"LAST_BACKUP";s:47:"Your last backup was made {1} {1|day|days} ago.";s:17:"LAST_BACKUP_TODAY";s:32:"Your last backup was made today.";s:21:"LAST_BACKUP_YESTERDAY";s:36:"Your last backup was made yesterday.";s:14:"NO_LAST_BACKUP";s:104:"You have not yet made a backup. It is highly recommended that you keep regular off-server/-site backups.";s:13:"BACKUP_INFO_1";s:400:"Your backup is currently being generated in the <kbd>exports/backups</kbd> directory as <kbd>{1}</kbd>. You will receive a notification once it has been completed, and you will be able to track progress by viewing the log file. Please test your backups are properly generated at least once for any server you host this software on; some servers cause problems that can result in corrupt backup files.";s:11:"BACKUP_TYPE";s:185:"Full backups include all files. Incremental backups contain files changed since the last backup, and a directory of the filesystem state. Both types come with a database restore script.";s:18:"INCREMENTAL_BACKUP";s:18:"Incremental backup";s:11:"FULL_BACKUP";s:11:"Full backup";s:10:"SQL_BACKUP";s:20:"Database backup only";s:13:"MAX_FILE_SIZE";s:67:"Only files smaller than this size (in megabytes) will be backed-up.";s:15:"BACKUP_FINISHED";s:73:"Your backup has finished and is <a href="{1}">available for download</a>.";s:13:"SCHEDULE_TIME";s:13:"Schedule time";s:25:"DESCRIPTION_SCHEDULE_TIME";s:205:"If you wish to schedule (postpone) the backup, choose a date and time when you would like this backup to be taken. It is advisable to run the backups when the site is least active, to maximise performance.";s:15:"RECURRANCE_DAYS";s:20:"Days between backups";s:27:"DESCRIPTION_RECURRANCE_DAYS";s:200:"If you have scheduled a time, you can also request that backups be routinely taken from that time onwards, with this number of days between backups. If you leave this blank, no recurrence will happen.";s:29:"SUCCESSFULLY_SCHEDULED_BACKUP";s:43:"The backup has been successfully scheduled.";s:22:"BACKUP_FILE_COMPRESSED";s:22:"Compressed backup file";s:24:"BACKUP_FILE_UNCOMPRESSED";s:11:"Backup file";s:15:"BACKUP_FILE_LOG";s:8:"Log file";s:22:"BACKUP_FILE_UNFINISHED";s:18:"Backup-in-progress";s:30:"MODULE_TRANS_NAME_admin_backup";s:7:"Backups";s:25:"CONFIG_OPTION_backup_time";s:68:"The number of hours between backups. Set to blank to disable checks.";s:17:"BACKUP_REGULARITY";s:17:"Backup regularity";s:22:"MAXIMUM_SIZE_INCLUSION";s:28:"Maximum file size to include";s:13:"BACKUP_README";s:259:"This is a backup of a website taken on {1}.
To restore the backup:
 - upload the files to the web server;
 - edit the _config.php if you have moved to a server with different database settings;
 - load up the restore.php script by URL to restore the database.";s:36:"CONFIG_OPTION_backup_server_hostname";s:119:"The remote server hostname/IP-address to auto-copy scheduled backups to (if not specified, no remote backups are done).";s:32:"CONFIG_OPTION_backup_server_port";s:32:"The FTP port for remote backups.";s:32:"CONFIG_OPTION_backup_server_user";s:88:"The optional FTP username for remote backups (if left blank anonymous-FTP will be used).";s:36:"CONFIG_OPTION_backup_server_password";s:99:"The optional FTP password for remote backups (if left blank the staff e-mail address will be used).";s:32:"CONFIG_OPTION_backup_server_path";s:120:"The FTP file-path to send remote backups to, or if the last character is a slash, the FTP directory-path to backup into.";s:30:"CONFIG_OPTION_backup_overwrite";s:64:"Whether a full backup should overwrite the previous full backup.";s:22:"BACKUP_SERVER_HOSTNAME";s:29:"Remote backup server hostname";s:18:"BACKUP_SERVER_PORT";s:25:"Remote backup server port";s:18:"BACKUP_SERVER_USER";s:29:"Remote backup server username";s:22:"BACKUP_SERVER_PASSWORD";s:29:"Remote backup server password";s:18:"BACKUP_SERVER_PATH";s:25:"Remote backup server path";s:16:"BACKUP_OVERWRITE";s:21:"Overwrite old backups";s:14:"CALCULATE_SIZE";s:20:"Calculate total size";s:15:"CALCULATED_SIZE";s:49:"A full backup at this cut-off value would be {1}.";s:11:"COMPRESSING";s:34:"TAR generated, now compressing it.";s:31:"FAILED_TO_UPLOAD_BACKUP_SUBJECT";s:23:"Failed to upload backup";s:28:"FAILED_TO_UPLOAD_BACKUP_BODY";s:76:"An automated backup failed to be uploaded to the configured FTP server, {1}.";s:20:"CONTINUE_RESTORATION";s:20:"Continue restoration";s:22:"BACKUP_RESTORE_SUCCESS";s:118:"The backup has restored. It is important that you now delete <kbd>restore.php</kbd> immediately, for security reasons.";}