Permalink
Browse files

Typos.

  • Loading branch information...
1 parent 7e24dbf commit f9a57f39561cf83f03a6a4138b08f777c7b20fe8 @djanowski djanowski committed Feb 13, 2013
Showing with 2 additions and 2 deletions.
  1. +2 −2 topics/persistence.md
@@ -267,8 +267,8 @@ Since many Redis users are in the startup scene and thus don't have plenty
of money to spend we'll review the most interesting disaster recovery techniques
that don't have too high costs.
-* Amazon S3 and other similar services are a good way for mounting your disaster recovery system. Simply transfer your daily or hourly RDB snapshot to S3 in an encrypted form. You can encrypt your data using gpg -c (in symmetric encryption mode). Make sure to store your password in many differnet safe places (for instance give a copy to the most important guys of your organization). It is recommanded to use multiple storage services for improved data safety.
-* Transfer your snapshots using scp (part of ssh) to far servers. This is a fairly simple and safe route: get a small VPS in a place that is very far from you, install ssh there, and greate an ssh client key without passphrase, then make
+* Amazon S3 and other similar services are a good way for mounting your disaster recovery system. Simply transfer your daily or hourly RDB snapshot to S3 in an encrypted form. You can encrypt your data using `gpg -c` (in symmetric encryption mode). Make sure to store your password in many different safe places (for instance give a copy to the most important guys of your organization). It is recommanded to use multiple storage services for improved data safety.
+* Transfer your snapshots using SCP (part of SSH) to far servers. This is a fairly simple and safe route: get a small VPS in a place that is very far from you, install ssh there, and greate an ssh client key without passphrase, then make
add it in the authorized_keys file of your small VPS. You are ready to transfer
backups in an automated fashion. Get at least two VPS in two different providers
for best results.

0 comments on commit f9a57f3

Please sign in to comment.