Vorta gives BorgBackup a desktop interface for selecting files, managing snapshots and restoring older copies. It can replace a paid file-backup workflow when you are willing to manage your own storage. This guide starts with a small folder and ends with a restore test before you trust a schedule. Provider documentation was checked on October 14, 2026; AltStack has not executed these installations or measured backup reliability on your machine. Follow the current instructions for your operating system and retain your original files throughout the exercise.

1. Understand the price and choose a realistic first backup

Vorta is GPL-3.0 software, and its Borg-based local workflow needs no Vorta subscription. You still supply the computer, destination drive and storage capacity. A remote hosting service such as BorgBase is optional and has its own plans; using Vorta does not include that service. Compare this with the particular paid backup task you want to replace. A desktop interface for file backups is different from a whole-system disk image or a bundled cloud-storage subscription.

Choose a test folder containing a few ordinary documents you can recognize. Avoid your only copy of a research project or a folder containing private client information for the first exercise. Decide how you will judge success: not just a completed backup notification, but being able to restore the documents into another folder and open them. Write down the location of the source and destination so they cannot be confused during setup.

2. Prepare storage before installing the application

A backup destination should survive the failure you are preparing for. A second folder on the same failing disk will not protect you from that disk's loss. For a beginner's local workflow, an external drive is an understandable starting point. Keep room for source files, restored samples and future snapshots. Label the drive and create a destination you can identify, separate from the documents you will select as sources.

Do not format or erase an existing drive merely to follow this guide. If it already holds valuable data, back it up and review its use before changing anything. Think about physical loss as well as file mistakes: a drive permanently beside the laptop shares some of the same risks. The first local exercise teaches the workflow; a broader backup plan may also need an independently stored copy. Storage, power and network arrangements remain your responsibility.

3. Install on macOS with the documented Homebrew route

If you already use Homebrew, the provider documents installing Borg without the optional mounting feature with brew install borgbackup, followed by brew install --cask vorta. These are two different components: Borg performs the backup work and Vorta supplies the interface. Review Homebrew's output and resolve a failed dependency before opening Vorta. The commands are presented here for you to review and run; AltStack has not executed them on your computer.

The project's installation page also links packaged macOS releases. Choose the current release and read its supported-system notes rather than assuming every old macOS version is covered. Mounting backup archives has additional FUSE requirements; you do not need to begin with that route. This guide uses extraction for the restore test. If the operating system questions a download, verify its origin and the current provider instructions. Do not disable system protections to get past an unexplained warning.

4. Install on Linux with the appropriate package

For a Linux system with Flathub configured, the provider's documented Flatpak command is flatpak install flathub com.borgbase.Vorta. Follow the Flathub setup for your own distribution first. The project also documents distribution packages and a source-install route. Beginners should choose one supported packaging method and use its normal update process, rather than mixing several installations and wondering which binary launches.

The Flatpak sandbox restricts access to certain system folders, including /root, /etc and /var. That can matter for a system-administration backup, but it need not block a first test with ordinary documents. Check the actual file access permitted by your package before selecting sources. If your task requires folders the sandbox cannot access, review the documented alternative installation instead of granting broad filesystem access without understanding it. Native Windows installation is outside this walkthrough; the provider discusses WSL separately, rather than promising an ordinary Windows app.

5. Create a repository and keep its recovery information

Open Vorta and inspect the settings window. Use the Add Repository menu and select New Repository… for a new destination. Pick the intended repository folder and review the encryption and passphrase settings before selecting Add. A repository is the storage container; an archive is a saved point in time inside it. Give the profile and destination names that make their purpose recognizable next month.

Store recovery information somewhere safe away from the source computer. You should be able to find it if that computer is lost. Keep it out of screenshots, public issue reports and Git repositories. Confirm that your destination is the backup location, not the source folder or an unrelated existing repository. Stop if you do not understand the selected encryption mode. The provider's restore guidance explains the passphrase or keyfile requirements; read that before deciding where recovery details will live.

6. Select sources and check the first snapshot

