Skip to content

fixed typos in backup.rst file #3636

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
justinegeffen merged 4 commits into from
May 27, 2020
Merged

fixed typos in backup.rst file #3636

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
dc8d32a
fixed typos in backup.rst file
fakela May 25, 2020
3911e0b
Update source/administration/backup.rst
fakela May 26, 2020
eb2bf9a
Update source/administration/backup.rst
justinegeffen May 27, 2020
5ba03dd
Update source/administration/backup.rst
justinegeffen May 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions source/administration/backup.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Options to protect your Mattermost server from different types of failures range
Backup
------

The state of your Mattermost server is contained in multiple data stores that need to be separately backed-up and restored to fully recover your system from a failure.
The state of your Mattermost server is contained in multiple data stores that need to be separately backed up and restored to fully recover your system from failure.

To backup your Mattermost server:

Expand All @@ -27,7 +27,7 @@ To backup your Mattermost server:

Please note that to make a 'clean' backup you need to stop Mattermost during the duration of the backup otherwise the database and files may become out of sync.

To restore a Mattermost instance from backup, restore your database, ``config.json`` file and optionally locally stored user files into the locations from which they were backed up.
To restore a Mattermost instance from backup, restore your database, ``config.json`` file, and optionally locally stored user files into the locations from which they were backed up.

Disaster Recovery
---------------------------
Expand All @@ -38,19 +38,19 @@ There are two common approaches:

Automated backup
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Automating backup up a Mattermost server provides a copy of the server's state at a particular point in time, which can be restored if a failure in future leads to loss of data. Options include:
Automating backup for a Mattermost server provides a copy of the server's state at a particular point in time, which can be restored if a failure in the future leads to loss of data. Options include:

- Automation to periodically backup the Mattermost server, which may include all the components listed above or a subset depending on what you choose to protect.
- Automation to periodically back up the Mattermost server, which may include all the components listed above or a subset depending on what you choose to protect.
- Automation to restore a server from backup, or deploy a new server, to reduce recovery time.
- Automation to verify a backup has been successfully produced to protect against backup automation failures.
- Storing backups off-site, to protect against physical loss of onsite systems.

Recoverying from a failure using a backup is typically a manual process and will incur downtime. The alternative is to automate recovery using a high availability deployment.
Recovering from a failure using a backup is typically a manual process and will incur downtime. The alternative is to automate recovery using a high availability deployment.

High availability deployment
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Deploying Mattermost in `high availability mode <https://docs.mattermost.com/deployment/cluster.html>`__ allows for fast, automated recovery from a component failure, such as a specific server running out of disk space or having a hardware issue, by running on redundant servers. Options include:
Deploying Mattermost in `high availability mode <https://docs.mattermost.com/deployment/cluster.html>`__ allows for fast, automated recovery from component failure, such as a specific server running out of disk space or having a hardware issue, by running on redundant servers. Options include:

- Deploying redundant Mattermost servers, to protect against failures in the Mattermost server.
- Deploying redundant databases, to protect against failures in the database.
Expand Down Expand Up @@ -106,6 +106,3 @@ It is highly important after the outage to switch everyone back to SSO from emai