mirror of
https://github.com/Start9Labs/documentation.git
synced 2026-03-26 02:11:55 +00:00
2734b4c08f
* Add instructions for mounting encrypted StartOS data drive * Clarify header language * Update backup-advanced.rst --------- Co-authored-by: kn0wmad <39687477+kn0wmad@users.noreply.github.com>
88 lines
2.9 KiB
ReStructuredText
88 lines
2.9 KiB
ReStructuredText
.. _backup-advanced:
|
|
|
|
=====================
|
|
Advanced Backup Tools
|
|
=====================
|
|
|
|
.. warning:: The following are advanced tools and using them is only advised when under the instruction of a Start9 Support Technician. USE AT YOUR OWN RISK - these operations are not supported outside of the context of support.
|
|
|
|
.. _backup-mount:
|
|
|
|
Mount a Backup
|
|
--------------
|
|
#. :ref:`Setup SSH Access<ssh>` and connect to your server via SSH. Elevate yourself to root once in:
|
|
|
|
.. code-block:: bash
|
|
|
|
sudo -i
|
|
|
|
#. Any previously added Network Folder backup location (or physical drive) will be available. Enter the following command:
|
|
|
|
.. code-block:: bash
|
|
|
|
embassy-cli backup target list
|
|
|
|
.. figure:: /_static/images/backups/backup-target-list.png
|
|
:width: 60%
|
|
|
|
#. Select the backup target from the available list. In this example, we could use either ``disk-/dev/sdb1`` or ``cifs-1``:
|
|
|
|
.. code-block:: bash
|
|
|
|
embassy-cli backup target mount disk-/dev/sdb1 "YourMasterPasswordGoesHere"
|
|
|
|
.. figure:: /_static/images/backups/backup-mount.png
|
|
:width: 60%
|
|
|
|
The terminal will print the directory where your decrypted backup is now mounted.
|
|
|
|
#. `ls` the directory to inspect it, and continue any other operations necessary:
|
|
|
|
.. figure:: /_static/images/backups/backup-mount-ls.png
|
|
:width: 60%
|
|
|
|
.. _backup-mount-data-drive:
|
|
|
|
Mount a StartOS Data Drive
|
|
--------------------------
|
|
If you have an encrypted disk from a prior StartOS installation, you can mount its decrypted contents on a Linux computer.
|
|
|
|
#. Attach the StartOS data drive to your Linux desktop or laptop computer.
|
|
|
|
#. Ensure cryptsetup is installed:
|
|
|
|
.. code-block:: bash
|
|
|
|
sudo apt update && sudo apt install cryptsetup
|
|
|
|
#. Enter the following command to reveal your disk's crypto_LUKS filesystems and their labels:
|
|
|
|
.. code-block:: bash
|
|
|
|
lsblk --fs
|
|
|
|
.. figure:: /_static/images/backups/disk-mount-1-lsblk.png
|
|
:width: 60%
|
|
|
|
We are interested in the services data so copy the long label ending with ``package-data``.
|
|
|
|
#. Take that label, prepend ``/dev/mapper/`` to it, and feed it to ``cryptsetup``:
|
|
|
|
.. code-block:: bash
|
|
|
|
sudo cryptsetup open /dev/mapper/EMBASSY_NBMVE7OASAPTIIXNEPFN6PLAPJNT72F2XAVK43L2PGB6O2JRB35A-package--data startos_data_unlocked
|
|
|
|
You will be prompted for the password to decrypt the filesystem which is ``password``, and a new device mapping called `startos_data_unlocked` will be created.
|
|
|
|
#. Mount the `startos_data_unlocked` device at a path of your choosing. Here, we will use ``/mnt/startos_data``:
|
|
|
|
.. code-block:: bash
|
|
|
|
sudo mkdir /mnt/startos_data
|
|
sudo mount /dev/mapper/startos_data_unlocked /mnt/startos_data
|
|
|
|
#. Inspect the decrypted files in preparation for copying via ``cp``, ``scp``, ``rsync`` or similar utility:
|
|
|
|
.. figure:: /_static/images/backups/disk-mount-3-inspect.png
|
|
:width: 60%
|