In Sources, add your small test folder and review any exclusions. Select Start Backup, then wait for the operation to finish. Check the result and the archive entry, rather than closing the application immediately after pressing the button. The actual duration depends on your files, hardware and destination. A timestamp alone is not enough to confirm that the intended documents were included.

Keep a simple record of what you selected and where the backup was stored. Open the archive listing and confirm that the test has an identifiable snapshot. If the run fails, retain the source files and note the failing stage before changing settings. Start with one source and one destination so a troubleshooting change is easy to reason about. Only expand the selection after the small restore test succeeds. This sequence is a recommended validation exercise, not a claim that AltStack has already backed up or recovered your data.

7. Restore into a separate empty test folder

In Archives, select the snapshot you want to examine and choose Extract. Review the files shown, select your sample, and set the Extraction Point to an empty folder you prepared for the test. Check that path again before starting. After extraction, open the recovered files and compare their contents with the originals. Pay attention to folders, filenames and the document you expected, not just whether some files appeared.

Extraction is a practical first restore method when you do not need to mount an archive as a drive. The provider also supports mounting with the appropriate platform requirements. If you use that method later, understand the FUSE dependency and unmount when finished. For this exercise, avoid overwriting a working source directory. Keep both copies until you are confident about the result. Save a short note about the successful recovery so you can repeat the same process when the original machine is unavailable.

8. Schedule only after you have verified recovery

Choose a suitable interval in Schedule, select Apply, and inspect Next Backup to confirm that the setting was accepted. Vorta needs to be running for its integrated scheduler to trigger the job. Its usage documentation describes starting the application when you log into the desktop. A schedule configured in the interface does not prove that a sleeping, disconnected or powered-off machine will complete a backup.

Make the schedule fit when the computer and destination are actually available. For an external drive, include a habit of connecting it and checking the most recent successful archive. For a remote destination, consider connectivity and the account's storage allowance. Return after the first scheduled interval and verify the observed result. Record failures and investigate repeated ones. An unattended task deserves occasional restore checks as well as success checks; otherwise a long list of jobs can create confidence without showing that important files remain recoverable.

9. Treat retention and exported settings carefully

Pruning removes older archives according to retention rules. Read the Vorta pruning article and the Borg prune documentation before enabling it. Decide which recovery points you actually need, and understand that deletion changes what can be restored. Do not turn on aggressive cleanup simply to make the first exercise look tidy. Preserve useful recovery points while you learn how the rules apply.

Profile export is useful when moving a configuration to another machine, but it can carry sensitive details. The settings documentation explains that an export can include repository information and optionally its password. Keep exported configuration files private, and review the options before sharing or storing them. A configuration export is not a substitute for the backed-up files or their encryption recovery information. Avoid importing unknown profiles or copying an initialization file from an unrelated tutorial: settings can change destinations and behavior. Make a backup of your current configuration before a planned migration.

10. Diagnose failures and keep a recovery checklist

If Vorta cannot launch, check which packaging method you installed and whether its Borg dependency is available. If sources are unavailable, review folder permissions and Flatpak access. If the destination cannot be reached, check the physical drive or the remote connection before changing the backup's configuration. Read the provider's current help and issue guidance for the error you actually observed. Keep version information and the stage of failure in your notes.

For a remote repository, SSH authentication and Borg encryption are separate responsibilities. Access to the server does not replace the key or passphrase needed to decrypt an archive. Before posting a support report, remove private filenames, server addresses, account credentials and recovery secrets from logs and screenshots. Finish with a checklist you can use without the original computer: where the repository lives, how to obtain the current application, where recovery information is stored, and which sample you successfully extracted. Review it periodically and after changing hardware, storage or credentials.

Official instructions and sources

Vorta source, free software license and supported desktop systemsmacOS installation and optional FUSE requirementsLinux packages and Flatpak limitationsCreate a local repository and select sourcesSnapshots, scheduling and application runtimeExtraction, mounting and recovery informationRemote backups and SSH authenticationPruning and retention controlsExported profiles and sensitive settingsPlatform limitations and troubleshootingBorg encryption optionsBorg archive retention semantics

Original AltStack guide by Sushil Kumar Sah. Installation steps follow provider documentation; they do not imply testing on every supported device.