From 91bfaacb5a74b8bc2bb6f6c452116fcf0fd39e7c Mon Sep 17 00:00:00 2001 From: jpdsceu Date: Tue, 16 Feb 2021 17:45:55 +0100 Subject: [PATCH] Updated Backing up your vault (markdown) --- Backing-up-your-vault.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Backing-up-your-vault.md b/Backing-up-your-vault.md index bb1427d..62d1b5d 100644 --- a/Backing-up-your-vault.md +++ b/Backing-up-your-vault.md @@ -1,6 +1,6 @@ ## Overview -bitwarden_rs data should be backed up regularly, preferably via an automated process (e.g., cron job). Ideally, at least one copy should be stored remotely (e.g., cloud storage or a different computer). Avoid relying on filesystem or VM snapshots as a backup method, as these are more complex operations where more things can go wrong, and recovery in such cases can be difficult or impossible for the typical user. Adding an extra layer of encryption on your backups would generally be a good idea (especially if your backup also includes config data like your [[admin token|Enabling-admin-page]]), but you might choose to forgo this step if you're confident that your master password (and those of your other users, if any) is strong. +bitwarden_rs data should be backed up regularly, preferably via an automated process (e.g., cron job). Ideally, at least one copy should be stored remotely (e.g., cloud storage or a different computer). Avoid relying on filesystem or VM snapshots as a backup method, as these are more complex operations where more things can go wrong, and recovery in such cases can be difficult or impossible for the typical user. Adding an extra layer of encryption on your backups would generally be a good idea (especially if your backup also includes config data like your [[admin token|Enabling-admin-page]]), but you might choose to forget this step if you're confident that your master password (and those of your other users, if any) is strong. ## Backing up data