|
1.
|
|
|
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.\nMany events could lead to the destruction of your data, including:\n - 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])\n - fire or other physical disaster\n - accidental damage\n - malicious damage\n - accidental loss of files\n - web-hosts going out of business\n - having a hard-disk seized (if for example the site is unfortunately hosted on the same web server as a police suspect)\n - 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)
|
|
|
|
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.\nMany events could lead to the destruction of your data, including:\n - 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])\n - fire or other physical disaster\n - accidental damage\n - malicious damage\n - accidental loss of files\n - web-hosts going out of business\n - having a hard-disk seized (if for example the site is unfortunately hosted on the same web server as a police suspect)\n - 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)
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]DOC_BACKUPS
|
|
2.
|
|
|
Backups
|
Context: |
|
[strings]BACKUPS
|
|
|
|
Backups
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]BACKUPS
|
|
3.
|
|
|
Make backup
|
|
|
|
Make backup
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]BACKUP
|
|
4.
|
|
|
Your last backup was made {1} days ago.
|
|
|
|
Your last backup was made {1} days ago.
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]LAST_BACKUP
|
|
5.
|
|
|
Your last backup was made today.
|
|
|
|
Your last backup was made today.
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]LAST_BACKUP_TODAY
|
|
6.
|
|
|
Your last backup was made yesterday.
|
|
|
|
Your last backup was made yesterday.
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]LAST_BACKUP_YESTERDAY
|
|
7.
|
|
|
You have not yet made a backup. It is highly recommended that you keep regular off-server/-site backups of your content.
|
|
|
|
You have not yet made a backup. It is highly recommended that you keep regular off-server/-site backups of your content.
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]NO_LAST_BACKUP
|
|
8.
|
|
|
Your backup is currently being generated in the <tt>exports/backups</tt> directory as <tt>{1}</tt>. You will receive an e-mail 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.
|
|
|
|
Your backup is currently being generated in the <tt>exports/backups</tt> directory as <tt>{1}</tt>. You will receive an e-mail 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.
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]BACKUP_INFO_1
|
|
9.
|
|
|
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.
|
|
|
|
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.
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]BACKUP_TYPE
|
|
10.
|
|
|
Incremental backup
|
|
|
|
Incremental backup
|
|
Translated and reviewed by
mrx5682
|
|
|
|
Located in
[strings]INCREMENTAL_BACKUP
|