Best practices for backup: rsync

[core-man]

Related to #43.

[github-actions]

This comment was written by the Continuous Documentation bot!

• Preview: https://seismo-learn.org/sitepreview/seismo-learn/seismology101/backup-rsync
• Commit hash: 092bfd7

[seisman]

I made some suggestions to the backup script, but I didn't run it.

Are you running the script in your daily life?

[core-man]

I made some suggestions to the backup script, but I didn't run it.

Are you running the script in your daily life?

usually every month. I convert it from perl.

[seisman]

Please run the backup script again to make sure it works after applying my suggestions. After that this PR is good to merge.

[seisman]

Have you read section 6 in this post (https://www.ruanyifeng.com/blog/2020/08/rsync.html)?

[core-man]

Have you read section 6 in this post (https://www.ruanyifeng.com/blog/2020/08/rsync.html)?

Yes, I have read it. But I think we need a mirror, right? Do we want to do incremental backups?

[seisman]

Have you read section 6 in this post (https://www.ruanyifeng.com/blog/2020/08/rsync.html)?

Yes, I have read it. But I think we need a mirror, right? Do we want to do incremental backups?

It's unclear to me what "a mirror" means.

The current script works well, but it's still risky. We will have big trouble if we backup files weekly and realized that we did something wrong two weeks ago.

[core-man]

The current script works well, but it's still risky. We will have big trouble if we backup files weekly and realized that we did something wrong two weeks ago.

That's a problem. Let's fix it later.